PRE-LAUNCHThe contracts are not deployed yet, so there are no markets to show.
Supply only goes down

$SEND

One billion tokens, minted once, with no mint function and no owner. Protocol revenue is used to buy SEND on the open market and send it to the burn address. There is no staking, no emissions, and no treasury unlock — the only thing that ever happens to the supply is that some of it stops existing.

$SEND is not deployed yet

There is no token, no supply, and nothing burned. The mechanics below describe what the contracts do — they are read from the code, not from activity that has not happened. Burn figures will appear here only once there are real burns to report.

Where the money comes from

Two revenue lines, both routed by contract rather than by promise.

Launch feeΞ0.002 per launch
Buy & burn 50%Protocol 50%
Trading fees1% of every swap, forever
Creator 70%Buy & burn 24%Protocol 6%

The burn's half of the launch fee is capped in the contract: the owner can raise the burn share but can never push it below 50%. The creator's 70% is fixed per launch at the moment it is created, so changing the split later cannot reach backwards into a market that already exists.

How the burn runs

The owner triggers it. Nobody, including the owner, can point it somewhere else.

  1. 1
    Revenue accumulates

    Launch fees and the protocol's cut of trading fees land in the burner contract as native ETH. Nothing is wrapped; Uniswap v4 pairs against ETH directly.

  2. 2
    The owner calls buybackAndBurn()

    This one call is owner-gated, and that is a real limitation rather than a preference. A permissionless burn has to derive its own minimum output or a searcher would call it with no floor and sandwich the spend — and deriving one needs an oracle. Uniswap v4 has no built-in observations; they are a hook's job. So the minimum is supplied per call instead, and supplying it is gated.

  3. 3
    The floor is set per call

    Whoever sends the transaction quotes the pool immediately before submitting and sets the minimum tightly. If the swap cannot meet it, the whole call reverts and the revenue stays where it was.

  4. 4
    Output goes straight to 0x…dEaD

    The swap's recipient is the burn address itself. The tokens never touch a wallet the protocol controls.

There is no withdraw. The burner has no function that moves ETH or SEND out to anyone — the owner included. Its rescue function refuses both. Once revenue arrives, buying and burning is the only way it can leave, and the swap’s recipient is a hard-coded burn address. Being able to trigger the burn is not the same as being able to take the money.

Burning reduces supply. It does not guarantee a price increase, and it is not a yield, a dividend, or a claim on revenue. $SEND carries no rights to anything and may be worth nothing.