Skip to content

Clients ​

Reading metadata is not enough. A client that lists signed extensions and then skips unknown ones will omit CheckPqcPolicy in silence. The node answers Codec error / Bad input data provided to validate_transaction. There is no hint of the two missing bytes.

Read Extrinsics first. This page is the per-client map.

What every client must do ​

  1. Pin genesis 0xe973931eb0041952249c6a5f6d66537ced5acfe7e1334c44b531ddbbffeae7aa.
  2. Pin EVM chain ID 2026. Never 1337, 9911, or 27777.
  3. Emit CheckPqcPolicy as two Option<Vec<u8>> at the start of extra. Ordinary transfer: 0x00 0x00.
  4. Put specVersion and transactionVersion in the implicit payload. Live (2026-11-20): spec 255, tx 12. transactionVersion is what invalidates signatures.
  5. Against the public RPC, pass accounts as SS58 prefix 42 or hex. Prefix 2026 (vx…) is rejected by the live binary. See Accounts and SS58.

subxt ​

Factory subxt aborts UnknownTransactionExtension("CheckPqcPolicy"). Use EmpoorioConfig from cli/src/extensiones.rs. The CLI empooriochain was fixed 2026-09-07: it needs both the extra bytes and the extension declaration.

@polkadot/api ​

Unconfigured @polkadot/api does not work. Measured 2026-10-27 on a local chain, same library, same call balances.transferKeepAlive:

SetupResult
No custom signedExtensionsrejected
With signedExtensions for this runtimeaccepted

Tried on 17.0.2 and 10.13.1. It is not a version problem.

Do not require CheckDormantAccount in metadata against spec 223+. Declaring it extra is harmless; requiring it fails. The live extra starts with CheckPqcPolicy.

The error you get without the two bytes looks like a WASM trap (unreachable). The node log says Codec error. That is the decode path, not a runtime panic.

Python (substrate-interface) ​

Does not know the owned extensions. Build extra by hand. AiloOS has a working path (EmpoorioSubstrateInterface). A real signed extrinsic on this genesis: Reputation::report_positive_event(AiWorkVerified), hash 0x62a63e8b…edc60, block 0x47b4c42e…55f5 (2026-09-12).

EVM clients (MetaMask, ethers, viem, Hardhat) ​

Frontier eth_* methods respond on the same RPC. Configure chain ID 2026. Native DRACMA in MetaMask is the Frontier mapping of the same account, not an ERC-20 contract.

Until the SS58 binary is deployed, native (Substrate) signing and EVM signing fail for different reasons: native for the envelope / SS58 parse, EVM only if the chain ID is wrong.

What still cannot submit from a stock tool ​

  • Polkadot.js Apps against the public RPC with default signed extensions.
  • Any SDK that encodes Substrate extras from a hardcoded Polkadot/Kusama list.
  • vx… addresses on system_accountNextIndex and emp_*.

English technical docs. Marketing lives at empooriochain.com.