<aside> ⛓️ Hyperstructures have been defined differently in various domains of knowledge dating back at least 30 years (references below).
</aside>
Unresolved Hypotheses About Hyperstructures
Table of Contents
<aside> 🧠 Hyperstructures were first widely defined in the context of smart contracts in the “OP” by Jacob Horne, founder of Zora Protocol. [ref]
</aside>
“Hyperstructures take the form of protocols that run on blockchains. Something can be considered a hyperstructure if it is:
- Unstoppable: the protocol cannot be stopped by anyone. It runs for as long as the underlying blockchain exists.
- Free: there is a 0% protocol wide fee and runs exactly at gas cost.
- Valuable: accrues value which is accessible and exitable by the owners.
- Expansive: there are built-in incentives for participants in the protocol.
- Permissionless: universally accessible and censorship resistant. Builders and users cannot be deplatformed.
- Positive sum: it creates a win-win environment for participants to utilize the same infrastrastructure.
- Credibly neutral: the protocol is user-agnostic”
<aside> 🧠 Since then, a few notable voices have published affirmations, albeit the only claimed implementation is not open-source.
</aside>
<aside> 🧠 Authors: Evan Aronson, Ivan Fartunov, and Joan Arús
</aside>
Building the Hyperstructure for Governance
<aside> 🤔 Details of their strategy, in which they deviate from meeting at least one of the requirements defined in OP, are published on GitHub without any code.
This is now logged in Unresolved Hypotheses About Hyperstructures.
</aside>