Intro
Common serves as a governance and coordination layer for Tezos bakers and delegates. It streamlines participation in Tezos decentralized governance through intuitive dashboards and voting mechanisms. This guide explains how to deploy Common effectively within the Tezos ecosystem.
Key Takeaways
Common integrates directly with Tezos baker infrastructure to automate governance decisions. Users access real-time voting metrics and delegate weight analysis through its interface. The platform reduces technical barriers for non-technical delegates. Security audits by external firms protect user funds throughout the process.
What is Common
Common is a governance facilitation tool built specifically for the Tezos blockchain. It connects bakers with their delegators to coordinate voting on on-chain proposals. The platform aggregates delegate preferences and executes votes according to predefined parameters. Tezos relies on such tools to maintain its self-amending governance model.
Why Common Matters
Tezos governance requires broad delegate participation to function properly. Many delegators lack technical knowledge to cast informed votes on protocol upgrades. Common bridges this gap by providing clear proposal summaries and voting recommendations. The platform increases governance participation rates across the Tezos network. Active delegate involvement strengthens the overall security and evolution of the protocol.
How Common Works
Common operates through a structured decision pipeline that converts delegator intent into on-chain votes. Core Mechanism Formula: Vote_Output = Σ(Delegate_Weight × Voting_Preference) ÷ Total_Delegate_Weight The system first collects voting preferences from registered delegators. Each preference carries weight proportional to the delegate’s Tezos holdings. Common then calculates aggregate positions using weighted averaging. Finally, the platform executes votes matching the calculated consensus position. Step-by-Step Process:
- Delegators connect wallets and submit voting preferences through the dashboard.
- Common verifies wallet ownership and records preferences in the system.
- The engine calculates aggregate preference weighted by delegate stake.
- Baker executes the resulting vote on-chain using authenticated keys.
- Vote confirmation propagates to the Tezos blockchain within one block.
Blockchain governance tools like Common formalize decision-making processes that were previously ad hoc.
Used in Practice
A Tezos baker named “Tezos Commons” recently used Common to coordinate voting on the Mumbai protocol upgrade. The baker gathered preferences from 2,400 delegators representing 8.3 million XTZ. Within 72 hours, Common aggregated preferences and executed the consensus vote. The process eliminated manual vote collection that previously took two weeks. Delegators received automatic notifications of the outcome through the platform.
Risks / Limitations
Platform downtime during critical voting periods could miss proposal deadlines. Common relies on accurate delegate preference data; misconfigured settings produce incorrect votes. The tool cannot guarantee bakers will honor aggregated preferences as submitted. Central bank research on blockchain governance highlights that delegated voting systems concentrate influence among large bakers. Users must verify their baker’s voting record before committing delegation.
Common vs Manual Voting
Manual voting requires delegators to directly interact with Tezos wallets for each proposal. Common automates this process through preset preferences that execute automatically. Manual voting offers granular control but demands technical expertise and constant attention. Common sacrifices some customization for convenience and consistency across votes.
Common vs Snapshot Voting
Snapshot voting captures delegate weights at specific block heights for governance calculations. Common enhances snapshot voting by aggregating preferences before the snapshot occurs. Snapshot tools alone do not facilitate preference collection or vote coordination. Common adds the communication layer that makes snapshots actionable for ordinary delegators.
What to Watch
The upcoming Nairobi protocol upgrade introduces new governance features that Common may integrate. Developer activity on the Common GitHub repository indicates upcoming dashboard improvements. Regulatory clarity around decentralized governance tools varies by jurisdiction. Competition from other Tezos governance platforms could fragment delegate coordination efforts. Baker consolidation trends affect how Common distributes governance influence across the network.
FAQ
Does Common hold my Tezos tokens?
No. Common only reads wallet balances to calculate voting weights. Private keys remain in your control throughout the process.
Can I change my voting preference after submission?
Yes. Users can update preferences at any time before the voting deadline for each proposal.
What happens if my baker doesn’t use Common?
Your delegation still earns baking rewards. However, your voting preferences will not influence governance decisions through the platform.
Is Common open source?
The core voting aggregation code is publicly auditable. The platform publishes regular security audit reports on its official website.
How does Common handle proposal disputes?
Common provides links to full proposal documentation but does not offer investment advice on governance outcomes.
What are the fees for using Common?
Common charges no direct fees to delegators. Bakers may incorporate platform costs into their operational fee structures.
Can institutions use Common for large delegations?
Yes. Institutional delegators receive dedicated dashboard access and priority support for governance coordination.
Leave a Reply