Smart contracts

Architecture, addresses, and responsibilities of every peaqOS contract.

peaqOS runs on five on-chain layers. The Economics 2.0 contract set (machine registry, subscriptions, price oracle, trust validator staking) is what new machines activate against. The Tokenomics 1.0 registry and staking contracts still serve machines onboarded before 2026-09-01. Both sets live on peaq chain as UUPS upgradeable proxies. Bridging is LayerZero V2; smart accounts follow ERC-4337; and low-level DID, batch, and WPEAQ operations are peaq chain precompiles.

Architecture

Economics 2.0 (peaq chain, UUPS proxies)
  InfoDesk (parameters, peers, allowlists)
  MachineStateAndSync ──activateMachine──► MachineRegistry (ERC-721, machineId == tokenId, DID document)
        │                                  MachineSubscription (tier bond, grace, runoff, credits) ◄── PriceOracle
        └──────────────────────────────►  CrossChainMirror ◄──► MachineBridgeAdapter (relocation, disabled)
  SubscriptionTokenProvisionPool (bond provision, USDT settlement) · TrustValidatorStaking · CoordinationFeeCollector
  EventRegistry (2.0) · ExecutionCostReserve · MachineMigrationHub (legacy mirroring)

Tokenomics 1.0 (peaq chain, UUPS proxies, legacy machines)
  IdentityRegistry ──owns──► IdentityStaking
        │                         ▲
        │ (gates on)              │ stakeFor()
        └─────► EventRegistry
        │
        └─────► MachineNFT

Cross-chain (peaq ↔ Base, LayerZero V2)
  MachineNFTAdapter (peaq)  ◄──► MachineNFTBase (Base)

ERC-4337 (peaq chain)
  MachineAccountFactory ──deploys──► MachineSmartAccount (BeaconProxy)

Precompiles (peaq chain, fixed addresses)
  DID (0x...800) · Batch (0x...805) · WPEAQ (0x...809)

• Which set a client talks to is a configuration choice: the SDKs enter Tokenomics 2.0 mode when you pass tokenomics20: { deploymentId } (JS) or tokenomics20=Tokenomics20Config(deployment_id=...) (Python); the CLI reads TOKENOMICS_DEPLOYMENT_ID. Apart from the 2.0 EventRegistry, which event submission reads from EVENT_REGISTRY_ADDRESS, Economics 2.0 addresses are not environment variables: they ship inside the SDK’s deployment record and are verified against InfoDesk.peer(role) before every write.
• Core contracts use UUPS upgradeable proxies (OpenZeppelin 5.x) with ERC-7201 namespaced storage. Future upgrades preserve state.
• Identity NFT (minted by IdentityRegistry) and Machine NFT (minted by MachineNFT) are separate ERC-721 spaces with independent tokenId sequences linked by machineId. See Machine NFT.
• The Tokenomics 1.0 IdentityRegistry implements ERC-8004 for DID-anchored machine metadata. The MCR API serves JSON Machine Cards for Economics 2.0 machines only and has none for Tokenomics 1.0 machines. See Machine Card.

peaq mainnet addresses

Economics 2.0 (peaq mainnet)

Deployment record peaq-mainnet (chain ID 3338). All are ERC-1967 proxies. Economics 2.0 writes go through the SDKs and the CLI. The seven contracts marked SDK are the roles the SDK snapshot carries: before a write the SDK checks their bytecode and verifies the six other than InfoDesk against InfoDesk.peer(role). Of the other eleven, the SDKs resolve OperatorRegistry and RemoteBondSettlement through InfoDesk.peer(role) for a Solana onboarding and read EventRegistry (2.0) for event submission; the rest are used by peaq’s own services. Apart from the 2.0 EventRegistry, which event submission reads from EVENT_REGISTRY_ADDRESS, none of them are environment variables.

