Tomb / Seigniorage
A coming three-token system for rules-based expansion and contraction around a Pons V2 launch.
Three connected assets
The launch token is the asset traded through Pons V2. A separate share token represents participation in expansion rewards. A bond token is issued through the contraction mechanism and may become redeemable during a later expansion.
- Launch token: the primary Pons V2 market
- Share token: access to boardroom expansion distributions
- Bond token: a claim governed by future recovery conditions
Epochs and the target
The protocol evaluates its configured market target at fixed epochs. The oracle source, observation window, threshold, epoch duration, and maximum response will be immutable or explicitly permissioned and visible before launch.
Expansion
Above the configured target, the protocol may mint a bounded amount of the launch token. The deployment rules determine how much goes to share stakers, reserves, debt repayment, and other disclosed recipients.
Expansion is conditional protocol issuance, not guaranteed yield.
Contraction and bonds
Below the target, holders may exchange launch tokens for bonds, removing those tokens from circulation. Bonds do not guarantee repayment: redemption requires a later qualifying expansion and remains subject to the contract's queue, premium, and reserve limits.
Pons V2 fee funding
Traditional seigniorage forks often depended heavily on emissions and continuing demand. Ponzi Launchpad is designing the system so custom Pons V2 creator fees continuously add external trading revenue to reserves, liquidity, contraction capacity, and disclosed protocol operations.
Each launched system is funded for its own token first, while the configured platform share also contributes to the main Ponzi Launchpad ecosystem.
Why it is coming later
The launch gateway currently supports only Ponzi / OHM and Miner. Tomb requires new share, bond, boardroom, treasury, oracle, and epoch contracts plus a new gateway mode. Peg manipulation, debt accounting, redemption ordering, permission limits, and shutdown behavior must be tested before deployment.
Skip to content