A transaction on EmpoorioChain — called an extrinsic in Substrate terminology — is a signed request to execute one or more calls against a pallet. Once submitted, it moves through a well-defined lifecycle before it should be treated as final.
Transaction Structure
The parts of a signed extrinsic — signature, nonce, and the call itself — and how fees relate to them.
Transaction Pipeline
The three real states a transaction moves through: submitted, included, finalized — and why "included" isn't the same as "final."
Key facts
- Three states, not one confirmation:
submitted→included(in a block produced by Aura) →finalized(GRANDPA has finalized the block). An included-but-not-yet-finalized transaction can, in principle, still be reorganized away — don't present it to a user as final. - Signed with sr25519, ed25519, or ecdsa — not a quantum-resistant signature scheme. EmpoorioChain does have separate infrastructure for post-quantum key registration on accounts, but that's distinct from, and doesn't currently change, how ordinary transactions are signed.
- Fees are paid in native DMS, calculated from the transaction's weight and byte length — see Fees.
- Atomic execution: if a call fails, its state changes revert, but the transaction fee is still charged.
Is this page helpful?