Contract	Address	Role
InfoDesk	0x6C7426ada37212D94477Ac4CFcA43A38177D6A82	SDK. Parameters, peers, trust validator allowlist, PEAQ token pointer. Holds the transport of each sync message type, route-wide and per destination chain (0 = the trust validator node, the default; 1 = LayerZero; set by the owner with setTransport / setChainTransport, read with transportFor(route, chainId)), and the switch for messages the node delivers (isTvInboundAccepted()). For system messages sent over LayerZero it carries the receive value per destination chain (lzReceiveValueOf(5), 1,574,800 lamports for Solana on mainnet) that pays the Solana account rent, and the bridge adapter’s PEAQ reserve pays the message, not the machine’s operator
MachineRegistry	0x64b93Cc29b251fAFa83BD110cDB1C24207f85536	SDK. ERC-721 machines (machineId == tokenId) and DID documents
MachineStateAndSync	0xcD1917FB2a56459AcA34FDD118e08776dE0890f2	SDK. activateMachine, suspend, resume, relocation orchestration
MachineSubscription	0x9e37AD189c334C92e6B8a812Ca4c02f35Ac43895	SDK. Tier bonds, renewals, grace and runoff, credits. Allowance spender for PEAQ
CrossChainMirror	0x71DCB313977d6884212395505f081a2991Bfe8E5	SDK. Home-chain records and mirrored data
MachineBridgeAdapter	0x791087c35484b567c53f392a624d2e4BaDcC53DF	SDK. Sends and receives the sync messages between peaq and Solana, through the trust validator node (TvRelayQueued out, tvReceive in) or LayerZero, as set in InfoDesk. LayerZero relocation transport (disabled). Receives the link push from Solana; lastAppliedMirrorPushSeq is the watermark that marks a Solana onboarding complete
SubscriptionTokenProvisionPool	0x7088Cf400081428a41a4287B75AC633071c0e92A	SDK. PEAQ reserve that pays out bonds collected on another chain, and USDT settlement of the PEAQ bond (needs a USDT token configured in the pool; none is set on mainnet). Allowance spender for USDT
PriceOracle	0x96E6a3BAB0254E7f25B0cdE50C3cBF39272cd46B	Daily PEAQ/USD stamps by the trust validator node
TrustValidatorStaking	0x38cfa22Da649F650Cbe7278A9B5141380968920e	Permissionless trust validator staking (not exposed in SDKs)
CoordinationFeeCollector	0xCaD48Dc0Eb650C9a0B799e36627D9de18f5a9Dc2	Per-tier coordination fees, x402 (fee configured at 0)
ExecutionCostReserve	0xC2F13a8310432f27701F59f060417e986ae24e82	Gas reserve for system functions
EventRegistry (2.0)	0xA1e7F1d7B24dAb55Dc92491e6d9B89F6E925Ad1e	Events for 2.0 machines. Set EVENT_REGISTRY_ADDRESS to this address for 2.0 machines; peaqos init writes it on peaq mainnet
MachineMigrationHub	0x06EbC22B08229fb796788DB1AAE9675bfC4e22ba	Mirrors Tokenomics 1.0 machines into 2.0 (operated by peaq)
OperatorRegistry	0xBaA547479Ae3bBbe9DB21Dbe03870C3D8427db8F	Binds a foreign-chain operator identity to a peaq address for the remote-bond rail. The SDKs’ and CLI’s Solana registration (register_solana_operator / registerSolanaOperator, [1/7]) writes it
RemoteBondSettlement	0xe8ad89b42C1309878c6DDD3D20136a858550FFA2	Books bonds paid on a terminal chain (Solana) onto peaq. Trust validator only; the SDKs and CLI observe it as the bond stage of a Solana onboarding
PeaqReturnReceiver	0x859e5B41B4dF66556CFfFCE243E392e1E7300D6E	Receives PEAQ returned from a terminal chain’s vault. Validator and owner operated
TreasuryPool	0xD45aF41357f55A52A10336b2f5c965a9eEa35e75	Treasury sink. InfoDesk.treasury() resolves to it, so the treasury half of bond runoff, fraud termination and coordination fees lands here. Not in the SDKs
AttestationRegistry	0x08804517BB1290ef0dDa8Db9Ff95255045d25f9A	Attestation quorums and states for Verify, registered in InfoDesk as the ATTESTATION_REGISTRY peer. Read through the Verify API, the SDKs and peaqos verify status; writes are peaq-only in v1. Not in the SDK deployment record

