Tokens, Incentive Design and Decentralized Governance

Introduction and Context

Decentralized applications (DApps) are not merely software systems deployed on a blockchain. They are socio-technical institutions in which code, economic incentives, cryptographic rights, and collective decision-making interact. A token may represent ownership, access, voting power, a claim on assets, or a unit of account. Governance determines how rules change, resources are allocated, disputes are resolved, and participants are held accountable.

The strategic importance of token and governance design arises from a central problem: a DApp must encourage behaviour that creates long-term value without giving a small group excessive power or rewarding short-term extraction. Poorly designed tokens can produce speculation without utility; poorly designed governance can be captured by wealthy holders, flash-loan-funded voters, insiders, or coordinated minorities. Conversely, well-designed systems can coordinate participants who do not share a legal entity, employer, or physical location.

This chapter examines token standards, utility, incentive alignment, mechanism design, voting, treasuries, decentralized autonomous organizations (DAOs), governance attacks, and sustainable participation models. The emphasis is on analysis rather than on the assumption that decentralization is automatically beneficial.

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Distinguish major fungible, non-fungible, semi-fungible, and governance token standards.
2. Analyse token utility, value capture, distribution, vesting, and monetary policy.
3. Apply mechanism-design principles to incentive alignment and resistance to manipulation.
4. Compare voting systems and evaluate their assumptions and failure modes.
5. Explain DAO treasury design, proposal lifecycles, delegation, and accountability.
6. Identify governance attacks, including plutocratic capture, bribery, flash-loan voting, and social-layer attacks.
7. Design sustainable participation models using appropriate incentives, safeguards, and performance metrics.

1. Tokens as Institutional Instruments

A token is a digitally recorded unit of entitlement or coordination. Its meaning is not determined by its name but by its technical rights, economic constraints, legal context, and social interpretation. A token can be:

• Fungible: each unit is interchangeable with another unit of the same class.
• Non-fungible: each token is individually identifiable and not necessarily interchangeable.
• Semi-fungible: tokens may be interchangeable within a class but distinct across classes.
• Native: issued as part of a blockchain’s base protocol.
• Application-level: issued by a smart contract operating on an existing blockchain.
• Permissionless or permissioned: transferable and usable by anyone, or restricted by identity and authorization rules.

A token system should be analysed through four questions:

1. What right or capability does the token provide?
2. Who receives it, under what conditions, and with what restrictions?
3. How can its supply and distribution change?
4. What behaviour does its design encourage or discourage?

A token that has no credible answer to the first question may be a speculative asset rather than a useful coordination instrument. A token with valuable rights but concentrated distribution may create a governance hierarchy that contradicts the project’s public claims of decentralization.

1.1 Major Token Standards

Standards define common interfaces so wallets, exchanges, marketplaces, and other contracts can interact reliably with tokens. Standards do not guarantee sound economics or legal compliance.

A fungible token balance is commonly represented as an account-to-balance mapping. A non-fungible system instead maps a unique token identifier to an owner and may associate metadata with that identifier. The distinction affects divisibility, transfer logic, market structure, and governance risk.

Standards also create composability. A lending protocol may accept a token issued by another application as collateral. This improves innovation but creates dependency risk: a bug, oracle failure, or governance attack in one system can propagate to others.

2. Token Utility and Value Capture

2.1 Categories of Utility

Token utility can be classified as follows:

• Access utility: the token is required to use a service or enter a network.
• Payment utility: the token is used to pay fees or settle transactions.
• Security utility: holders stake tokens and may lose them for dishonest conduct.
• Governance utility: holders vote, delegate, propose, or approve changes.
• Coordination utility: tokens reward contributions, allocate scarce resources, or signal preferences.
• Asset or claim utility: the token represents ownership, redemption, revenue participation, or a legal claim, subject to applicable law.

These categories can overlap. A token used for governance does not necessarily have economic value merely because it has voting rights. Value depends on whether governance controls a valuable resource, whether rights are enforceable, and whether supply and demand conditions support the token.

2.2 Direct and Indirect Value Capture

