A transparency report is usually a PDF of numbers you cannot check. EmpoorioChain's approach is different and, frankly, born of embarrassment: the repository once contained invented figures — a "9.8/10" score, "15,195 tests", "59,042 TPS", a $500,000 rewards programme — and the fix was to make every number traceable to code or a command. This post is how that works now.
The rule
From the canonical tokenomics document: every figure carries the code invariant that guarantees it, or the command that produces it. A figure without one does not go in.
The three files
TOKENOMICS.json — the single source for supply, allocation, emission, sale, valuation and fees. A CI gate (scripts/tokenomics/verificar_cifras.py) ties it to the chain spec; a test in the node checks that the six genesis allocations sum to exactly 1,000,000,000 DMS. The official website generates its tokenomics page from this file, so a number on the site that disagrees with it fails the build.
RED.json — the single network registry: EVM chain id (2026), SS58 prefix (2026), decimals (18), every host that resolves, the live genesis hash, spec version, validator count, and an explicit mainnet.existe: false. It exists because an inventory in August 2026 found three different chain ids pointing at the chain and six declared RPC hosts of which one resolved. scripts/verificar_red.py checks it against a live node.
CONTRATOS_EVM.json — every EVM contract the ecosystem has deployed, with address, deployment block and transaction, verification link, phase parameters, and status. When a contract is superseded, the file says so and verificar_contratos.py fails if a live reference to the old one remains.
What a reader can check right now
# chain id, from a public node
curl -s -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}' \
https://rpc.testnet.empooriochain.org # → 0x7ea = 2026
# genesis hash
curl -s -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"chain_getBlockHash","params":[0]}' \
https://rpc.testnet.empooriochain.org # → 0xe973931e…eae7aa
# the sale contract's phase, on Sepolia
# getPhase(keccak256("PUBLIC")) on 0x675036F6809631929CD8d55190aE2869DE1E105c → price 650000, allocation 150000000
The validator set is read from Session::Validators, the supply from Balances::TotalIssuance, and the treasury cap from the runtime constants — all through Polkadot.js against the public endpoint.
What the files say the project has not done
This is the part a transparency page usually omits. The canonical documents list, under headings like what this document does NOT claim: that the team "dilutes to 8.57 %" (false while the founder's tranche can stake); that transactions are post-quantum (they are sr25519; PQC is opt-in and account protection is unbuilt); that the supply cap is globally enforced (checked on the staking path only; other mint paths pending); any TPS figure as a production claim (weights are hand-written, not measured on the reference machine). The mainnet gate lists every unchecked box.
Cadence
RED.json is re-verified on every runtime upgrade and carries its verification date. The decentralization report is regenerated weekly from the validator audit script. This blog's status posts cite the file versions they were written against.
Based on TOKENOMICS_CANONICO.md (preamble and §6), RED.json v1.2.0, CONTRATOS_EVM.json v1.1.0 and MAINNET_GATE.md.