Skip to main content

Decentralized governance

Syscoin Core lets users submit funding proposals and valid Sentry Nodes vote on them. A proposal requests a payment from the base-chain superblock budget. Any user with the proposal fee can submit one. Funding votes use the voting key registered for the Sentry Node, which may be delegated. This guide follows the released Core v5.1.3 rules. Proposal admission · Funding vote verification

For the design rationale and a public superblock example, see Dynamic governance.

Inspect proposals and the schedule​

Run these commands on a synced node. Substitute the governance object hash for GOVERNANCE_HASH. For Tanenbaum, add -testnet before each RPC command.

syscoin-cli getgovernanceinfo
syscoin-cli getsuperblockbudget
syscoin-cli gobject_list all proposals
syscoin-cli gobject_get "$GOVERNANCE_HASH"
syscoin-cli gobject_getcurrentvotes "$GOVERNANCE_HASH"

Mainnet superblocks follow a 17,520-block cycle, roughly monthly at the target block interval. Tanenbaum uses 60 blocks. Use nextsuperblock for the next scheduled height. A proposal’s net funding vote is yes minus no. To qualify for selection, it must reach the greater of the network’s minimum governance quorum and one tenth of the current valid Sentry Node count, rounded down. Core considers qualifying proposals in order of net support and applies the payment window and budget. Verify actual payment in the superblock’s coinbase outputs. Mainnet schedule · Testnet schedule · Proposal selection

How the superblock budget changes​

Under the released mainnet rules, the nominal SYS budget is a limit used to select payments. It starts from 2,000,000 SYS when a valid previous superblock has no cached budget. At a scheduled superblock, qualifying proposals can draw up to 110% of the nominal budget, capped at 5,000,000 SYS. Core records the actual payment for adjustment purposes as the coinbase output total above the ordinary block-payment allowance. Individual recipients and amounts are visible in the triggered superblock’s outputs. Budget lookup · Output limit and utilization · Selecting payable proposals

Payment relative to the prior nominal budgetNext nominal budget
ZeroKeep the prior budget.
Above zero and at most 95%Reduce by 10%, with a floor of 20,000 SYS.
Above 95% and below 105%Keep the prior budget.
At least 105%Increase by 10%, with a ceiling of 5,000,000 SYS.

For example, suppose the prior nominal budget is 2,000,000 SYS. A 1,900,000 SYS payment sets the next budget to 1,800,000 SYS. A 2,100,000 SYS payment sets it to 2,200,000 SYS. A cycle with no payout leaves the nominal budget at 2,000,000 SYS and mints no proposal payment. The released rules and the PQ candidate use the same budget arithmetic. The candidate changes how voting authority and eligibility are verified. Budget constants · Released adjustment · PQ candidate adjustment · PQ signing roles

Submit a proposal​

  1. Write a proposal with type set to 1, a name, start_epoch and end_epoch in Unix seconds, the requested payment_amount in SYS, a base-chain payment_address for the selected network, and a url with the proposal details. Encode the exact JSON bytes as hex, save them with the parent hash, revision, and creation time, and run gobject_check "$DATA_HEX".
  2. Once you have reviewed the data, call gobject_prepare from a funded wallet using those values. In the default wallet configuration, this step commits and broadcasts the fee transaction. The current proposal fee is 150 SYS burned on mainnet, plus the ordinary transaction fee. Save the returned fee transaction ID.
  3. Wait for six active-chain confirmations for the fee transaction, then use gobject_submit with the same parent hash, revision, creation time, hex data, and the fee transaction ID. Record the returned governance object hash and query it from a synced node.

Use syscoin-cli help gobject_prepare and syscoin-cli help gobject_submit for argument order. A root proposal uses parent hash 0. Rehearse the flow with test funds before preparing a mainnet proposal. Proposal data validation · Fee and confirmation constants · Fee transaction and broadcast

Cast a funding vote​

Use a local wallet that holds the registered voting key for a valid Sentry Node. Set OUTCOME to yes, no, or abstain, and PROREG_TXID to the Sentry Node’s registration ID.

syscoin-cli -rpcwallet="$VOTING_WALLET" gobject_vote_alias \
"$GOVERNANCE_HASH" funding "$OUTCOME" "$PROREG_TXID"
syscoin-cli gobject_getcurrentvotes "$GOVERNANCE_HASH"

The PQ candidate proposes an independent SLH-DSA key for proposal funding votes. The released v5.1.3 instructions above use the current voting key. Released voting RPC · PQ signing roles