A protocol may generate fees while its token captures little or none of that value. This distinction is strategically important. Possible value-capture mechanisms include fee sharing, token buybacks, staking rewards funded by protocol revenue, access rights, or control over treasury assets. Each mechanism introduces trade-offs involving regulation, sustainability, dilution, and stakeholder fairness.

A simple dilution relationship is:

This expression assumes that all tokens have the same governance weight and that no delegation, lock-up multiplier, or special class exists. If a holder owns 1,000 tokens and total outstanding supply is 10,000 tokens, the holder’s token ownership is 10%. That does not necessarily mean 10% of votes, because voting power may be delegated, time-weighted, capped, or separated from economic ownership.

If new tokens are minted, the post-mint ownership of an existing holder is:

where h is the holder’s tokens, S₀ is pre-mint supply, and M is newly minted supply. The formula assumes the holder receives none of the new tokens and that all units have equal status. For example, with 1,000 tokens held, pre-mint supply of 10,000, and a mint of 2,000, the share becomes 1,000 ÷ 12,000 = 8.33%, not 10%.

2.3 Token Design Questions

A professional token design process should specify:

• initial allocation and recipient categories;
• investor, employee, and adviser vesting;
• emissions and maximum supply, if any;
• treasury and ecosystem reserves;
• transfer restrictions and jurisdictional controls;
• staking requirements and slashing conditions;
• governance eligibility and delegation rules;
• redemption, fee, or access rights;
• procedures for emergency upgrades and retirement.

Vesting reduces immediate selling pressure and aligns contributors with long-term development, but it can also conceal future dilution. Transparency requires publishing both circulating supply and fully diluted supply, together with unlock schedules.

3. Incentive Alignment and Mechanism Design

Mechanism design studies how rules can produce desirable outcomes when participants have different information, preferences, and opportunities for strategic behaviour. In a DApp, the mechanism includes smart-contract rules, reward schedules, access conditions, voting procedures, and social enforcement.

3.1 Principal–Agent Problems

A principal–agent problem occurs when one party makes decisions on behalf of another but has different incentives or better information. Examples include token holders delegating votes to professional delegates, a multisignature committee managing a treasury, or liquidity providers relying on an automated market maker’s parameter-setting process.

The design response may include:

• transparent reporting;
• measurable performance objectives;
• bounded authority;
• revocable delegation;
• conflicts-of-interest disclosure;
• independent review;
• staged funding;
• slashing or loss of reputation for misconduct.

No mechanism fully eliminates information asymmetry. The goal is to make misconduct costly, detection more likely, and authority proportionate to responsibility.

3.2 Public Goods and Free Riding

Protocol documentation, open-source code, security research, and community support often benefit all users but are difficult to fund through ordinary transactions. Participants may prefer others to pay while enjoying the result. This is the free-rider problem.

Possible responses include retroactive rewards, grants, quadratic funding, contribution attestations, and recurring budget allocations. These mechanisms require protection against identity fraud, collusion, sybil accounts, and low-quality submissions.

3.3 Staking and Security Incentives

In proof-of-stake or application-level staking, participants lock assets to obtain rewards or influence while accepting penalties for defined misconduct. A basic net-return expression is:

All terms must be measured over the same period and in comparable units, commonly tokens or monetary value. Expected penalty can be represented as:

This is an expected-value model, not a prediction of an individual outcome. It assumes that probabilities and losses can be estimated and that participants are sensitive to expected economic costs. In practice, uncertainty, liquidity constraints, reputation, and legal risk also affect behaviour.

A high nominal reward does not necessarily create security. If rewards are funded by uncontrolled issuance, token dilution may exceed the benefit. If slashing is ambiguous or technically unsafe, honest participants may avoid staking. Security therefore depends on credible rules, adequate decentralization, reliable monitoring, and proportional penalties.

3.4 Mechanism-Design Principles

Effective incentive mechanisms commonly follow these principles:

