Tokenized Allocation Mechanisms (TAM)
Purpose: Serve as the overview and navigation hub for the TAM framework—explaining what TAM is, who should use it, and which pages to read next based on your goals.
Audience: Protocol teams, DAO operators, and researchers building on-chain governance and funding mechanisms.
Level: Intermediate
Source of truth: TAM design in
[email protected]; deployment addresses, where needed, come from the Deployed Addresses page.Use this page when: You are new to TAM and need a high-level orientation, or you want to navigate to specific TAM pages based on your use case (understanding the model, building a concrete mechanism, or finding smart-contract references).
Do not use this page for: Deep dives into TAM architecture, hook-specific policy design, or quadratic funding math. Start here, then move to Introduction to TAM, TAM: Architecture, or TAM: Mental Model & Lifecycle.
Tokenized Allocation Mechanisms (TAM) let a community register voters, create proposals, and allocate funds with a rigorously defined on-chain lifecycle. TAM follows the Yearn-style tokenized pattern: one shared implementation owns the state machine and accounting, while minimal mechanism contracts plug in policy via hooks.
Start here if you want to build
| I want to... | Start here | Then read... |
|---|---|---|
| understand the overall TAM model | Introduction to Tokenized Allocation Mechanisms | TAM: Architecture, TAM: Mental Model & Lifecycle |
| build a concrete mechanism | TAM: Writing a New Funding Mechanism | Reading the Smart-Contract Reference |
| find the key reference pages | Reading the Smart-Contract Reference | BaseAllocationMechanism, TokenizedAllocationMechanism, AllocationMechanismFactory |
Pages in this section
- Introduction to Tokenized Allocation Mechanisms
- TAM: Architecture
- TAM: Mental Model & Lifecycle
- TAM: Writing a New Funding Mechanism (1-person-1-vote)