Bridge

Bridge Machine NFTs between peaq and Base from ROS 2 via LayerZero V2.

Tokenomics 1.0 path. These services bridge Tokenomics 1.0 Machine NFTs. They serve machines already onboarded under Tokenomics 1.0. New machines use the Economics 2.0 flow in Activate, and a 2.0 machine is not bridged.

peaq_ros2_peaqos exposes the LayerZero V2 ONFT bridge as two services:

Service	Type	Purpose
/peaqos_node/bridge/nft	peaq_ros2_interfaces/srv/PeaqosBridgeNft	Send a Machine NFT between peaq and Base
/peaqos_node/bridge/wait_arrival	peaq_ros2_interfaces/srv/PeaqosWaitForBridgeArrival	Poll the destination chain until the bridged NFT arrives

Bridging is mainnet only. LayerZero V2 has no DVN route between agung and Base, so testnet bridge calls do not relay end to end.

Required configuration

peaq-source calls need the peaq-side LayerZero ONFT adapter wired into peaq_robot.yaml; Base-source calls pass the Base contract per call:

peaq_os:
  contracts:
    machine_nft_adapter: "0x9AD5408702EC204441A88589B99ADfC2514AFAE6"   # peaq mainnet
    # Pass the Base counterpart per call (see base_nft_address below).
    # It is required for Base-source calls and unused for peaq-source calls.

Equivalent env override: MACHINE_NFT_ADAPTER_ADDRESS. Base side reference contract: 0xee8A521eA434b11F956E2402beC5eBfa753Babfa (MachineNFTBase).

peaq → Base

The signer must own the Machine NFT on peaq and hold enough peaq for gas plus the LayerZero fee.

ros2 service call /peaqos_node/bridge/nft \
  peaq_ros2_interfaces/srv/PeaqosBridgeNft \
  "{signer_address: '<OWNER_EVM_ADDRESS>', token_id: 1, source: 'peaq', destination: 'base', recipient: '<RECIPIENT_EVM_ADDRESS>', base_rpc_url: '', base_nft_address: '', options_hex: ''}"

Then poll the destination:

ros2 service call /peaqos_node/bridge/wait_arrival \
  peaq_ros2_interfaces/srv/PeaqosWaitForBridgeArrival \
  "{dst_rpc_url: 'https://mainnet.base.org', dst_nft_address: '0xee8A521eA434b11F956E2402beC5eBfa753Babfa', token_id: 1, timeout: 900}"

timeout is in seconds. The service returns once ownerOf(token_id) on the destination chain returns any non-zero address, or the deadline is hit. It does not compare the owner with the intended recipient; read ownerOf yourself if you need that check.

Base → peaq

Same service shape, swapped source / destination. The signer must hold the Machine NFT on Base and enough Base ETH to cover gas plus the LayerZero fee. The bridge cannot fund that wallet for you.

ros2 service call /peaqos_node/bridge/nft \
  peaq_ros2_interfaces/srv/PeaqosBridgeNft \
  "{signer_address: '<OWNER_EVM_ADDRESS>', token_id: 1, source: 'base', destination: 'peaq', recipient: '<RECIPIENT_EVM_ADDRESS>', base_rpc_url: 'https://mainnet.base.org', base_nft_address: '0xee8A521eA434b11F956E2402beC5eBfa753Babfa', options_hex: ''}"

Wait for arrival on peaq:

ros2 service call /peaqos_node/bridge/wait_arrival \
  peaq_ros2_interfaces/srv/PeaqosWaitForBridgeArrival \
  "{dst_rpc_url: 'https://quicknode1.peaq.xyz', dst_nft_address: '0x2943F80e9DdB11B9Dd275499C661Df78F5F691F9', token_id: 1, timeout: 900}"

Field reference

PeaqosBridgeNft:

Field	Description
signer_address	Local wallet address that owns the NFT on the source chain
token_id	Machine NFT token id
source	peaq or base
destination	peaq or base
recipient	Address that receives the NFT on the destination chain
base_rpc_url	Base JSON-RPC URL. Required when source: 'base'; unused when source: 'peaq'
base_nft_address	Base MachineNFTBase address. Required when source: 'base'; unused when source: 'peaq'
options_hex	Raw LayerZero extraOptions payload hex. Leave blank to use the node’s default, an executor lzReceive option with 200,000 gas

PeaqosWaitForBridgeArrival:

Field	Description
dst_rpc_url	RPC for the destination chain
dst_nft_address	NFT contract on the destination chain
token_id	Machine NFT token id
timeout	Seconds to poll before returning arrived: false

Operational notes

• Record pre/post balances on both chains for any production bridge test.
• A fresh Base wallet has no ETH, so a Base → peaq bridge tx reverts on insufficient funds. Fund the Base wallet first.
• For a deeper protocol view (LayerZero peers, ONFT contracts, supported chains) see Machine NFT: cross-chain portability and the SDK JS / SDK Python bridge methods, which this node mirrors 1:1.