Registrar changes use the Registry's governed activation process. Name owners control transfers and resolver selection for their active names.
XDCID Trust Center
Know what the platform can—and cannot—control
XDCID is designed to be verified rather than taken on trust. This page exposes the active contracts, administrative boundaries, custody model, security safeguards, stored data, and remaining operational limits so every important claim can be checked independently.
Contract control
Verified XDC mainnet contracts
Open-source · On-chain verifiedEvery active address is public and links to its explorer record. The contracts are deployed as ordinary contracts rather than upgradeable proxies, so their logic cannot be silently replaced. Material logic changes require a new deployment; changes to governed configuration remain visible on-chain.
Active Registrar V2
0x3D87B064a06f62cc4a24EAff13A591C9Ba791135The owner can pause new registrations and renewals. Payment amounts, signer authorization, ownership, nonce, and expiry are checked on-chain.
Pricing Policy V2
0x8aE4b7E57b6693c70FD40F5De17974CA5AB6DB94Owner-governed configuration changes use a 48-hour delay before activation.
Multichain Resolver
0xf4B040A2519E8BFdA62eDC3FDd1b6F9867F97232Only the current, unexpired name owner can set or clear chain-specific destination records.
Administrative contract state is checked during deployment preflight. Resolver contracts authorize individual name owners through the Registry and do not expose an administrative transfer role.
Custody
Non-custodial payments
XDCID never receives a wallet private key and does not hold user payment funds. Pay Link and Send transactions move from the payer wallet to the resolved destination, while current XDCID ownership and signed request integrity are checked before execution.
Security
Wallet-authorized controls
Owner actions require the connected wallet, expiry and ownership are checked on-chain, signed requests are bound to exact fields and nonces, and compatible smart accounts are verified through ERC-1271. Administrative routes use wallet challenges and server-side sessions.
Privacy
Minimized, purpose-bound data
Public names, addresses, and transactions remain visible on-chain. XDCID stores completed-payment metadata for wallet-authorized history; private references are encrypted. Production analytics remove URL queries and dynamic name or Pay Link identifiers before collection.
Independent assurance
Security evidence you can inspect
The active deployment is checked against its published manifest, contract bindings, administrative state, signers, treasury, pause state, and resolver configuration. The release process includes contract and application tests, ownership-lifecycle regression tests, and Slither static analysis. An independent third-party audit would add another expert review as adoption grows; it is an additional assurance layer, not the source of XDCID's security.
Support and disclosure
Use the verified project channel
Product questions and reproducible non-sensitive issues can be reported through the public GitHub repository. Do not post private keys, recovery phrases, personal payment records, or unpatched vulnerability details in a public issue.
Open GitHub Issues