Further questions
Some questions to explore further
The potential scale of on-chain events related to Halo could be geometrically larger than current chain-event generating projects. How can these be managed efficiently? Is there a useful opportunity to produce some “Halo friction” so that “spammy” achievements are adversely selected, and “valuable achievements” privileged?
Is there a design that integrates Web2 and Web3 architecture, where “critical” events are stored on-chain, and less critical events are linked back into a traditional Web2 data store? For example, the on-chain identity could store verifiable links to a related data file (e.g. a JSON object) that contains the long tail of individual Halo events.
How is a Halo achievement composed by the issuer? What “standing” should the Halo issuer have in the ecosystem to qualify themselves as a “legitimate actor” in the granting of Halo?
How can the bad-faith of trading or selling Halo be controlled for?
In the creation of DAOs and staking mechanisms, how can Halo be used to counterbalance the risk of “rich token owners” controlling governance alone?
In the case of the Ready Games ecosystem, how does Halo integrate with the accumulation of $aura tokens? (See whitepaper on $aura, link)
See wikipedia. “Reputational Capital.” Source ↑
The concept of NTSTs derives from Jeremy Parris, Venture Associate at Delphi Digital. A draft paper exists by Parris describing the theoretical case for the development of NTSTs. Source. Ready is indebted to Parris’ thoughts in this arena. ↑
See “Gini Coefficient”, Wikipedia. Source. ↑
Last updated