Ember: Buy, then burn.

Explanation — not permission to act

Buy-then-burn describes a mechanism. An allocation or pending queue is not proof of a purchase or burn.

The mechanics and diagram include historical specification design. Current gates and finalized evidence govern; configuration is not availability or execution proof.

The EMBER share buys the coin through its own pool, whichever kind it trades on, and sends what it buys to the burn address, with burn history linked to transactions. A purchase waits whenever estimated price impact exceeds the configured ceiling or no route exists; waiting is the expected safe outcome, not a failure. Ember is separate from perp-profit buybacks, which come from realized desk profit rather than the router.

Buy, then burn

The EMBER design buys through the coin’s own pool and sends acquired units to the burn address. This is distinct from realized desk-profit buybacks.

Waiting is a valid outcome

No route or excessive estimated impact can defer a purchase. Waiting is not evidence of a completed trade or a guarantee of eventual execution.

Verify burn evidence

Check the mint, native quantity and finalized transaction in the public burn ledger. Burn activity does not guarantee price appreciation.

Ember purchase path with its wait condition.
  1. EMBER share

    Router allocation accumulates.

  2. Impact check

    Wait if impact exceeds the ceiling or no route exists.

  3. Own-pool buy

    Bought through the coin's own pool only.

  4. Burn

    Sent to the burn address and recorded.

Practical next reading

Inspect burn history · Understand allocation coverage

The numbers that bound it.

Live configuration is not embedded in this guide. No values are shown rather than guessed. Local settings are not chain, provider or release evidence. Spec defaults are not provider proof.

  • EMBER_MAX_IMPACT_BPS

Platform spec reference

Historical source summaries, not a statement of current enforcement.

Applicability and precedence · §12 Ember