1. Connect to the new chain
The creator page talks to a public validator RPC. It does not run on the validator.
Verify the creator governance wallet and the genesis dripWallet, review the rules already enforced by the chain, record the initial configuration, and execute creator governance actions through signed on-chain proposals.
The creator page talks to a public validator RPC. It does not run on the validator.
This wallet is the first accepted governance member created in genesis.
This separate wallet is already registered as an active escrow voter.
These are engine rules, not merely text entered by the creator.
All 1,000,000,000 CWC starts at protocol:treasury. No private key can directly spend it.
Each active governance member appears once in the eligible voter snapshot for a proposal.
Treasury transfers, budgets, membership changes, and parameter changes execute only after YES votes exceed two-thirds of eligible members.
Each escrow names active dripWallet voters and its own threshold. A YES or NO threshold atomically settles the escrow plan.
Records the completed bootstrap configuration on-chain. Enforcement still comes from the engine rules above.
Add treasury, budget, membership, or parameter actions to one proposal.
The governance wallet signs both the proposal and its YES vote. Nothing is submitted until you press commit.
{}
Current members, proposals, and budgets.
Connect to load governance state.
RPC, signature, proposal, and vote results.