HC1: HyperQube SIG Roadmap: Difference between revisions
No edit summary |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 26: | Line 26: | ||
On hyperqube_z, deploy new pay to merkle root embedded contract, with withdrawal using merkle inclusion proof. (Allows multiple people to be paid with 1 transaction). | On hyperqube_z, deploy new pay to merkle root embedded contract, with withdrawal using merkle inclusion proof. (Allows multiple people to be paid with 1 transaction). | ||
On hyperqube_z, deploy changes to AZ that payout to merkle root contract. | (Solutions beside merkle will be evaluated. Goal is payouts to multiple people with an atomic tx) | ||
On hyperqube_z, deploy changes to AZ that allow payout to merkle root contract. | |||
| Line 54: | Line 56: | ||
Usage of hyperqube_z incubator chain to rapidly develop and deploy new features and upgrades. | Usage of hyperqube_z incubator chain to rapidly develop and deploy new features and upgrades. | ||
Including dynamic plasma, sentinels, dex, libp2p, and other fun and experimental features such as ZNS and on-chain microblogging. | Including dynamic plasma, sentinels, dex, libp2p, narwhal&tusk and other fun and experimental features such as ZNS and on-chain microblogging. | ||
Deploy relevant/useful ones to mainnet. | |||
== 3b. Extension Chain == | == 3b. Extension Chain == | ||
Connect hyperqube_z to mainnet via bridge. | Connect hyperqube_z to mainnet via bridge and work on true extension chain features. | ||
Enable chain/data relay through oracles. | |||
Enable additional usecases for bridged ZNN and/or bridged QSR. | Enable additional usecases for bridged ZNN and/or bridged QSR. | ||
Latest revision as of 17:18, 3 October 2024
1. Launch
Launch an independent L1 (hyperqube_z) supported by a broad set of dedicated Zenon community members backed by mainnet Pillars.
Demonstrate the ability to work together to comprehensively deliver a new desired feature: Governance module, with incentives for all necessary components including testing, docs, etc
With governance module, signal and vote for community driven development.
Hyperqube new supported use cases:
- Community polling/signalling
- Testnet for Zenon mainnet
Benefits to Mainnet:
- Same as above
Payout will either be individual payouts or deferred until step 2.
2. Collaborative Work and Payout
Create new embedded contracts on hyperqube_z to support Incubator functionality, and move the collaborative work process on-chain.
On hyperqube_z, deploy new pay to merkle root embedded contract, with withdrawal using merkle inclusion proof. (Allows multiple people to be paid with 1 transaction).
(Solutions beside merkle will be evaluated. Goal is payouts to multiple people with an atomic tx)
On hyperqube_z, deploy changes to AZ that allow payout to merkle root contract.
Deploy governance module onto mainnet if desired or necessary.
Hardfork kaine out of spork control on mainnet if necessary.
Deploy AZ changes and merkle root contracts to mainnet.
Hyperqube new supported use cases:
- Incubator: on-chain work tracking, bidding, and AZ proposal formation
Benefits to Mainnet:
- A place to send new developers to pick up incremental work
- Governance module (if needed)
- Ability to pay multiple people with one transaction
AZ:
Payout here and after will be through the merkle contract.
3a. Renaissance
Usage of hyperqube_z incubator chain to rapidly develop and deploy new features and upgrades.
Including dynamic plasma, sentinels, dex, libp2p, narwhal&tusk and other fun and experimental features such as ZNS and on-chain microblogging.
Deploy relevant/useful ones to mainnet.
3b. Extension Chain
Connect hyperqube_z to mainnet via bridge and work on true extension chain features.
Enable chain/data relay through oracles.
Enable additional usecases for bridged ZNN and/or bridged QSR.
Add direct support on mainnet for extension chains and incentivization.
Possibly rework hyperqube_z tokenomics to account for bridged assets.