The PEAQ token the bond is paid in is not a deployed contract: InfoDesk.peaqToken() resolves to the native-balance precompile 0x0000000000000000000000000000000000000809.

Tokenomics 1.0 (peaq mainnet)

Set these in your environment. The SDK reads them from fromEnv() / from_env(). The SDK constructor still requires them in Tokenomics 2.0 mode, although activation reads none of them.

Core

Contract	Variable	Address
IdentityRegistry	IDENTITY_REGISTRY_ADDRESS	0xb53Af985765031936311273599389b5B68aC9956
IdentityStaking	IDENTITY_STAKING_ADDRESS	0x11c05A650704136786253e8685f56879A202b1C7
EventRegistry	EVENT_REGISTRY_ADDRESS	0x43c6AF2E14dc1327dc3cc6c7117D1CD72fffEcbA
MachineNFT	MACHINE_NFT_ADDRESS	0x2943F80e9DdB11B9Dd275499C661Df78F5F691F9

Precompiles

Contract	Variable	Address
DID	DID_REGISTRY_ADDRESS	0x0000000000000000000000000000000000000800
Batch	BATCH_PRECOMPILE_ADDRESS	0x0000000000000000000000000000000000000805
PEAQ (native ERC-20 precompile, IWPEAQ in the contracts)	n/a	0x0000000000000000000000000000000000000809

Optional

Contract	Variable	Address	Needed for
MachineAccountFactory	MACHINE_ACCOUNT_FACTORY_ADDRESS	0x4A808d5A90A2c91739E92C70aF19924e0B3D527f	deploySmartAccount / getSmartAccountAddress
MachineNFTAdapter	MACHINE_NFT_ADAPTER_ADDRESS	0x9AD5408702EC204441A88589B99ADfC2514AFAE6	bridgeNft from peaq
AdminFlags	ADMIN_FLAGS_ADDRESS	0x1c5f33fBEE6BA38ed9bDE247C1Ba89A2116C25f1	MCR API server (negative-flag reads + admin trust overrides)

Base mainnet addresses

Needed when bridging into peaq from Base. Pass as baseNftAddress / base_nft_address to bridgeNft / bridge_nft.

Contract	Address
MachineNFTBase (LayerZero ONFT)	0xee8A521eA434b11F956E2402beC5eBfa753Babfa

Solana mainnet addresses

Economics 2.0 (Solana mainnet)

Eleven Anchor programs. Protocol chain ID 5, LayerZero EID 30168. All keep the deployment wallet as upgrade authority and as administrator of each program’s root account.

Program	Program ID	Counterpart on peaq
InfoDesk	UzabYW77ox4AJzsMiiFqA89Vm5aWeyy3PSW9LtaYnjG	InfoDesk subset: chain registry, currency whitelist, tokenomics parameters, bridging flags
MachineBridgeAdapter	CEqQYLMm6WKHyvBZRU91N2kkQV1J2V3HxLW8McFQ681H	MachineBridgeAdapter plus the mirror stores. LayerZero OApp and trust validator node endpoint (tv_receive in, a TvOutbox account per destination out); its store PDA 5MKZ41yuSg46fTt4ma29J69aCbw93eyVQ9XKW89vxJ6i is the peer peaq’s adapter points at
MachineRegistry	AgR8exgW2mwpf4v2PpojYuDHXVBThZtenS6XYjV4JnUD	MachineRegistry: Solana-native machine identity and DID documents
CoordinationFeeCollector	7DsHEYDpvvZY3BgCLS2wAYrftGAQuUWLibQijeYULMBh	CoordinationFeeCollector: fees paid in SOL or a whitelisted SPL mint
MachineStateAndSync	DbhzPvFghnmpw6YmZsCBuVU6u1sjbc1FfzPDqi4VjoZL	MachineStateAndSync destination half: relocation state
EventRegistry	AWMkhnccpjuMgUDqWfFG38DCiKTqC3KsLhrzivEPWb77	EventRegistry (2.0): per-machine activity and revenue events for Solana machines
PriceOracle	FpfGfjbkSm5yBuV5d5HLsr6wybm1EvgHoqcTyTFZG12v	PriceOracle: the PEAQ/USD stamp that sizes a bond paid on Solana, and the USD price reference for the coordination fee
TreasuryPool	EzppvStr1VorTrNEDGWwgSGnM9xum3uAc6W1vCFnr4Ey	Treasury sink for coordination fees (native SOL and SPL)
TrustValidatorStaking	BSDXwYicwx3NZdD7Mpe147jzWqUYmAzR8PptqH5NU1wM	TrustValidatorStaking, home chain 1 (peaq)
SubscriptionTokenProvisionPool	af2qxPw66kUuboH8TfiGqkVray1W91UnMYPYyPPDZhF	SubscriptionTokenProvisionPool: PEAQ provision for bonds paid on Solana
MachineSubscriptionTerminal	4EFBHr9AyazPA6cxZRYYU5eK6uguogG5YhPQX6cs6A9d	MachineSubscriptionTerminal: payment intake for a bond settled on peaq

