The public discussion that led to this WFC is in the Polkadot Forum: "Proposal: Introduce a Permanent Burn Account for Polkadot".
"blake_256" in the on-chain text refers to blake2_256 — BLAKE2b with a 256-bit output.
1. The address derived from blake_256("POLKADOT_BURN_ACCOUNT") — the 32-byte account ID encoded under Polkadot's SS58 rules as 16Xvw6oiEcn1GWAU61WheW3xn6jA4aNQTk1nqpPDPWuwTg4q — is confirmed as the canonical Polkadot burn account.
2. The burn required by WFC #1926 shall be executed by transferring DOT to this address.
3. Any account — holders, projects, DAOs, exchanges — may voluntarily send DOT to this address. The address has no private key, and no one can ever sign a transaction from it.
WFC #1926 passed in August 2026. It commits the community to removing the DOT revenue from JAMKB sales out of circulation for good. A burn needs a destination. This WFC does one thing: it confirms that destination.
A protocol-level burn — deleting DOT from the total issuance directly — conflicts with the monetary model the community adopted in Referendum 1710. The issuance schedule converges on the 2.1 billion DOT cap along a fixed curve: whatever the protocol burns, the issuance formula mints back, so the burn quietly returns; and if it does not mint back, the cap's math breaks. A keyless account sidesteps both. DOT sent to it leaves circulation for good, while the protocol's issuance accounting stays unchanged and the schedule runs as before. Protocol-internal slashes, dust and similar flows keep being handled under the Dynamic Allocation Pool (DAP) framework; this WFC does not change where they go.
No runtime upgrade is needed. Anyone can verify the address by computing blake_256("POLKADOT_BURN_ACCOUNT") themselves. W3F publicly endorsed this implementation path in the comments of the #1926 referendum: "We would prefer to see this DOT locked in an unspendable account."
Beyond carrying out the #1926 burn, the address has wider uses. Exchanges that want to burn tokens, projects that want to remove surplus treasury funds, anyone who wants to take their own DOT out of circulation permanently — all of them can choose to use this address. It is simply a public, verifiable standard destination, so nobody has to rely on scattered unofficial "burn addresses" that no one can check.
This WFC builds on: the forum thread #18280 (initiated by ultracoconut; the address derivation proposed by Bastian Köcher; Jonas's argument on compatibility with Referendum 1710's issuance schedule); WFC #1926 (passed in August 2026) and its referendum page comments (W3F's public endorsement); and Referendum 1710 (the 2.1 billion DOT cap and the Pi issuance schedule).
As with any Wish for Change, this is a signal of community sentiment, not a protocol change in itself; if approved by ballot, a future technical implementation is bound by it.
Polkadot has a special account called the burn account. Everyone can send DOT coins there. Nobody can take coins out because no one has the key. It is a safe, fixed place to burn tokens forever. The address is made from a known code, so people can check it. This helps remove coins from circulation without breaking Polkadot's rules. Projects, exchanges, and people can use it too.
The public discussion that led to this WFC is in the Polkadot Forum: "Proposal: Introduce a Permanent Burn Account for Polkadot".
"blake_256" in the on-chain text refers to blake2_256 — BLAKE2b with a 256-bit output.
1. The address derived from blake_256("POLKADOT_BURN_ACCOUNT") — the 32-byte account ID encoded under Polkadot's SS58 rules as 16Xvw6oiEcn1GWAU61WheW3xn6jA4aNQTk1nqpPDPWuwTg4q — is confirmed as the canonical Polkadot burn account.
2. The burn required by WFC #1926 shall be executed by transferring DOT to this address.
3. Any account — holders, projects, DAOs, exchanges — may voluntarily send DOT to this address. The address has no private key, and no one can ever sign a transaction from it.
WFC #1926 passed in August 2026. It commits the community to removing the DOT revenue from JAMKB sales out of circulation for good. A burn needs a destination. This WFC does one thing: it confirms that destination.
A protocol-level burn — deleting DOT from the total issuance directly — conflicts with the monetary model the community adopted in Referendum 1710. The issuance schedule converges on the 2.1 billion DOT cap along a fixed curve: whatever the protocol burns, the issuance formula mints back, so the burn quietly returns; and if it does not mint back, the cap's math breaks. A keyless account sidesteps both. DOT sent to it leaves circulation for good, while the protocol's issuance accounting stays unchanged and the schedule runs as before. Protocol-internal slashes, dust and similar flows keep being handled under the Dynamic Allocation Pool (DAP) framework; this WFC does not change where they go.
No runtime upgrade is needed. Anyone can verify the address by computing blake_256("POLKADOT_BURN_ACCOUNT") themselves. W3F publicly endorsed this implementation path in the comments of the #1926 referendum: "We would prefer to see this DOT locked in an unspendable account."
Beyond carrying out the #1926 burn, the address has wider uses. Exchanges that want to burn tokens, projects that want to remove surplus treasury funds, anyone who wants to take their own DOT out of circulation permanently — all of them can choose to use this address. It is simply a public, verifiable standard destination, so nobody has to rely on scattered unofficial "burn addresses" that no one can check.
This WFC builds on: the forum thread #18280 (initiated by ultracoconut; the address derivation proposed by Bastian Köcher; Jonas's argument on compatibility with Referendum 1710's issuance schedule); WFC #1926 (passed in August 2026) and its referendum page comments (W3F's public endorsement); and Referendum 1710 (the 2.1 billion DOT cap and the Pi issuance schedule).
As with any Wish for Change, this is a signal of community sentiment, not a protocol change in itself; if approved by ballot, a future technical implementation is bound by it.
Threshold
Threshold