The transaction
A native balances transfer, built by hand with the correct extrinsic envelope — including the two EmpoorioChain-specific signed extensions — submitted to rpc.testnet.empooriochain.org, included in a block, finalized by GRANDPA, and it moved a balance. Verified against spec 213.
Why it took 102,912 blocks
Not because the chain rejected transactions. Because no client had ever built one correctly. Runtime 208 placed CheckPqcPolicy (two bytes when empty) and CheckDormantAccount (zero bytes) at the front of SignedExtra; every library that did not know them omitted them, every subsequent byte shifted, and the node answered Bad input data provided to validate_transaction. For weeks that error was read as five unrelated bugs.
What changed that day
- The envelope was documented byte by byte (
FORMATO_DE_EXTRINSECOS.md), with the example transaction that worked. - Eoonia, the Dart SDK and the Rust SDK were confirmed to encode it; Polkadot.js does so from metadata.
- The metric signed transactions per day went onto the dashboard — the number that had been zero and invisible.
What followed within a week
Eoonia's 35 verified native operations. The first governance proposal. The first EVM transaction accepted (runtime 211). The first DID. The first DEX swap. None of them could have happened before this one.
Why it counts as a "first" and not a bug fix
Because a chain's real launch is its first user transaction, not its genesis block. EmpoorioChain's genesis was 31 August; its launch, by that measure, was 7 September.
The winners this page used to name
Were another ecosystem's inaugural hackathon. EmpoorioChain's inaugural event is unannounced. Its first real transaction is above, and it was not a contest — it was a two-byte field, found by someone who insisted on running the chain instead of reading the tests.
Based on FORMATO_DE_EXTRINSECOS.md (2026-09-07).