Skip to main content

Dynamic governance

Who pays for open-source work after the original team leaves? We designed dynamic governance so wallets, documentation, hosting, and research can compete for public funding. When a small treasury group controls day-to-day funding, the people maintaining the network depend on that group’s priorities and finances. A public proposal, vote, and payout give the community a way to scrutinize those choices over time. Sidhu’s February 2025 essay

We limit what a funding vote can do and how fast the budget can change. The time between cycles gives people a chance to see where funds went and respond. A funding vote can pay for work on a protocol change. Activating consensus rules still requires nodes to run software that enforces them. The Syscoin 5 Nexus upgrade added the adaptive budget described below. Nexus rationale · Proposal approval

How one cycle sets up the next​

Proposals compete for funding in a scheduled cycle of 17,520 blocks on mainnet. Sentry votes determine which requests qualify and their priority. The payment window and the cycle’s ceiling determine what can be paid. At a triggered superblock, a node can verify the selected payouts in the block’s coinbase outputs. Core uses the payout it records to set the next nominal budget. Mainnet schedule and proposal rules

The nominal budget is the baseline, and the current cycle can pay up to 110% of it, subject to the 5 million SYS payment ceiling. If the recorded payout is positive and at most 95% of the nominal budget, the next budget falls by 10%, down to a 20,000 SYS floor. At 105% or more, it rises by 10%, up to 5 million SYS. Between those thresholds, or with zero paid, it stays the same.

What becomes the next nominal budget when the current budget is 2 million SYS?
Zero paid
2.0M SYS No change
1.9M SYS paid · 95%
1.8M SYS Falls by 10%
2.0M SYS paid · 100%
2.0M SYS No change
2.1M SYS paid · 105%
2.2M SYS Rises by 10%

The step limit gives participants time to see and respond to sustained changes in spending. Payouts give the protocol an observable input. They can also reflect the voting threshold, proposal timing, or which requests fit the ceiling. Unused capacity creates no treasury payment.

Read the exact budget rules

Follow a public payout​

An August 2026 ecosystem sustainability proposal requested 4,350,000 SYS per month. Superblock 2,330,160 paid that amount in output 2 of its coinbase transaction. The address matches the mainnet wallet published on the proposal’s linked infrastructure support page. The governance trigger identifies the same proposal hash, amount, and recipient. That lets an independent reader verify the amount and destination of the payment. Subsequent expenditures and the delivery of the proposed work are separate facts. Proposal · Published recipient · Coinbase transaction

Verify the trigger and coinbase from Core

On a synced mainnet node that retains the governance trigger, check its event height, proposal hash, recipient, and amount. Read the third coinbase output from the canonical block using jq.

trigger=d29a40acbd9d623580eeb33680e0636b02fbe27b2994322137c952a1033382a8
syscoin-cli gobject_get "$trigger"
block=$(syscoin-cli getblockhash 2330160)
syscoin-cli getblock "$block" 2 | jq '.tx[0].vout[2]'

The trigger refers to proposal 9c675dfc0bd5d7b08dbdd8300e918d1f9c50b0c6804ede8336c41d010e5248a2. The block output remains checkable long after a node has forgotten the governance object.

Use a synced Core node to inspect the schedule and nominal budget, submit a proposal, cast a vote, or verify a payout against a block’s outputs. Governance commands