Configuration: bonds are sized from peaq’s tier prices mirrored to Solana ($0.02 /$0.20 / $40 for Entry, Basic and Pro), native SOL and bridged PEAQ whitelisted as currencies, bridging on and relocation off. On the peaq side MachineBridgeAdapter has the Solana store PDA registered as its LayerZero peer. Sync messages use the trust validator node in both directions.

The SDKs and CLI reach InfoDesk, MachineBridgeAdapter, MachineRegistry, MachineStateAndSync, EventRegistry, MachineSubscriptionTerminal, PriceOracle and SubscriptionTokenProvisionPool (deployment record solana-mainnet in the JS SDK, the Solana half of peaq-mainnet in the Python SDK): management, reads and event submission for machines homed on Solana, and onboarding (CLI 0.0.19, both SDKs 0.11.2, terminal-first in seven stages). CoordinationFeeCollector, TreasuryPool and TrustValidatorStaking are deployed but not configured in the SDKs; nothing the SDKs call depends on them. MachineSubscriptionTerminal owns the SubscriptionTerminal account the programs read for onboarding and event eligibility; which subscription account the SDKs read is selected by the deployment record’s reader setting (terminal). With the SDKs and CLI the bond for a Solana machine is paid on Solana through MachineSubscriptionTerminal, in PEAQ or in USDC swapped to exactly the bond, and peaq’s trust validator node books it onto peaq. See Onboard a machine on Solana and Omni-chain for the status of each capability.

Agung testnet addresses

Economics 2.0 (agung testnet)

Deployment record agung-2026-08-28 (chain ID 9990). Same seven SDK roles as mainnet. Agung has no paired 2.0 MCR, so monetization calls fail with DEPLOYMENT_UNAVAILABLE there.

Contract	Address
InfoDesk	0x72b66AF120c55371cA6e5Ce38D4e10dF1bA30Bb1
MachineRegistry	0x538da35489B1F0035799a8351E67835ae4ABb377
MachineStateAndSync	0xA7D33726232aae30622643a18047f0Ca3e159da9
MachineSubscription	0xaDCc5dD8CD57E3198B881c3388F25D2fD69B5aDc
CrossChainMirror	0xd5F8d5944c5d488B1cD698D642FC8156a8CD0c0c
MachineBridgeAdapter	0x0406e7bE522AEa626aee54f6258D415215e59F76
SubscriptionTokenProvisionPool	0x8A3692Ad0AcF79BB89413514Af9957d95032e19B

Tokenomics 1.0 (agung testnet)

Tokenomics 1.0 path. These contracts serve machines already onboarded under Tokenomics 1.0 on agung, and the SDK constructor still requires the core addresses. New machines on agung activate against the Economics 2.0 set above.

The contract surface matches mainnet; only the deployed addresses differ.

Core

