Skip to content

Addresses & registries

Use this page when you need a public identifier for the Polkadot Products Devnet: a chain ID, asset ID, registry address, or contract address. The tables below are meant to help you orient quickly, then point you back to the current source of truth before you build anything around a fixed value.

Every address here is a snapshot

Addresses are network-specific and change when a network is redeployed. Before you hard-code one, read it back from the devnet preset in the tooling address book, or resolve it on chain.

Note

Only public identifiers appear here: parachain IDs, asset IDs, and contract addresses. Account keys, mnemonics, and seeds are never published — the platform signs on the device, and operator secrets live outside every source repository.

Key chains and identifiers

The suite runs on the community-operated Paseo network: a relay chain plus a set of system parachains. Product developers usually start with Asset Hub (para 1000) for contracts and assets, People (para 1004) for identity, and Bulletin (para 1010) for app bundle storage.

Chain Para ID Role
Asset Hub 1000 Contracts (pallet-revive), assets, DotNS gateway
People 1004 Identity and proof-of-personhood
Bulletin 1010 Web-app bundle storage

The product suite itself targets 1000 / 1004 / 1010.

Field Value
EVM chain id (Asset Hub pallet-revive) 420420417
Native token PAS, 10 decimals
SS58 prefix (Devnet) 42
Web gateway dev-dot.li

Native token and stablecoins

The end-user CASH display name maps to a Devnet digital-dollar asset. On Asset Hub the protected asset ID is 50000413; the same logical asset can be represented on the People chain for app-facing CASH flows.

Asset Asset Hub u32 id Decimals Notes
pUSD (Digital Dollar / "CASH") 50000413 6 The main CASH asset used by the Devnet
USDt (Tether USD) 1984 6

The native token is PAS with 10 decimals; Devnet tokens carry no value. You can obtain Devnet funds from the Polkadot faucet.

On-chain registries

Three registries make the platform's names, contracts, and apps discoverable. They are deployed per network, so always resolve the address for the environment you are targeting.

DotNS (the .dot naming system)

DotNS resolves a .dot domain to an app bundle and records ownership. For most developers, the important idea is simple: a name points to content, and the gateway uses that record to load the app.

Devnet runs DotNS v1.0.0 (protocolVersion() on DotnsProtocolRegistry).

Contract Devnet address
DotnsProtocolRegistry 0xdDF3D3838Ff056F15602fC5a65927f185679C36F
DotnsRegistrar (ERC-721) 0xc609e0c2DAB4433d55a32FB098Db8788C1956302
DotnsRegistrarController 0x59dcF8BfFFa7239243785C3fC336D8Bb22312e8c
DotnsRegistry 0xb052E5EfC5ADEff1f21d48DEfb5169Cb394A1a73
DotnsResolver 0xFcB74C073a2d14dc65B178Bb873f4dE51318DDC2
DotnsReverseResolver 0x736e067290AE71f841399575ABfc8b2BAA5Eed7E
DotnsContentResolver 0x7e75491ecfb04900EB05ee63CABA2B33900aABB5
DotnsPopController 0xC3a3EdAb753F91488fD84E6134b5b0325dc22452
DotnsPopResolver 0x398912c9bb03180Ff049f0E034FE2E0024fb8406
PopRules 0xD5Ee34610F06f7FF4668aB4fabE2393B65a43AE7
DotnsNameEscrow 0xb50269322010DeeF2afb162c009Caf897971952C
StoreFactory 0x5Df012daA06cA2602DA153309C2E3A83284Cb879
Multicall3 0x92640655c5c7ee7E42F0B5aD68D205a8A767b81C

Some supporting DotNS contracts vary by network and are not reproduced here. Read them from DotnsProtocolRegistry (get(key)) or from the dotns-sdk address book for the devnet preset when you need them.

See Naming (DotNS) for how these contracts fit together.

CDM ContractRegistry

The Contract Dependency Manager (CDM) publishes a global package-name registry for contracts. cdm install and app frontends use it to resolve a contract name to a deployed address and ABI.

Registry Address
ContractRegistry (Devnet) 0x05662b3dbd5dd9f2ff92d67630477e84b0b37c1f

Shared system contracts registered in it:

CDM name Address
@polkadot/contexts 0x65317D46e8F62682002F9A769F7Bd8d63f8100Ba
@polkadot/profiles 0xaFa90438a1cBEd95A1fbA380226b27226e36C71B
@polkadot/threads 0x9F8c47b542856ABDa30F665eE4c7071444E39f50
@mock/reputation 0xa92964b3D49953086D01124cE0508932519edaDD

These are the kind of values you should resolve from the on-chain ContractRegistry rather than hard-code. See Smart contracts & CDM.

Browse Publisher

Browse is the app-discovery directory. Publisher records which .dot apps are discoverable; display metadata lives in DotNS records.

Contract Devnet address
Publisher 0xaab42efbe8ea4d4228c3a11e973f94c17b9a0f2c

Browse also reads attestation-resolver contracts for compliance badges. Those addresses are network-specific, so read them from the Browse address book for the network you target. See App discovery (Browse).

Polkadot app AccountDataStore

AccountDataStore is the contract the Polkadot app uses to back up coinage installations. Each install stores a small, client-encrypted record under the account's own address, so restoring the same recovery phrase on a new device can find coins held by earlier installs. The contract has no owner or admin, and only the device holding the key can read a record's contents.

Contract Devnet address
AccountDataStore 0x58c9963308c7735cf72ab633e8a9d892f5ab9e05

Attestation protocol

An EAS-style attestation suite (SchemaRegistry + AttestationService) provides general, permissionless attestations used by Browse compliance badges and other consumers. Both contracts run on Asset Hub via pallet-revive.

The concrete SchemaRegistry and AttestationService addresses are network-specific and are not reproduced here — read them from the attestation-protocol deployment records for the network you target.

Runtime precompiles

Some capabilities are exposed to contracts at fixed precompile addresses rather than as deployed contracts:

Precompile Address Purpose
Personhood 0x000000000000000000000000000000000a010000 personhoodStatus(address, bytes32 context) → tier + per-app alias

See Identity & personhood for how this is used by Product flows.

How addresses are resolved by tooling

You rarely paste these addresses by hand. CLIs select the devnet network preset (--env devnet for pad and dotns, -n devnet for CDM), and that preset carries the RPC endpoints and the full address book. Apps and frontends resolve names to addresses at runtime through the registries above. When you need a value directly, read it from the preset rather than assuming it.

Sources