1. Compatibility: truthful or desired behaviour should be a reasonable strategy.
2. Participation: honest participation should be worthwhile after costs and risks.
3. Budget discipline: rewards should be affordable and linked to value created.
4. Resistance to sybil behaviour: one actor should not gain unlimited influence by creating many identities.
5. Auditability: participants should be able to verify calculations and decisions.
6. Adaptability: parameters should change through legitimate and controlled processes.
7. Proportionality: penalties and powers should match the severity of misconduct.

Mechanism design cannot substitute for a clear objective. Rewarding a measurable proxy may cause participants to optimize the proxy rather than the underlying goal, a problem known as Goodhart’s law.

4. Governance Architecture

Governance is the process through which collective decisions are proposed, evaluated, authorized, executed, and reviewed. It includes both on-chain mechanisms and off-chain institutions such as forums, working groups, legal entities, and contributor norms.

A typical lifecycle is:

1. Agenda formation: a problem or proposal is identified.
2. Discussion: technical, economic, legal, and security implications are examined.
3. Drafting: the proposal specifies code changes, parameters, costs, and risks.
4. Temperature check: an informal or non-binding signal tests community support.
5. Formal vote: eligible participants cast or delegate votes.
6. Timelock: approved actions remain visible for a delay before execution.
7. Execution: a contract, multisignature group, or authorized executor performs the action.
8. Monitoring: outcomes and unintended effects are reviewed.

Separation between proposal, approval, and execution reduces accidental or malicious changes. A timelock gives users time to exit or respond, although it cannot protect users if an attacker can immediately drain assets.

4.1 Voting Models

#### Token-weighted voting

Voting power is proportional to token holdings. It is simple and compatible with financial ownership, but tends toward plutocracy: influence is concentrated in large holders. The model also assumes that token ownership is a suitable proxy for competence, commitment, and affected interests.

#### One-person-one-vote

Each verified person receives one vote. This can reduce wealth concentration but requires identity infrastructure and raises privacy, exclusion, and sybil-resistance questions.

#### Quadratic voting

Under quadratic voting, the cost of expressing intensity rises with the square of the number of votes. If a participant purchases q votes and each vote unit costs c, cost is:

The model assumes a mechanism for funding or crediting participants and is intended to make intense preferences expensive rather than allowing wealth alone to dominate. It is vulnerable if participants create multiple identities or if the funding model is manipulated.

#### Conviction voting

Influence increases with the duration and persistence of support. This can discourage sudden decisions but may favour early participants and make urgent changes difficult.

#### Delegated voting

Participants assign voting authority to representatives while retaining the ability to revoke or change delegation. Delegation improves expertise and participation but creates representative capture and accountability problems.

#### Reputation-based voting

Influence depends on a non-transferable reputation score. Reputation may reflect contribution, expertise, or past performance. It must be carefully designed to avoid permanent exclusion, opaque scoring, and social retaliation.

4.2 Quorum, Thresholds, and Approval

A proposal may require a quorum, meaning a minimum amount of participation, and an approval threshold, meaning a minimum proportion of affirmative votes. If Y is yes votes, N is no votes, and [[MATH>A]] is abstentions, an approval ratio may be calculated as:

Abstentions are excluded from this ratio, while quorum may count all participating votes. Governance documents must state these rules explicitly. A high threshold can prevent harmful changes but create gridlock; a low threshold improves responsiveness but increases capture risk.

4.3 Governance Security Controls

Important controls include:

• proposal delays and minimum discussion periods;
• timelocked execution;
• quorum and approval thresholds;
• vote snapshots that prevent last-minute balance changes;
• delegation and representative disclosure;
• caps or non-linear voting weights where appropriate;
• emergency pause powers with narrow scope;
• independent audits and simulation;
• transparent event logs;
• separation of treasury custody from proposal authorship.

Emergency powers should be limited by time, function, and review. An emergency council that can change all protocol rules is not a minor operational detail; it is a central governance authority.

5. DAOs and Treasury Management

A DAO is an organization whose rules and some operational processes are implemented through blockchain-based contracts. The term does not imply that every decision is decentralized or that the DAO lacks legal obligations. Many DAOs combine token voting, multisignature committees, paid contributors, foundations, service providers, and informal social institutions.

