Build on TKMChain
TKMChain keeps familiar EVM tools while adding native APIs for Shield3, post-quantum accounts, TVM, communications, mining, and governance.
Open the explorer · Browse the source · Open the wallet
Network constants
- Chain ID: 8979
- Currency: TKM
- Execution: EVM-compatible transactions and deterministic TVM modules
- Consensus: RandomX proof of work with permanent finality through block 41913
- Account signatures: post-quantum ML-DSA-87
- Private sends: Shield3 native proof verifier and encrypted notes
RPC namespaces
The daemon exposes standard eth, net, web3, and admin methods alongside TKM-specific namespaces for privacy, account registration, rotating kings, TVM, phone, governance, and RandomX status. Bind RPC to loopback and place authenticated access behind a private service when remote access is necessary.
Validator registration is a consensus envelope rather than a contract call. The wire payloads and state machine are documented in the validator operator guide and implemented in core/validator_registry.go. Use the node's local signer or IPC; never construct a registration from an untrusted web page.
tkmprotocol_antarticalStatus and tkmprotocol_antarticalFeatures are read-only consensus views. They use the canonical chain head, so clients must not derive activation from local wall-clock time. The feature catalog includes validator registration and rewards, Shield3/Shield4, slot-level witnesses, multidimensional gas, finality certificates, and the four gated follow-ups: parallel contract execution, enforced Verkle stateless sync, bundled Revm/evmone adapters, and native byte-compatible EIP-4337/RIP-7560 execution.
When a node provides a validator registry RPC, display its records only after checking the returned head number and chain ID. A missing registry method is a normal compatibility state, not evidence that a validator set is empty.
Shield3 integration
Use the wallet helpers to decode payment codes, build private batches, review relay offers, construct selective disclosures, and match an operator's exact signed bytes. Applications should never parse or manufacture private envelopes by hand.
TVM and contracts
TVM modules must be deterministic across supported nodes. Avoid wall-clock time, filesystem access, network calls, floating-point ambiguity, unmanaged threads, and platform-specific assembly. Contract execution remains bounded by gas and consensus rules.
Mining
RandomX is CPU-friendly proof of work. The official XMRig build includes TKM configuration examples and cross-platform release artifacts. Pool connections can use onion endpoints through Tor.