Core Concepts

EmpoorioChain is a Substrate-based Layer 1. Its core building blocks look different from an Ethereum-only or program-model-only chain because it runs a native FRAME runtime (compiled Rust modules called pallets) alongside a built-in EVM compatibility layer for Solidity. Read Accounts, Programs, Extrinsics, Transactions, and Fees in that order — each builds on the previous.

Accounts

Every account is identified by an AccountId32 (shown in SS58 format). Solidity contracts on the EVM pallet also get an H160 address, mapped back to a native AccountId32 by a one-way hash.

Programs

Most on-chain logic ships as native pallets compiled into the runtime and upgraded through governance, not deployed per app. Teams that want a permissionless, per-app deploy model use the EVM pallet with Solidity.

Extrinsics

How to call a pallet directly — the api.tx.<pallet>.<call>() pattern used by the real SDKs.

Transactions

A signed extrinsic moves through three states — submitted, included in a block, and finalized by GRANDPA. Only a finalized transaction should be treated as irreversible.

Fees

Fees are paid in native DMS (18 decimals) and calculated from Substrate's weight- and length-based fee model, not a fixed per-signature charge.

Key facts

Consensus: Aura produces blocks; GRANDPA finalizes them. The runtime also compiles BEEFY/MMR for compact bridge finality proofs, but GRANDPA is the primary user-facing finality mechanism. The codebase additionally contains research-stage HotStuff and Bullshark DAG-BFT consensus modules — these are not wired into block production today and should not be described as live.
Two ways to add on-chain logic: (1) native pallets, compiled into the runtime and activated network-wide through a governed runtime upgrade — this is how most of EmpoorioChain's functionality (assets, NFTs, governance, DeFi, storage markets, AI-related pallets, and more) is built; (2) Solidity contracts deployed to the built-in EVM pallet via standard Ethereum tooling (Hardhat, Foundry, ethers.js/viem), for teams that want a permissionless per-app deploy workflow.
ink!/WASM contracts do not work today. pallet-contracts is a declared dependency with a default-on feature flag, but it is not wired into the compiled runtime — there is no Contracts pallet and no Config implementation. Don't assume ink! contract deployment works just because the dependency exists in the source tree.
Fees are native DMS, calculated from transaction weight and length, not a separate "gas token."

This site does not currently publish a specific testnet RPC endpoint, chain ID, or faucet link. As of this writing the project's own operational status docs describe the testnet as mid-remediation (a forensic security purge is in progress after a compromised sudo key was found in the chain specification). Check the EmpoorioChain repository or your SDK's own configuration for a currently-live endpoint before connecting.

Additional Topics

Tokens

Fungible and non-fungible assets on EmpoorioChain.