How Dracma connects to the Empoorio ecosystem, protocol standards, and the technology we ship — without listing alliances we have not announced.
Empoorio ecosystem
Native products that settle in Dracma (DMS) on EmpoorioChain — built and operated by Empoorio.
Protocol standards
Substrate/FRAME runtime conventions and standard JSON-RPC interfaces — not proprietary lock-in.
- FRAME pallets
Substrate / FRAME runtime
DMS is compiled directly into the EmpoorioChain runtime as the native currency — not deployed as a smart contract on top of it.
- AccountId32 · SS58
SS58 accounts
Every account is a Substrate AccountId32, normally shown in SS58 format — the same account model used by Polkadot and Kusama chains.
- pallet_transaction_payment
Weight-based fees
Fees scale with computational weight and transaction byte length, not with a fixed "gas price" — standard Substrate `pallet_transaction_payment`.
- pallet-evm (Frontier)
EVM compatibility
A built-in EVM pallet exposes an Ethereum-JSON-RPC-compatible endpoint for Solidity tooling (Hardhat, Foundry, ethers.js) — both settle fees in the same native DMS balance.
- pallet_transaction_payment_rpc
Real fee estimation
Standard Substrate RPC (`payment_queryInfo` / `payment_queryFeeDetails`) gives real fee estimates before signing.
- @polkadot/api · subxt
Client tooling
Compatible with `@polkadot/api` / polkadot{.js} tooling on the JS side and `subxt` on the Rust side — standard Substrate client libraries, not a bespoke SDK.
Programming languages
Languages behind the EmpoorioChain runtime, public SDKs, and client integrations across the Empoorio stack.
Built with
Frameworks and infrastructure behind the public Dracma site and chain runtime.
Strategic partners
External security, legal, capital, and enterprise alliances — listed only when agreements are public.
Coming soon
We do not list external strategic alliances until agreements are public. Security audits, exchange listings, market makers, and infrastructure vendors will appear here when announced.
Contact partnerships






