tangle-network · drewstone · Jun 14, 2026 · Jun 14, 2026
diff --git a/CONTENT_AUDIT.md b/CONTENT_AUDIT.md
@@ -7,13 +7,13 @@ Last updated: 2026-01-19
 | Area | File | Status | Notes / Needed Inputs |
 | ---- | ---- | ------ | --------------------- |
 | Network parameters | `pages/network/network-parameters.mdx` | Updated (testnet + sources) | Mainnet/local addresses still needed. |
-| Token allocation | `pages/network/tokenomics/allocation.mdx` | Updated (tnt-core values) | Need distribution contract addresses by environment. |
-| Inflation model | `pages/network/tokenomics/inflation.mdx` | Updated | Reflects v2 budgeted incentives; verify against current policy. |
+| Token allocation | `pages/network/tokenomics/allocation.mdx` | Updated (100M normalized distribution) | Need distribution contract addresses by environment. |
+| Inflation model | `pages/network/tokenomics/inflation.mdx` | Updated | Reflects 1M TNT year-one treasury-funded budget from Base-mainnet config. |
 | Operator incentives | `pages/network/incentives-operators.mdx` | Updated | Confirm default fee split and operator commission rules. |
 | Developer incentives | `pages/network/incentives-developers.mdx` | Updated | Confirm metric weights and eligibility rules. |
 | Participation credits | `pages/network/points-mechanics.mdx` | Updated (testnet) | Mainnet/local addresses still needed. |
 | Launch page | `pages/network/launch.mdx` | Needs investigation | Reported runtime error; content updated with v2 links. |
-| Governance docs | `pages/network/governance.mdx` | Removed | Replace with new governance system when ready. |
+| Governance docs | `pages/network/governance.mdx` | Added | Reflects Base-mainnet launch params; role addresses still pending. |
 | Differences doc | `pages/network/overview.mdx` | Updated | Content merged; old doc removed. |
 | Use cases | `pages/vision/use-cases.mdx` | Updated | Review for AI alignment and add any missing product references. |
 

diff --git a/components/AllocationTable.tsx b/components/AllocationTable.tsx
diff --git a/pages/network/_meta.ts b/pages/network/_meta.ts
@@ -7,6 +7,7 @@ const meta: Meta = {
   },
   overview: "Protocol Foundation",
   "network-parameters": "Protocol Parameters",