5.1 Treasury Functions

A treasury may fund development, grants, security audits, liquidity, legal services, public goods, and emergency reserves. Treasury management involves four questions:

1. What assets should be held?
2. What liquidity and runway are required?
3. Who may authorize expenditure?
4. How are performance and conflicts reported?

Concentration in a volatile native token may expose the treasury to operating risk. Diversification can reduce volatility but may introduce counterparty, custody, and regulatory risks. Stable-value assets reduce some price exposure but depend on their issuer, collateral, and redemption mechanisms.

A basic runway measure is:

This assumes a stable estimate of liquid value and expenditure. If treasury value and expenses are volatile, scenario analysis is more appropriate than a single point estimate. For example, a treasury valued at $1,200,000 and expected net monthly expenditure of $100,000 has a nominal runway of 12 months. A 30% fall in liquid asset value, with expenses unchanged, reduces runway to 8.4 months.

5.2 Budgeting and Accountability

A sound treasury proposal should identify the problem, requested amount, currency, milestones, responsible persons, deliverables, risks, conflicts of interest, and reporting schedule. Large grants should be staged rather than paid entirely in advance. Milestone-based release creates an opportunity to stop funding when assumptions fail.

Treasuries should publish a balance sheet or asset report, but transparency must not expose personal data or operational security. Disclosure of wallet addresses, vendor identities, or payment timing can create privacy and attack risks.

6. Governance Attacks and Failure Modes

6.1 Plutocratic Capture

Large holders can pass proposals that benefit themselves, particularly when participation is low. The risk increases when voting power is concentrated, quorum is weak, and proposals are complex enough to discourage scrutiny.

Mitigations include delegation, participation incentives, vote caps, longer deliberation periods, minority protections, and separating economic ownership from certain constitutional decisions. Each mitigation has costs and should be evaluated against the protocol’s purpose.

6.2 Flash-Loan and Temporary-Ownership Attacks

If voting power is based on a token balance at the moment of voting, an attacker may borrow a large quantity, vote, and repay it within one transaction or voting period. Snapshot-based voting at a prior block, staking delays, and minimum holding periods reduce this risk. However, snapshots may create their own attack window if an attacker accumulates tokens before the snapshot.

6.3 Vote Buying and Bribery

Voting markets may be explicit, through direct payments, or implicit, through delegated rewards and political alliances. Vote buying is not automatically malicious, but it can convert governance into an extractive market where proposals serve short-term financial interests.

Defences include privacy-preserving voting, conflict disclosure, delegation accountability, conviction mechanisms, and constitutional limits on proposals. Privacy can also make auditing harder, so trade-offs must be recognized.

6.4 Sybil Attacks

A sybil attack occurs when one actor creates many identities to obtain disproportionate influence or rewards. Proof-of-personhood, stake requirements, contribution history, and rate limits can help. Identity systems may introduce surveillance, exclusion, or centralization, so the remedy may be worse than the threat if designed carelessly.

6.5 Smart-Contract and Execution Risk

A legitimate vote may still cause harm if the executed code contains a bug, interacts incorrectly with another protocol, or changes an economic parameter beyond its safe range. Governance security therefore requires code review, formal verification where feasible, constrained parameter ranges, testnet simulation, and operational monitoring.

6.6 Social and Constitutional Attacks

Attackers may exploit panic, misinformation, rushed votes, or disputes over which chain or contract represents the legitimate system. The social layer matters because code cannot determine every question of legitimacy. Clear constitutional principles, communication channels, archival records, and credible dispute procedures reduce ambiguity.

7. Sustainable Participation Models

Participation is often low because voting is time-consuming, proposals are technical, and the private benefit of voting is small relative to the cost. Token incentives can increase turnout but may attract mercenary participants who sell votes or ignore long-term effects.

A sustainable participation model combines:

• accessible proposal summaries and technical appendices;
• delegate specialization and public track records;
• compensation for legitimate review work;
• predictable governance calendars;
• inclusive channels for affected users without tokens;
• education and onboarding;
• transparent conflict-of-interest rules;
• periodic evaluation of decisions and delegates;
• mechanisms for minority voice and dissent.

