Participating as an Elastos Council Member
The Elastos Council consists of 12 elected members who govern the DAO treasury, review proposals, and run critical infrastructure (sidechains, arbiter bridge). This page covers the on-chain mechanics of becoming and serving as a council member.
Becoming a Candidate
To run for the council, submit a RegisterCR transaction (type 0x21) with your DID, public key, and a locked deposit.
| Field | Description |
|---|---|
Code | Redemption script (P-256 public key) |
CID | Contract ID derived from the code |
DID | Your Elastos DID |
NickName | Display name (max 100 chars) |
Url | Campaign/info URL (max 100 chars) |
Location | Country code |
Signature | P-256 signature over the payload |
Candidates must lock a deposit of ELA to register. This deposit is returned when the member unregisters or their term ends, minus any penalties.
Update your profile with UpdateCR (type 0x23). Withdraw candidacy with UnregisterCR (type 0x22) — your deposit enters a return period before it can be reclaimed.
Candidate Lifecycle
Council Member Responsibilities
1. Reviewing Proposals
When a CRCProposal (type 0x25) appears on-chain, each council member submits a CRCProposalReview (type 0x26) with their vote:
| Vote | Value | Meaning |
|---|---|---|
| Approve | 0 | Support the proposal |
| Reject | 1 | Oppose the proposal |
| Abstain | 2 | No position |
Timelines:
- Council members have 7 days to vote on a proposal
- After council approval (8/12 required), the community has a 7-day public veto window
2. Tracking Proposal Execution
Council members monitor approved proposals and verify milestone completion. When a proposal team submits a CRCProposalTracking transaction (type 0x27), the Secretary General and council review the evidence.
3. Electing the Secretary General
The Secretary General handles day-to-day DAO operations. Council members elect the Secretary General via a SecretaryGeneral proposal (type 0x0400).
Claiming a Validator Node
After height 751,400, council members can claim BPoS validator nodes — contributing to block production in addition to governance.
Transaction: CRCouncilMemberClaimNode (type 0x31)
| Field | Description |
|---|---|
NodePublicKey | The BPoS node's public key |
CRCouncilMemberDID | Your DID |
CRCouncilMemberSignature | Signature proving DID ownership |
Once claimed, your node joins the active BPoS validator set alongside community-elected validators.
The Validator Set
Each validator takes turns proposing blocks. Block finality requires a two-thirds supermajority of active validators. See nodes.elastos.net for current counts.