Contract	Variable	Address
IdentityRegistry	IDENTITY_REGISTRY_ADDRESS	0x9E9463a65c7B74623b3b6Cdc39F71be7274e5971
IdentityStaking	IDENTITY_STAKING_ADDRESS	0x55f336714aDb0749DbFE33b057a1702405564E3d
EventRegistry	EVENT_REGISTRY_ADDRESS	0x2DAD8905380993940e340C5cE6d313d5c2780040
MachineNFT	MACHINE_NFT_ADDRESS	0xB41C2A4f1c19b6B06beaAce0F5CD8439e77C4b1c

Precompiles

Identical to mainnet: same fixed addresses on every peaq runtime.

Contract	Variable	Address
DID	DID_REGISTRY_ADDRESS	0x0000000000000000000000000000000000000800
Batch	BATCH_PRECOMPILE_ADDRESS	0x0000000000000000000000000000000000000805
PEAQ (native ERC-20 precompile, IWPEAQ in the contracts)	n/a	0x0000000000000000000000000000000000000809

Optional

Contract	Variable	Address	Needed for
MachineAccountFactory	MACHINE_ACCOUNT_FACTORY_ADDRESS	0x65a4DfEB799dFf8CF15f13816d648a7805d6b1F9	deploySmartAccount / getSmartAccountAddress
AdminFlags	ADMIN_FLAGS_ADDRESS	0x4181a2Aa34aFb247450FfcBd65be5aBD4Cbee658	MCR API server (negative-flag reads + admin trust overrides)

Bridging cannot be exercised on agung. LayerZero deprecated the agung endpoint (EID 40299): DVNs and executors are no longer active, so bridgeNft / bridge_nft cannot relay, and there is no agung MachineNFTAdapter. Exercise the bridge on peaq mainnet and Base mainnet only.

Economics 2.0 contracts

MachineRegistry

The 2.0 machine registry: one ERC-721 per machine where the token ID is the machine ID (uint256(keccak256(abi.encode(machineType, credentialSubject)))), plus the machine’s DID document (controller, verification methods, authentication, service endpoints). Standard ERC-721 transfers and approvals are how a machine changes owner. New machines are minted inside MachineStateAndSync.activateMachine; the registry’s other mint paths (legacy reissue, relocation import) are callable only by MachineStateAndSync and MachineBridgeAdapter. There is no public mint.

SDK methods: getMachineOwner, computeMachineId, transferMachine, safeTransferMachine, approveMachine, setMachineApprovalForAll, setMachineController, setMachineVerificationMethods, setMachineAuthentication, setMachineServiceEndpoints

MachineStateAndSync

Orchestrates the one-transaction activation (activateMachine, activateMachineWithUsdt), voluntary suspend and resume, per-machine and protocol-wide pause flags, and relocation. Never holds tokens.

SDK methods: activateMachine, activateMachineWithUsdt, previewMachineActivation, suspendMachine, resumeMachine, getMachineActivationState, getMachineAvailability

MachineSubscription

Prices and collects the tier bond (requiredPeaqAmount(tier)), stores each machine’s subscription (tier, period, bonded amount), applies grace and runoff, and tracks bonding reward and voucher credits. A renewal can also change the tier, up or down, once the period has ended (Grace or Runoff), priced at the full bond of the new tier; a tier change is refused while the machine is Active. The contracts on peaq mainnet support it, but the published peaq-mainnet deployment record does not enable tier selection on renewal, so the CLI and the SDKs refuse a tier there (RENEWAL_TIER_UNSUPPORTED) and today a renewal keeps the stored tier. The allowance spender for PEAQ bonds. Settlement functions are called by the trust validator node.

SDK methods: activateExistingMachine, renewMachine, previewMachineRenewal, getMachineSubscription

InfoDesk

Owner-set protocol parameters (tier prices in USD, grace and runoff durations, epoch length, fee rates, burn and treasury addresses), the peer registry the SDK verifies against (the owner can set or clear a role; a cleared role reads as the zero address), the trust validator allowlist, and peaqToken(), which is set once and cannot be re-pointed.

PriceOracle

