Fees

Every EmpoorioChain transaction requires a fee paid in native DMS. Unlike a flat per-signature fee, the fee scales with the transaction's computational weight (how expensive the call is to execute) and its length in bytes — the standard Substrate pallet-transaction-payment model.

Key facts

• Native currency, single gas token: both native extrinsics and EVM (Solidity) transactions settle fees in the same native DMS balance — there is no separate "gas token" concept.
• 18 decimals: 1 DMS = 10^18 of the smallest unit.
• Weight- and length-based, not a flat per-signature charge: OperationalFeeMultiplier is set to 5, and both the weight-to-fee and length-to-fee conversions use an identity function over the runtime's Balance type.
• Real fee estimation before signing: EmpoorioChain's node exposes the standard payment_queryInfo / payment_queryFeeDetails RPC methods, so you can get an accurate fee estimate before submitting a transaction.
• Fee-reduction mechanisms exist but are partially shipped: fee sponsorship (gasless transactions via a paymaster pallet) and up to a 50% discount for verified/reputation-linked accounts are real, compiled pallets, but at least one of them is documented as only partially hardened — see Fee Structure for the caveat.
• Where collected fees go (burn vs. treasury vs. validators) is not yet a finalized, documented policy — don't rely on a specific fee-distribution claim until the project publishes one.