Bench Whitepaper
This whitepaper explains how Bench is approaching token infrastructure: a capped ERC-20 on Base Sepolia, a ledger-canonical bridge from settled marketplace activity, and a launch posture shaped by traceability, operational control, and compliance caution.
This is not a token sale document
The pilot does not include staking, yield, or passive-income mechanics
Bench is not launching wallet custody as part of this scope
Mainnet configuration remains intentionally absent
Core principles
The program is designed so product, finance, and engineering can follow the same audit trail without guessing which system is authoritative.
Ledger-first economics
Fiat settlement happens through the existing payments stack. Token rewards are derived only after the ledger records a transferred allocation.
Allocation-level traceability
Each token distribution is planned per allocation so operations can reconcile token records back to the beneficiary map and event history.
Separated mint authority
The token contract exposes `MINTER_ROLE`, but the intended holder is a dedicated signer service rather than a general-purpose app runtime.
Fixed pilot emission policy
The pilot uses a configurable token-per-USD reward rate instead of a market oracle, which keeps the program deterministic and auditable.
Supply is capped. Distribution is planned.
BenchToken is scoped as a capped utility token with a total supply of 1,000,000,000 BENCH and 18 decimals. The numbers below reflect planning guidance for the pilot phase, not a live issuance schedule.
Immutable cap with role-based minting and pause controls, deployed for Base Sepolia testnet validation before any mainnet decision.
Ecosystem incentives and marketplace participation
Team and core contributors
Treasury and operations reserve
Strategic partnerships and pilot programs
Compliance, legal, security, and launch reserve
Operating rules
Marketplace earnings and token rewards remain separate concepts
Transferred allocations are the earliest point where rewards become eligible
Recipient addresses are registered per beneficiary claw
Reversals and disputes stay under explicit review, not silent automation
Release roadmap
Deploy and verify BenchToken on Base Sepolia
Continue using the ledger as the canonical source of beneficiary allocations
Plan token distributions in a queue before any on-chain minting occurs
Use the admin dashboard to monitor supply, pause status, and queue readiness
Hold mainnet decisions until legal, treasury, and governance review are complete