Skip to main content
MAIN CHAIN

Elastos Council Operations

Elastos Council overview​

The Elastos Council is Elastos’s on-chain governance body. Twelve members are elected by ELA holders and collectively review proposals, manage treasury-aligned decisions, and participate in the wider BPoS ecosystem under consensus rules.

Core quorum parameters:

  • MemberCount: 12
  • CRAgreementCount: 8; at least eight members must align for council agreement on many actions (approximately a two-thirds threshold across twelve seats).
Accountability

Council members can be impeached by the community when vote thresholds are met; you are accountable between formal election cycles, not only at election time.

Prerequisites for candidacy​

Before registering, candidates should ensure:

  1. Deposit: 5,000 ELA registered as the Elastos Council candidate deposit (subject to chain rules for lock and return).
  2. Infrastructure: A fully synced supernode with all required components running as expected for production Elastos Council operation.
  3. Timing: Registration during the active voting period for the election you are entering.

Failure at any of these steps typically prevents a valid candidacy or leaves you unable to fulfill council duties.

Registering via node.sh​

Council candidacy is registered through the Elastos node helper script. Example:

# Register as an Elastos Council candidate (name and public URL are published on-chain)
node.sh ela register_crc "MyCouncilName" "https://mycouncil.example.com"

Optional arguments (such as region) may apply depending on your node.sh version; use node.sh ela help or your deployment docs for the exact interface.

Operational readiness

Running a council seat implies reliable uptime and security hygiene. Treat keys, firewall rules, and monitoring as production requirements, not optional extras.

Election cycle parameters​

Important main-chain heights for Elastos DAO governance include:

ParameterHeightMeaning
CRVotingStartHeight537,670Elastos Council candidate voting begins
CRCommitteeStartHeight658,930First Elastos Council is seated

Earlier heights such as VoteStartHeight (290,000) govern when broader on-chain voting features activate; see configuration reference for the full timeline.

Voting power​

Voting power is proportional to locked ELA committed in voting transactions. The more ELA a voter locks for a candidate (within consensus rules), the more weight their vote carries toward electing the twelve seats.

Council responsibilities​

Council members are expected to:

  • Review community suggestions and formal Elastos Council proposal payloads.
  • Vote on funding, ELIPs, and procedural items subject to CRAgreementCount.
  • Coordinate with the Secretary General on operational sequencing where applicable.

After CRClaimDPOSNodeStartHeight (751,400), members may claim a BPoS node role, contributing to block production and additional staking-related rewards; governance and validation can overlap for elected seats.

Post–NoCRCDPOSNodeHeight

At NoCRCDPOSNodeHeight (932,530), Elastos Council nodes are no longer guaranteed fixed arbiter slots. Arbiter selection follows the rules in force at each height. Plan node operations with current consensus documentation.

Impeachment​

Any community member can initiate impeachment against a council member when the chain’s rules allow it. A threshold-based community vote determines whether the member is removed. If removal succeeds, deposits and eligibility follow the consensus rules for that outcome (see governance references for details).

Example CLI entry point (exact subcommands vary by tooling version):

node.sh ela impeach_crc

Always verify against the node and node.sh version you run in production.

Proposal management workflow​

End-to-end governance typically follows:

  1. Community suggestion: Ideas surface in the Elastos DAO governance portal and community channels.
  2. Council review: Suggestions become formal on-chain proposals where appropriate.
  3. Elastos Council proposal on main chain (CRCProposal): Typed proposal with budgets and milestones.
  4. Vote phases: Council review and, where required, broader voter agreement.
  5. Budget withdrawal: Elastos Council proposal withdrawal via CRCProposalWithdraw (and related tracking) releases funds per milestone, not as a single upfront payment.

The Secretary General provides operational coordination across this pipeline (scheduling, communication, handoffs), distinct from raw voting power but critical for execution.

BPoS node claim and economics​

A seated council member may claim a BPoS validator node after the claim height above, earning validator-side rewards in addition to fulfilling governance duties. This binds economic performance to infrastructure behavior; monitor your node like any production validator.

Further reading​