Forge.
← Learn
Liveproduct· 3 min read· #forge#emissions#rewards#merkle

FORGE emissions are live: epoch clock, claims, and agent prompts

Weekly $FORGE epochs on Base mainnet — read the Tokenomics and Portfolio clocks, understand Merkle claims, and run MCP get_forge_rewards / claim_forge.

Last updated: May 28, 2026 · Published 2026-05-28

Forge Treasury smart contracts completed an external security review (May 2026). Yield is variable and not guaranteed. Residual risk remains — read Risks & Disclosures before depositing USDC or integrating MCP tools.

Weekly $FORGE emissions are live on Base mainnet. Hold fUSDC (Core vault shares) during each epoch, claim your slice after the Merkle root publishes, and track the countdown on Tokenomics and Portfolio. This is a usage subsidy — not USDC vault yield. Read FORGE emissions vs vault yield and Risks & Disclosures before quoting APY externally.

FORGE may be illiquid. No guaranteed APY, price targets, or combined “USDC + FORGE” marketing numbers. Contracts completed external security review (May 2026). Emissions are variable and depend on TVL share at weekly snapshot.
Weekly FORGE emissions live on Forge Treasury — 9.6M FORGE per epoch on Base mainnet
Featured — weekly $FORGE epoch clock on forgetreasury.com/tokenomics

Where to see epoch data on the site

Tokenomics — protocol clock

Open Tokenomics and scroll to Emission schedule. The Weekly $FORGE emissions card shows the current epoch number, a live countdown to the next epoch boundary, this week’s pool size (~9.6M FORGE in the front-loaded phase), UTC window, local timezone, epoch progress bar, and whether the Merkle root is published (“claims open”). Data refreshes from chain every 60 seconds; the countdown ticks in your browser.

Forge Tokenomics page showing Epoch 0 weekly FORGE emissions countdown, 9.6M FORGE pool, and claims open badge
Tokenomics epoch clock — countdown, weekly pool, and claim status

Portfolio — wallet view

Open Portfolio and enter your agent EOA. Example: `/portfolio?address=0x919789a083fd157D329C983e37086f843da5BeCe`. You get the compact epoch clock plus Claimable FORGE in the KPI row (from `RewardDistributor` + published manifest), Core/Middle vault NAV, and subgraph-backed activity. Middle vault shares do not count toward FORGE epochs today — Core fUSDC only.

Forge Portfolio page with weekly FORGE emissions epoch clock and wallet lookup
Portfolio — epoch clock with per-wallet context (claimable FORGE appears in KPI row below on live lookup)

How weekly emissions work

ConceptDetail
Schedule600M FORGE over 24 months; ~40% front-loaded in first 6 months
Epoch length7 days from `emissionStart` on RewardDistributor
EligibilityProportional to Core vault (fUSDC) shares at weekly snapshot
On-chain publishOwner sets `merkleRoots(epoch)` — one root hash per week
Off-chain proofsJSON manifest at forgetreasury.com/rewards/epoch-N.json
ClaimSeparate tx: `claim(epoch, account, amount, proof[])` — not automatic on deposit
Epoch mechanics (Base mainnet)

Think of each week as a fixed FORGE bucket split among Core depositors. When the epoch ends, Forge publishes a Merkle root on-chain and a manifest with proofs. You claim whenever you want after that — there is no narrow claim window. Deposit before the snapshot to be included; deposit after the snapshot counts toward the next epoch.

Weekly Merkle root → optional claim_forge. Separate from vault NAV.

Merkle claim flow — separate from ERC-4626 share price

MCP tools: check and claim

  • Connect production MCP: `https://mcp.forgetreasury.com/mcp` (see Docs).
  • get_forge_rewards — returns `claimableForge`, `unclaimedEpochs[]`, and manifest URLs.
  • claim_forge — builds unsigned `claim` calldata; proof auto-fetches from manifest when omitted.
  • If claim fails, MCP returns a structured `code` (`NO_ALLOCATION`, `ROOT_NOT_PUBLISHED`, `ALREADY_CLAIMED`, etc.) with a human-readable reason.

Sample agent prompt (weekly claim cron)

You are my Forge Treasury rewards agent on Base mainnet (chain ID 8453). (1) Call get_forge_rewards for AGENT_EOA. (2) If claimableForge is 0, report the epoch countdown from forgetreasury.com/tokenomics and exit. (3) For each row in unclaimedEpochs, call claim_forge with epoch + agentAddress — omit proof. (4) If claim_forge returns an error, print code + message; do not invent proofs. (5) Sign and broadcast each claim tx from AGENT_EOA; verify FORGE on Basescan. (6) Never combine FORGE with USDC vault APY. Replace AGENT_EOA with your wallet.

Contracts & manifests

  • FORGE token: `0xF50469247B3F1BB86d226bB2b333ca015A2b8470`
  • RewardDistributor: `0x44fE9676008154Eb461736F482873Ae7E3F87923`
  • Core vault (fUSDC): `0x2C9a3922b426005B979FDD1A8F43Eb61B309193B`
  • Epoch 0 manifest: forgetreasury.com/rewards/epoch-0.json

Deep dive on Merkle mechanics: Claim FORGE Merkle rewards — agent guide. Allocation chart and 24-month curve: Tokenomics.

External resources

Primary protocol documentation and data sources. Forge is not affiliated with these projects; links are for education only.

Related reading

Share this article

Draft copy for social posts — review before publishing. URL: https://forgetreasury.com/learn/forge-emissions-live-weekly-epochs

Open Graph / preview card

FORGE weekly emissions live on Base Epoch clock on /tokenomics, claimable FORGE on /portfolio, MCP claim_forge calldata. Variable subsidy — not USDC yield. /risks https://forgetreasury.com/learn/forge-emissions-live-weekly-epochs

Twitter / X

$FORGE weekly emissions are LIVE on Base — 9.6M FORGE/epoch, epoch clock on /tokenomics, claim via MCP. Not USDC yield. https://forgetreasury.com/learn/forge-emissions-live-weekly-epochs · /risks

LinkedIn

Forge Treasury published weekly $FORGE Merkle epochs on Base mainnet with a live countdown on Tokenomics and per-wallet claimable balances on Portfolio. Agents claim via MCP get_forge_rewards and claim_forge — separate from USDC vault NAV. Externally reviewed; variable subsidy: https://forgetreasury.com/learn/forge-emissions-live-weekly-epochs

MCP integration docs →Live vault stats →Risks & disclosures →