Participation should be evaluated by quality, not only turnout. Useful metrics include proposal completion rate, time to decision, voter concentration, delegate responsiveness, percentage of votes by active stakeholders, treasury performance against objectives, security incidents, and reversal or amendment frequency.

7.1 Participation Incentives

Possible incentives include voting rewards, reputation, grants, delegated authority, recognition, and access to working groups. Direct payment for every vote may encourage low-information voting and sybil behaviour. Rewards should therefore be linked to verifiable contribution, such as producing an analysis, reviewing code, or completing an approved governance task.

A balanced design distinguishes between voice and ownership. Users affected by a decision may deserve consultation even when they do not own governance tokens. Conversely, token holders may bear financial risk but lack technical competence. Bicameral or multi-stakeholder structures can represent these different interests, though they increase complexity.

8. Illustrative Case: The OpenCompute DAO

The following is a fictional illustrative case.

Background

OpenCompute DAO coordinates a decentralized marketplace for spare computing capacity. It uses a fungible token, OPC, for staking, fee discounts, and governance. Providers stake OPC to signal reliability; users pay for computing services in a stable-value asset. The DAO treasury holds OPC, stable-value assets, and a small reserve of the blockchain’s native asset.

Problem

After launch, the founding team proposed an emissions increase to attract providers. The proposal passed with 8% of circulating voting power participating. Three early wallets controlled 46% of votes, although some tokens were held for investors and advisers. A second proposal sought to transfer a large treasury grant to a development company partly owned by a delegate.

The system also allowed votes to be cast using balances held at the start of the voting period. A market participant argued that a temporary purchase before the snapshot could obtain decisive influence.

Analysis

The DAO faced four connected risks:

1. Low participation made quorum technically achievable but substantively weak.
2. Concentrated holdings created plutocratic capture.
3. The conflict of interest was not disclosed clearly.
4. Token emissions could dilute long-term holders without evidence that provider growth would create sufficient demand.

The treasury committee estimated that the proposal would increase monthly emissions by 150,000 OPC. At a reference value of $0.40 per OPC, the monthly nominal cost was:

This calculation is only a valuation snapshot. It does not account for price impact, future dilution, or whether emissions generate additional fees.

Approach and Solution

The DAO postponed the emissions proposal for a 14-day technical and economic review. It introduced a delegated voting programme, published delegate conflicts, and required a higher quorum for changes to monetary policy. The treasury grant was divided into three milestones, with each release dependent on independently verifiable deliverables.

The DAO also adopted balance snapshots taken before proposal publication, a seven-day voting period, and a two-day timelock. An emergency multisignature group could pause only the marketplace settlement function for 48 hours, after which a governance vote was required.

To evaluate emissions, the DAO tracked provider retention, fulfilled compute-hours, user demand, fee revenue, and security incidents. Rewards were gradually released rather than immediately distributed.

Outcome

Participation increased after delegates published analyses and users received plain-language explanations. The emissions programme was approved at a lower rate with a review condition. The grant was partially released after the first milestone and terminated when the second milestone failed an independent security review. The system did not eliminate concentration, but it reduced the consequences of low-information and conflicted decision-making.

Learning Points

The case demonstrates that governance quality depends on process as well as voting arithmetic. A technically valid vote can still be strategically unsound. Treasury decisions should be staged, conflicts should be visible, and token emissions should be evaluated against measurable outcomes rather than popularity.

9. Regulatory, Ethical, and Professional Considerations

Token systems may implicate securities, commodities, payments, consumer-protection, tax, money-transmission, sanctions, data-protection, and corporate-law regimes. Classification depends on jurisdiction and facts; a label such as “utility token” does not determine legal treatment. Professional teams should obtain qualified legal advice before issuance, public distribution, treasury investment, or operation of financial services.

Ethically, governance designers should consider accessibility, privacy, unequal technical literacy, environmental costs, conflicts of interest, and the consequences of irreversible decisions. Transparency is not identical to publishing every piece of personal information. A responsible DAO discloses material facts while minimizing unnecessary exposure.