Daily currency prices committed by trust validator nodes (commitPrices), read by MachineSubscription to convert USD tier prices to PEAQ. Public read: getLatestPrice(bytes32 currency).

CrossChainMirror and MachineBridgeAdapter

Record the machine’s home chain and carry the messages between peaq and Solana. Sync messages (mirror pushes such as the link push, and revenue reports from Solana) go through the trust validator node by default: the sending adapter emits TvRelayQueued with a nonce per destination, and the node delivers each message to the other chain’s adapter (tvReceive on peaq, tv_receive on Solana) in nonce order. Only an allowlisted trust validator can deliver. No LayerZero fee is paid on this route; the node pays the delivery transaction. The owner can switch a message type to LayerZero (on peaq InfoDesk.setTransport, or setChainTransport for one destination; on Solana set_sync_route); there is no automatic failover between the two. The relocation handshake and peaq’s Retire broadcast always travel over LayerZero V2, and the node refuses them on both chains. InfoDesk.isBridgingEnabled() is true and isMachineRelocationEnabled() is false, so relocation stays disabled and the SDKs expose status reads only. For a machine homed on Solana, MachineBridgeAdapter applies the owner’s link push coming back from Solana; lastAppliedMirrorPushSeq(5, 0, machineId, MACHINE_REGISTRY_KEY) at or above the push’s sequence is what the SDK calls complete.

SDK methods: getMachineRelocationStatus

SubscriptionTokenProvisionPool

Pays out the PEAQ bond for bonds collected on another chain, and settles --payment usdt / activateMachineWithUsdt / renewMachine with payment: "usdt" when a USDT token is configured in the pool. On peaq mainnet none is set, so USDT payments fail. The allowance spender for USDT.

TrustValidatorStaking, CoordinationFeeCollector, ExecutionCostReserve, EventRegistry (2.0), MachineMigrationHub

Live on mainnet. EventRegistry (2.0) is the write target of submitEvent / submit_event / peaqos qualify event when EVENT_REGISTRY_ADDRESS points at it; the other four are operated by peaq or reserved for later releases and not exposed in the SDKs or the CLI. See Economics 2.0.

Tokenomics 1.0 contracts

These serve the machines onboarded before 2026-09-01. A client constructed with tokenomics20 never writes to them; without tokenomics20 the SDKs still run the legacy registerMachine / register_machine flow against them (legacy flow).

IdentityRegistry

Central machine identity registry of Tokenomics 1.0. Mints an ERC-721 Identity NFT to each machine on registration and orchestrates bonding through IdentityStaking.stakeFor(). Implements ERC-8004 for DID-anchored machine metadata; the MCR API has no Machine Card for these machines. DID attributes themselves live on the peaq DID precompile (W3C DID), written by the SDK via writeMachineDIDAttributes. Tracks per-machine status (None → Pending → Verified / Rejected / Deactivated). Supports self-registration and proxy registration.

SDK methods: registerMachine, registerFor Key state: minBond (currently 1 PEAQ), nextMachineId, operatorOf, machineStatus

IdentityStaking

Bond token storage. Tokens are staked at registration time via stakeFor() and held permanently; no withdrawal path is exposed. Only authorized callers (IdentityRegistry) can initiate stakes. Supports pause / unpause by owner.

SDK interaction: Indirect. registerMachine / registerFor route the bond through here automatically.

EventRegistry

On-chain store for revenue (type 0) and activity (type 1) events. Gates event submission on (a) the machine being registered in IdentityRegistry, and (b) the machine being bonded in IdentityStaking. Authorization rule: msg.sender must be the Identity NFT holder, the machine wallet, or the operator (see Events: Authorization). Stores a keccak256 hash of the raw data; payloads stay off-chain.

SDK methods: submitEvent, batchSubmitEvents Concept: Events

MachineNFT

ERC-721 representing a machine’s financial profile, bridged through the separate LayerZero V2 MachineNFTAdapter. Minted in a separate mintNft call after registration: the Machine NFT tokenId is independent from the Identity NFT tokenId. tokenURI points at the MCR API’s /metadata/{token_id} route, which serves Economics 2.0 machines only; there is no public MCR for Tokenomics 1.0 machines.

