Skip to content
Tenzro
Documentation menu
Machine Economy

Governance

How Tenzro Network 1 is governed: Tenzro Foundation stewardship, on-chain proposals and stake-weighted voting.

Tenzro Network 1 is open, permissionless and open source under Apache 2.0. Two things govern it: the Tenzro Foundation, which stewards the project, and on-chain governance, in which staked TNZO votes on the parameters the protocol runs by.

The Tenzro Foundation

The Tenzro Foundation is a non-profit and the steward of the network. It is responsible for:

  • The protocol and network primitives, published under Apache 2.0.
  • The repositories, documentation and tools that developers and operators use.
  • Distribution and outreach, making the network's resources known and available.
  • TNZO, as the governing body for the token that pays all network fees and transaction settlement.

The Foundation works with the people and companies building on the network: individual developers and the open-source community, and commercial partners such as Tenzro Labs, which helps operators of any background get onboard. Tools, including abstraction layers for payments and TNZO, are built by the Foundation, by independent developers and by partners.

Anyone can be an operator, a developer or a user. No role requires the Foundation's permission. See Foundation.

On-chain governance

Protocol parameters change through proposals that TNZO stakers vote on, on-chain. A proposal that passes is executed by the protocol, not by hand.

What a proposal can change

Type--typeChanges
Parameter changeparameterA single protocol parameter, such as a bond floor or a burn share
Economic policyeconomic_policyThe whole economic policy at once: every rate the network charges and the revenue split
Treasury granttreasuryA payment from the network treasury to a recipient
Protocol upgradeupgradeA new protocol version, identified by its code hash

An economic-policy proposal carries the complete policy rather than one field, so a change can never leave the rates half-applied or a revenue split that does not sum to the whole payment. Start from the policy the network applies today:

bash
tenzro governance economic-policy --json

Voting power

Voting power is weighted by staked TNZO at the proposal's snapshot. Operators who bond TNZO for any role vote with that stake. A staker can delegate voting power to another address without moving the stake.

Read an address's voting power over RPC with tenzro_getVotingPower, and delegate with tenzro_delegateVotingPower, signed by the delegating account.

Lifecycle

  1. Propose. A staker submits a proposal with a title, a description and its type. Submitting requires a minimum stake and a deposit, both governance parameters.
  2. Vote. While the proposal is active, stakers vote yes, no or abstain, optionally with a reason. Abstentions count toward quorum but not toward approval.
  3. Decide. When voting closes, the proposal passes if it met quorum and its approval threshold, and fails otherwise.
  4. Execute. A passed proposal is executed by the protocol.

Quorum, approval threshold and voting duration are themselves governance parameters.

Using the CLI

bash
# See what is being decided
tenzro governance list --active
tenzro governance list --detailed

# Propose a parameter change
tenzro governance propose \
  "Adjust the storage bond floor" \
  "Rationale, expected effect and the exact parameter and value." \
  --type parameter

# Vote
tenzro governance vote <proposal_id> yes --reason "Matches observed demand"

Every call that creates a proposal, votes or delegates must be signed by the staking account. Reads are open to anyone:

bash
curl -s https://rpc.tenzro.xyz \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tenzro_listProposals","params":[]}'
MethodClass
tenzro_listProposals, tenzro_getProposal, tenzro_getVotingPoweropen
tenzro_createProposal, tenzro_vote, tenzro_voteOnProposal, tenzro_delegateVotingPowerowner (signed by the staking account)

What governance controls

  • Fees and burn. The split of the base fee between burn and treasury, and the burn share for gas paid in local assets. See Token economics.
  • The economic policy. The network's share of settled payments and the RPC provider's share for nodes that do not validate. See Settlement.
  • Bonds. The bond floor for each operator role and the withdrawal cooldown.
  • The treasury. Grants, the set of authorised withdrawers and the approval threshold.
  • Upgrades. Which protocol version the network runs.

Some things are not up to a vote. The total supply of TNZO is fixed at 1,000,000,000, and an operator's majority of each settled payment is enforced by the protocol, so no proposal can take it away.