AI tools may assist with proposal summarization, anomaly detection, code review, and scenario analysis. They should not receive unchecked authority to vote, execute treasury transfers, or determine eligibility. AI-generated summaries can omit assumptions or reproduce bias. Human accountability, audit trails, and source-linked evidence remain necessary.

10. Best-Practice Design Framework

A practical design review can proceed through the following sequence:

1. Define purpose: identify the network problem and why a token or DAO is necessary.
2. Map stakeholders: include users, contributors, investors, validators, delegates, affected communities, and regulators.
3. Specify rights: distinguish access, payment, security, governance, and asset claims.
4. Model incentives: identify desired behaviour, measurable proxies, costs, and likely gaming strategies.
5. Test distribution: analyse concentration, vesting, unlocks, liquidity, and sybil exposure.
6. Design governance layers: separate routine parameters, constitutional rules, emergency powers, and execution.
7. Protect execution: use audits, timelocks, constrained permissions, monitoring, and recovery procedures.
8. Budget the treasury: set reserves, spending limits, milestones, reporting, and risk tolerances.
9. Measure outcomes: evaluate value created, not merely token price or voter turnout.
10. Review and adapt: conduct post-decision evaluations and revise mechanisms through legitimate processes.

The central principle is proportionality. A small parameter change need not require the same process as a treasury transfer or constitutional amendment. Conversely, convenience should not be used to conceal concentrated authority.

Chapter Summary

Tokens are institutional instruments whose meaning depends on rights, distribution, transferability, and economic design. Standards improve interoperability but do not guarantee utility, security, or legal compliance. Token utility may involve access, payment, security, governance, coordination, or asset claims, and value capture must be distinguished from mere token issuance.

Mechanism design provides a framework for aligning individual incentives with collective objectives. Staking, rewards, penalties, vesting, and grants can support security and contribution, but they may also produce dilution, free riding, proxy gaming, or short-term speculation. Governance systems must therefore define proposal lifecycles, voting eligibility, quorum, approval thresholds, delegation, timelocks, and execution authority.

DAOs combine smart contracts with social, technical, and legal institutions. Treasury management requires liquidity planning, diversification, staged expenditure, reporting, and conflict controls. Major governance threats include plutocratic capture, flash-loan voting, bribery, sybil attacks, smart-contract failures, and social-layer manipulation.

Sustainable participation depends on informed delegation, accessible information, appropriate compensation, minority protections, and evaluation of decision quality. The most robust systems treat decentralization as a design problem rather than a slogan and continuously test whether governance arrangements produce secure, fair, and economically sustainable outcomes.

Key Terms

DAO: An organization using blockchain-based rules and processes for collective coordination.

Delegation: Assignment of voting authority to another participant, usually revocable.

Fungible token: An interchangeable digital unit of the same class.

Governance capture: Control of decision-making by a person or group whose influence is disproportionate or harmful.

Governance token: A token that confers specified participation or voting rights.

Mechanism design: The study of rules that produce desired outcomes under strategic behaviour and private information.

Non-fungible token: A uniquely identifiable token that is not necessarily interchangeable with another token.

Quorum: Minimum participation required for a decision to be valid.

Reputation: A record or score representing perceived contribution, reliability, or expertise.

Slashing: Destruction or confiscation of staked assets following defined misconduct.

Snapshot: A recorded state of balances or eligibility used to determine voting rights.

Sybil attack: Manipulation through creation of multiple identities controlled by one actor.

Timelock: A delay between approval and execution of a governance action.

Token utility: The practical right, capability, or function provided by a token.

Token vesting: A schedule under which allocated tokens become transferable over time or after conditions are met.

Treasury: Assets controlled by a protocol, DAO, or related organization.

Vote buying: Exchange of value for voting influence or a voting outcome.

Voting power: The influence assigned to a participant under a governance rule.

Review Questions

Short Answer Questions

1. Distinguish fungible, non-fungible, and semi-fungible tokens.
2. What is the difference between token utility and value capture?
3. Explain why a timelock can improve governance security.
4. Define a sybil attack and identify one mitigation.
5. Why should treasury grants be released in milestones?

