Skip to content
FORTIS AGENT

Buy & Burn

Fees collected, funds allocated, ETH spent and tokens burned are four different numbers. They are kept apart here, and a purchase is never counted as a burn until the burn is verified.

Fees collected
0 ETH
Confirmed escrow claims, measured from FeesClaimed
Allocated to buybacks
0 ETH
Eligible share set by the flywheel at each claim
ETH spent on purchases
0 ETH
Verified buybacks only, net of curve refunds
Tokens purchased
0
Includes purchases awaiting burn verification
Tokens burned
0
Independently verified Transfer logs into 0x…dEaD
Share of supply burned
Token not launched
balanceOf(0x…dEaD) ÷ totalSupply — includes burns by anyone
Successful buybacks
0
Status: burn verified

Cumulative burn

No readings recorded yet.

How it works

  1. 1

    Fees accrue

    Trades of the Fortis token on Pons generate creator fees. Pons sweeps them into its V2 fee escrow.

  2. 2

    Claim

    The fee-collection loop calls FortisFlywheel.claimFees(). The amount received is measured from the transaction, not assumed.

  3. 3

    Allocate

    The flywheel splits each claim once, by a ratio fixed at deployment: the eligible share joins the buyback pool, the rest goes to the treasury.

  4. 4

    Buy

    Within per-transaction, daily, slippage and price-impact limits, the pool buys Fortis on the Pons curve.

  5. 5

    Burn

    The curve delivers purchased tokens straight to 0x…dEaD. A burn counts only after a second RPC re-reads the Transfer logs.

Execution limits

On-chain caps in the flywheel are the hard ceiling. The agent applies these additional limits before it signs anything.

Per transaction
0.1 ETH
Per day
0.5 ETH
Minimum buy
0.001 ETH
Slippage floor
1.5% below simulated quote
Price impact
at most 3%
Minimum curve liquidity
0.5 ETH
Cadence
every 30 minutes
Burn destination
0x…dEaD, fixed in the contract

Buyback history

No buybacks yet. They begin once the token is live, the flywheel holds eligible fees and every limit is satisfied.