+  governance: "Governance",
   "metrics-and-scoring": "Metrics and Scoring",
   "-- economics": {
     type: "separator",

diff --git a/pages/network/claim-airdrop.mdx b/pages/network/claim-airdrop.mdx
@@ -2,7 +2,7 @@ import { Callout } from "nextra/components";
 
 # TNT Migration and Claims
 
-TNT migration moves balances from the legacy Substrate system and direct EVM allocations into the canonical TNT token on EVM. Claims are verified using a Merkle tree and an SP1 zero-knowledge proof, then distributed with a vesting schedule.
+TNT migration moves eligible legacy Substrate balances into the canonical TNT token on EVM. Claims are verified using a Merkle tree and an SP1 zero-knowledge proof, then distributed with a vesting schedule.
 
 <Callout emoji="⚠️">
   The claim window and unlock parameters are defined by the on-chain migration contract. The claims portal shows the current deadline and vesting configuration.
@@ -16,16 +16,18 @@ Contract sources (GitHub):
 ## Who Can Claim
 
 - **Substrate holders**: Submit a claim using your SR25519 public key and choose an EVM recipient.
-- **EVM recipients**: If you are included in the EVM list, you can claim directly to your wallet.
+- **EVM recipients**: The current normalized distribution has no active EVM allocation. If a future EVM list is added, it will be published in the distribution source files.
 
 ## Vesting Schedule (Default)
 
-- **2% unlocked** immediately at claim time.
-- **98% vested** through a linear vesting contract.
+- **10% unlocked** immediately at claim time.
+- **90% vested** through a linear vesting contract.
 - **12-month cliff + 24-month linear vesting** (36 months total).
 
 Vesting parameters can be updated before the first claim if governance changes them. Always confirm the live settings in the claims portal.
 
+The treasury and foundation buckets use separate launch schedules. See [Token Allocation](/network/tokenomics/allocation).
+
 ## Step 1: Access the Claims UI
 
 1. Navigate to the claims portal: [https://app.tangle.tools/claim](https://app.tangle.tools/claim)

diff --git a/pages/network/governance.mdx b/pages/network/governance.mdx
@@ -0,0 +1,57 @@
+# Governance
+
+Tangle governance uses TNT voting power, a Governor contract, and a Timelock. The Governor decides whether a proposal passes. The Timelock waits before executing the approved calls.
+
+Mainnet governance is configured from `deploy/config/base-mainnet.json`. The role addresses are still launch inputs until the Base-mainnet deployment is finalized.
+
+## Voting Parameters
+
+| Parameter          | Base-mainnet launch value      |
+| ------------------ | ------------------------------ |
+| Voting token       | TNT (`TangleToken`)            |
+| Clock              | Timestamp-based ERC-6372 clock |
+| Voting delay       | 1 day (`86400` seconds)        |
+| Voting period      | 7 days (`604800` seconds)      |
+| Proposal threshold | 100,000 TNT                    |
+| Quorum             | 4% of `getPastTotalSupply()`   |
+| Quorum at 100M cap | 4,000,000 votes                |
+| Vote choices       | Against / For / Abstain        |
+
+Quorum is measured against past total supply. At launch, the cap is 100,000,000 TNT, but much of that supply is locked or undelegated. The low initial quorum is intentional; it keeps governance usable while float is thin. Quorum can be raised later by governance.
+
+## Execution Parameters
+
+| Parameter                 | Base-mainnet launch value                              |
+| ------------------------- | ------------------------------------------------------ |
+| Timelock delay            | 4 days (`345600` seconds)                              |
+| Timelock minimum delay    | 1 day                                                  |
+| Timelock maximum delay    | 30 days                                                |
+| Max actions per proposal  | 10                                                     |
+| Max native value per call | 10,000 ETH                                             |
+| Proposer role             | `TangleGovernor`                                       |
+| Executor role             | `TangleGovernor`                                       |
+| Canceller role            | `TangleGovernor`; guardian Safe recommended for launch |
+
+The timelock is expected to hold admin and upgrade roles on protocol contracts after deployment. That means upgrades, parameter changes, and treasury actions should become delayed governance actions instead of direct deployer actions.
+
+## What Governance Controls
+
+Governance can change protocol parameters, fund incentive pools, manage treasury actions, and upgrade UUPS contracts whose upgrade role is held by the timelock. Examples include:
+
+- payment split updates
+- slashing config updates
+- incentive budget funding
+- staking asset enablement
+- protocol contract upgrades
+
+## Launch Caveat
+
+Do not treat placeholder addresses in `base-mainnet.json` as live governance addresses. Production launch still needs real Safe and Timelock addresses filled into `roles.admin`, `roles.treasury`, `roles.timelock`, and `roles.multisig`.
+
+## Sources
+
+- Governance config: https://github.com/tangle-network/tnt-core/blob/main/deploy/config/base-mainnet.json
+- Decision record: https://github.com/tangle-network/tnt-core/blob/main/deploy/MAINNET-PARAMETERS.md
+- Governor: https://github.com/tangle-network/tnt-core/blob/main/src/governance/TangleGovernor.sol
+- Timelock: https://github.com/tangle-network/tnt-core/blob/main/src/governance/TangleTimelock.sol
+- Token: https://github.com/tangle-network/tnt-core/blob/main/src/governance/TangleToken.sol
diff --git a/pages/network/incentives-developers.mdx b/pages/network/incentives-developers.mdx
@@ -7,9 +7,9 @@ Blueprint developers earn revenue when customers instantiate and run their servi
 
 ## Service Fees
 
-For each service payment, the protocol sends the **developer portion** to the blueprint owner by default. A blueprint’s service manager can return a different payout address (for example, to route revenue into a multisig, splitter, or DAO treasury).
+For each service payment, the protocol sends the **developer portion** to the blueprint owner by default. A blueprint's service manager can return a different payout address (for example, to route revenue into a multisig, splitter, or DAO treasury).
 
-The default protocol split is **20% developer / 20% protocol / 40% operators / 20% stakers** (governance configurable).
+The Base-mainnet launch split is **20% developer / 19.5% protocol / 40% operators / 20% stakers / 0.5% keeper** (governance configurable).
 
 ## Optional TNT Rewards
 

diff --git a/pages/network/incentives-operators.mdx b/pages/network/incentives-operators.mdx
@@ -7,7 +7,7 @@ Operators earn revenue from service usage and optional TNT budgets. This page ou
 1. **Service fees (default split)**
 
    - Fees paid by customers are split across developers, the protocol, operators, and stakers.
-   - The default split is **20% developer / 20% protocol / 40% operators / 20% stakers** (governance configurable).
+   - The Base-mainnet launch split is **20% developer / 19.5% protocol / 40% operators / 20% stakers / 0.5% keeper** (governance configurable).
 
 2. **Optional TNT incentives (pre-funded)**