Skip to content

Extrinsics ​

EmpoorioChain adds one owned extension to the extrinsic envelope. That changes the bytes you must send versus stock Substrate, and a client that skips them fails with a generic Codec error — Bad input data provided to validate_transaction — with no hint of what was missing.

This is the first page a builder should read. The public testnet once ran 102,912 blocks with zero signed transactions because every client omitted two bytes. After this page: Clients, then Accounts and SS58.

Applies from spec_version 223 (transaction_version 7). Live chain (2026-11-20): specVersion 255, transactionVersion 12. The extra bytes did not change with those bumps.

SignedExtra, in order ​

#ExtensionBytes in extraImplicit
1CheckPqcPolicy2 if both fields are None()
2CheckNonZeroSender0()
3CheckSpecVersion0u32 spec_version
4CheckTxVersion0u32 transaction_version
5CheckGenesis0[u8; 32] genesis hash
6CheckEra1 (immortal) or 2 (mortal)[u8; 32] block hash
7CheckNonceCompact<u32>()
8CheckWeight0()
9ChargeTransactionPaymentCompact<Balance> (tip)()

The difference versus stock Substrate is exactly this: two extra bytes at the start of extra. The implicit payload — what is signed but not sent — does not change: the owned extension contributes ().

CheckDormantAccount sat between 1 and 2 from spec 208 to 222 (zero bytes) and left with StateRent in 223. Declaring it extra is harmless; requiring it in metadata fails against 223+.

CheckPqcPolicy ​

rust
pub struct CheckPqcPolicy<T> {
    pub pqc_signature: Option<Vec<u8>>,
    pub batch_receipt: Option<Vec<u8>>,
}

It is not an empty struct. The two Option<Vec<u8>> are encoded, and it is the first extension. Omitting it shifts every later byte.

For an ordinary transfer with no post-quantum policy, both fields are None:

0x00 0x00

A client that does not know the extension emits zero bytes there. The node reads the era 0x00 as the first Option, and everything after that is misaligned.

Implicit = () is not the bug. Implicit is signed-not-sent. The break is in extra, which is sent. Fixing it does not require migrating to extrinsic v5. Emitting two bytes is enough. The runtime accepts extrinsic format v4 and v5.

When a account has an active PQC policy, the fields carry data. Rejections:

CodeMeaning
InvalidTransaction::Custom(121)Policy requires a registered PQC key
InvalidTransaction::BadProofMissing required PQC signature
InvalidTransaction::Custom(123)Missing required batch receipt
InvalidTransaction::BadSignerMissing classical signature
InvalidTransaction::Custom(124)pqc_signature over MaxSignatureLen
InvalidTransaction::Custom(125)batch_receipt over MaxBatchReceiptLen

An account with no PQC policy passes with None/None.

What is signed ​

payload = call ++ extra ++ implicit

implicit = u32(spec_version)
         ++ u32(transaction_version)
         ++ genesis_hash (32)
         ++ block_hash (32)   // genesis hash if immortal

If the payload exceeds 256 bytes it is signed as its Blake2b-256, as in stock Substrate.

Assembled extrinsic:

Compact(length) ++ 0x84 ++ MultiAddress ++ sig_type ++ signature(64) ++ extra ++ call
                   │        │              │
                   │        │              └─ 0x00 Ed25519 · 0x01 Sr25519 · 0x02 Ecdsa
                   │        └─ 0x00 + AccountId(32) for Id
                   └─ version 4 with the signed bit

A/B that isolates the cause ​

Same node, same call, same key, same nonce. Only the two bytes change:

extra sentResult
00 00 + era + nonce + tipAccepted, destination balance rises
era + nonce + tip (no two bytes)Rejected: Codec error

If removing the two bytes does not change the result, they were already being sent another way.

Example extra for immortal, nonce 0, tip 0:

00 00     CheckPqcPolicy { None, None }
00        CheckEra: immortal
00        CheckNonce: Compact(0)
00        ChargeTransactionPayment: Compact(0)

Five bytes. Without the owned extension it would be three (000000).

Clients ​

ClientStatus
subxt with EmpoorioConfig (cli/src/extensiones.rs)Verified — factory subxt aborts UnknownTransactionExtension("CheckPqcPolicy")
CLI empooriochainFixed 2026-09-07 (needs both pieces: extra bytes and extension declaration)
@polkadot/api unconfiguredDoes not work — needs custom signedExtensions
substrate-interface (Python)Does not know the extensions; build extra by hand

Reading metadata is not enough. A client that lists extensions and then skips unknown ones will omit CheckPqcPolicy in silence. You must emit the two bytes.

transactionVersion 12 is what invalidates signatures. specVersion can rise without breaking a correctly built envelope.

English technical docs. Marketing lives at empooriochain.com.