Base fee, not demand
The current burn is tied to a fixed base fee. Whether the network is idle or maxed out, roughly the same small amount leaves supply. Burn barely responds to how much Solana is actually being used.
// solana improvement document 547
SIMD-547 proposes a resource-based fee burn: a share of every fee is destroyed based on the actual compute a transaction consumes, not just the flat base fee. When Solana runs hot, $SOL gets meaningfully more deflationary.
// the proposal
The current burn is tied to a fixed base fee. Whether the network is idle or maxed out, roughly the same small amount leaves supply. Burn barely responds to how much Solana is actually being used.
SIMD-547 burns a portion of fees based on the real computational resources a transaction consumes. Heavier blocks, more compute, more $SOL destroyed. The burn finally tracks genuine network load.
The busier the chain, the harder it burns. Supply pressure turns down when the network is quiet and turns sharply up exactly when demand and activity spike.
// the numbers · SOL burned per day
// how it works
Activity spikes. Blocks fill with heavier, compute-hungry transactions.
Fees are measured against the actual resources each transaction consumes.
A portion of those resource-based fees is permanently destroyed, removing $SOL from supply.
The more the network is used, the more $SOL leaves circulation. Burn scales with real demand.
// signal
Anatoly has signaled support for the direction: linking the burn to real network demand.
Anatoly Yakovenko · Solana co-founder
// why it matters
It directly links $SOL destruction to genuine network activity instead of a fixed fee floor.
When usage spikes, $SOL becomes significantly more deflationary, exactly when it counts.
Stronger burn mechanics through bull-market activity can improve long-term supply dynamics.
Tighter supply through real demand is a structural tailwind for long-term holder value.