SDK methods: mintNft, tokenIdOf Concept: Machine NFT

Cross-chain contracts

These are the Tokenomics 1.0 Machine NFT bridge. Economics 2.0 machines relocate through MachineBridgeAdapter and CrossChainMirror instead, which is disabled today.

MachineNFTAdapter (peaq)

Wraps MachineNFT for LayerZero V2 bridging. Lock/unlock pattern: locks the NFT on peaq while the mirror exists on the destination chain. Needed only when bridging from peaq. Peer: Base (EID 30184). The Solana lane is closed: its ONFT program HraxgdzfcAi3AnxRP5sGSrXGAb9ZT1tZTMNuh9vQLxTu is closed on Solana mainnet (its program data no longer exists), and the SDKs bridge to Base only.

SDK methods: bridgeNft / bridge_nft when source is "peaq"

MachineNFTBase (Base)

Standard ONFT721 on Base. Burn/mint pattern: NFT is burned when bridged back to peaq. Needed when bridging from Base.

SDK methods: bridgeNft / bridge_nft when source is "base" (pass the address as baseNftAddress / base_nft_address)

ERC-4337 smart accounts

MachineAccountFactory

CREATE2 factory for deploying MachineSmartAccount BeaconProxy instances. Standard ERC-4337 flow: smart accounts run through the canonical EntryPoint at 0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789 (same address across all EVM networks).

SDK methods: deploySmartAccount / deploy_smart_account, getSmartAccountAddress / get_smart_account_address

MachineSmartAccount

The shared BeaconProxy implementation behind deployed smart accounts. Handles owner/machine RBAC and broad machine execution authority. Users never interact with the implementation address directly; calls go to the deployed proxy.

AdminFlags

Optional peaq-chain contract read by the MCR API server (not the SDK). Holds admin-set flags that modify MCR responses: per-machine negative_flags and trust-level overrides. MCR consumers see the adjusted score in their API response.

When the contract isn’t configured, contracts.admin_flags on GET /ready reports true (the optional check is skipped) and the service serves unmodified MCR.

Precompiles (peaq chain)

Precompile	Address	Purpose
DID	0x0000000000000000000000000000000000000800	Read/write DID attributes. Used for Machine Card metadata and proxy-operator fleet attributes
Batch	0x0000000000000000000000000000000000000805	Atomic multi-call. The SDKs use it to write several DID attributes in one transaction; Tokenomics 1.0 registration bonds through IdentityRegistry directly
WPEAQ	0x0000000000000000000000000000000000000809	The native PEAQ ERC-20 precompile, which peaqOS contracts reference as WPEAQ (IWPEAQ); used by IdentityStaking as the staking token. Not the standalone WPEAQ ERC-20 token, see PEAQ Token Contracts

LayerZero endpoints

Used by the bridge adapters. You don’t set these directly; the SDK handles them.

Network	LayerZero V2 endpoint	EID
peaq mainnet	0x6F475642a6e85809B1c36Fa62763669b1b48DD5B	30302
Base mainnet	0x1a44076050125825900e736c501f859c50fE728c	30184
Solana mainnet	76y77prsiCMvXMjuoZ5VRrhG5qYBrUMYTE5WgHqgjEn6	30168

The SDK exports the peaq and Base EIDs as LAYER_ZERO_EIDS (JS) / LAYERZERO_EIDS (Python); the Solana EID is not in that constant.

Upgrade pattern

All Economics 2.0 contracts, and all Tokenomics 1.0 core contracts (IdentityRegistry, IdentityStaking, EventRegistry, MachineNFT), use OpenZeppelin UUPS upgradeable proxies with ERC-7201 namespaced storage. Implementation slots are kept distinct by namespace, so future upgrades won’t collide with existing state.

MachineSmartAccount uses a BeaconProxy pattern: a single implementation upgrade simultaneously applies to every deployed smart account.

See also

Install

Wire the contract addresses into .env for the SDK.

SDK reference

Every method that reads or writes these contracts.

API reference

Off-chain reads derived from the on-chain state.