Long Answer Questions

1. Compare token-weighted, one-person-one-vote, quadratic, conviction, and delegated voting. Discuss the assumptions and risks of each.
2. Explain how mechanism-design principles can be applied to staking and contributor rewards.
3. Analyse the major components of a DAO governance lifecycle from agenda formation to post-execution review.
4. Discuss how token distribution, vesting, emissions, and delegation affect decentralization.
5. Explain the relationship between treasury management, governance accountability, and long-term protocol sustainability.

Analytical / Application Questions

1. A DAO has 12,000,000 outstanding tokens. A holder owns 900,000 tokens, and the DAO mints 3,000,000 new tokens to a different group. Calculate the original holder’s post-mint ownership percentage and explain the governance implications.
2. Design a governance system for a decentralized computing marketplace. Specify voting eligibility, quorum, delegation, timelock, emergency powers, treasury controls, and two metrics for evaluating outcomes.
3. A proposal to increase token emissions passes with low participation and benefits a company owned by a major delegate. Analyse the risks and recommend a defensible review and remediation process.

Multiple Choice Questions with Answers

Question 1

Which characteristic best describes a fungible token?

A. Each unit has a unique identity and cannot be exchanged for another unit

B. Units of the same class are interchangeable

C. It can never be transferred between accounts

D. It must represent a legal share in a company

Correct Answer: B. Units of the same class are interchangeable

Question 2

A holder owns 1,000 tokens out of a total supply of 10,000. If 2,000 new tokens are minted to other participants, what is the holder’s new ownership share?

A. 5.00%

B. 8.33%

C. 10.00%

D. 12.00%

Correct Answer: B. 8.33%

Question 3

What is the principal purpose of a governance timelock?

A. To guarantee that every proposal passes

B. To increase token supply automatically

C. To provide time for review or exit before an approved action executes

D. To prevent all forms of smart-contract bugs

Correct Answer: C. To provide time for review or exit before an approved action executes

Question 4

Which attack is most directly reduced by taking a voting-power snapshot before proposal publication?

A. Temporary balance acquisition immediately before voting eligibility is recorded

B. Loss of private keys by a treasury custodian

C. A denial-of-service attack on a website

D. Long-term decline in user demand

Correct Answer: A. Temporary balance acquisition immediately before voting eligibility is recorded

Question 5

Under quadratic voting, if one vote unit costs c, what is the cost of q vote units according to the model presented?

A. c + q

B. c ÷ q

C. c q²

D. q ÷ c²

Correct Answer: C. c q²

Question 6

Which statement best identifies a principal–agent problem in DAO governance?

A. A blockchain records transactions in chronological order

B. A delegate makes decisions for token holders but may have different incentives or information

C. A token has a unique identifier

D. A user pays a network transaction fee

Correct Answer: B. A delegate makes decisions for token holders but may have different incentives or information

Question 7

A treasury has liquid assets worth $1,200,000 and expected net monthly expenditure of $100,000. What is its nominal runway under the simple runway formula?

A. 6 months

B. 8 months

C. 10 months

D. 12 months

Correct Answer: D. 12 months

Question 8

Which practice most directly addresses treasury conflict-of-interest risk?

A. Hiding the identities and interests of proposal authors

B. Releasing the entire grant before work begins

C. Disclosing conflicts and using milestone-based funding

D. Allowing one delegate to execute all payments privately

Correct Answer: C. Disclosing conflicts and using milestone-based funding

Question 9

What is a key limitation of token-weighted voting?

A. It cannot be implemented with smart contracts

B. It may concentrate influence among large token holders

C. It always gives every person one vote

D. It prevents delegation by definition

Correct Answer: B. It may concentrate influence among large token holders

Question 10

Why can rewarding every governance vote create an undesirable outcome?

A. It may encourage low-information voting and sybil behaviour

B. It makes proposals impossible to publish

C. It eliminates all token liquidity

D. It guarantees perfect voter expertise

Correct Answer: A. It may encourage low-information voting and sybil behaviour