Liquidity fragmentation is what happens when an asset exists as three wrapped versions on three venues and none of them is deep. This post is about one design decision in EmpoorioChain that removes a whole class of it — and about the one wrapped DMS that does exist, so nobody mistakes it for liquidity.
The decision
EmpoorioChain runs Frontier, so it has an EVM. Many Substrate chains with an EVM expose the native token to Solidity through a bridge precompile that mints an ERC-20 representation — a wrapped native token — and locks the native balance. Two balances, one asset, fragmented from day one.
EmpoorioChain does not do that. The EVM view of DMS is the native balance: an H160 address maps deterministically to a native account, and pallet-evm reads and writes pallet-balances directly. A former DMS-bridge precompile at 0xEB was retired for exactly this reason; the engineering doc records DMS's canonical liquidity lives in the runtime.
Consequences:
- A DEX pool in
pallet-dexand a Uniswap-style pool deployed in Solidity on chain id 2026 both draw from the same DMS supply. There is no wDMS-on-EmpoorioChain. - A user can receive DMS natively and spend it from MetaMask without any conversion step.
- Eoonia shows one balance with two addresses.
What still fragments
- Native assets versus ERC-20 contracts. DUSD is a native asset in
pallet-stablecoins; a Solidity ERC-20 "USD" token deployed through Frontier would be a different asset. The0x1155and0x72precompiles expose native assets to Solidity so a contract need not deploy its own; a project that deploys anyway creates a second asset. - Other chains. DMS on any other chain is a wrapped representation with collateral — or, today, without.
The wrapped DMS that exists
On the Sepolia Ethereum testnet there is a wDMS ERC-20 with a total supply of about 215 million and a bridge escrow of zero. It represents no locked DMS; an attempt to redeem would revert. It was a test artefact of an earlier bridge design. In August 2026, 25 documents across the ecosystem that described it as available for Ethereum and BSC were corrected, and the price service returns 0 for it. Its final disposition — retire, convert to an allocation registry, or back with real DMS — is an owner decision recorded as open. It is not liquidity and no page here will treat it as such.
The bridge that would matter
A real Ethereum ↔ EmpoorioChain bridge was evaluated in May 2026 (Snowbridge selected as the candidate, aligned with the chain's BEEFY finality proofs). It is not built; the mainnet gate lists a working testnet bridge as blocking. When it exists, DMS on Ethereum will be a collateralised representation — and, by design, the only one.
Why this page exists
The previous version described a stablecoin issuer's cross-chain mesh unifying billions in liquidity. EmpoorioChain has unified nothing at that scale; it has made one architectural choice that prevents its own native token from fragmenting inside its own chain. That is a smaller claim and a true one.
Based on 02_CORE_SYSTEMS/EVM_AND_L2.md, CONTRATOS_EVM.json (wDMS note), BRIDGE_EVALUATION.md and MAINNET_GATE.md.