Transaction Structure

Summary

A signed extrinsic has a signature (from a native AccountId32 key), a nonce, and a call — the pallet and dispatchable function being invoked, plus its arguments. EmpoorioChain uses the standard Substrate/FRAME extrinsic format, not a account/program-style message with a fixed 1,232-byte packet limit.

Signed extrinsics

Most transactions you build against EmpoorioChain are signed extrinsics: a call wrapped with the information needed to authorize and order it.

  • Signature: an sr25519, ed25519, or ecdsa signature from the sender's native AccountId32 keypair, covering the call and the extra signed data below.
  • Signer: the AccountId32 that signed the extrinsic and pays the transaction fee.
  • Nonce: a per-account counter that increments with each signed extrinsic, preventing replay — the same purpose Ethereum's account nonce serves.
  • Tip (optional): an additional amount a sender can offer on top of the calculated fee to prioritize inclusion.
  • Call: the actual instruction — which pallet, which dispatchable function within that pallet, and the SCALE-encoded arguments for it. A single extrinsic can also be a utility.batch call wrapping multiple inner calls, similar in spirit to a multi-instruction transaction carrying multiple instructions.

This is the standard Substrate/FRAME extrinsic format used by any Substrate-based chain, encoded with SCALE (Substrate's compact binary codec) rather than the Borsh/Bincode formats used elsewhere. For the exact wire encoding, see the Polkadot SDK's extrinsic format documentation — it's generic Substrate architecture, not something EmpoorioChain customizes.

Unsigned and inherent extrinsics

Not every extrinsic in a block is signed by a user. Inherent extrinsics (such as the block timestamp) are inserted directly by the block author without a signature or fee, because their correctness is enforced by consensus rules rather than by a signature check. As an application developer building on EmpoorioChain, the extrinsics you construct and submit will almost always be signed.

Reading a submitted extrinsic

Once submitted, an extrinsic can be looked up by its hash through the standard Substrate JSON-RPC surface (chain_getBlock, state_* storage queries once included) — see Transaction Pipeline for how to tell whether a given extrinsic has only been included, or is actually finalized.

EmpoorioChain also exposes real RPC-based fee estimation before you sign — see Fees.

Is this page helpful?

Tabla de Contenidos

Editar Página
Transaction Structure | empoorio