Nests · port of a subgraph

MachineX

machinex-peaq · peaq

A Solidly/Ramses-style DEX on peaq - concentrated-liquidity and legacy pools discovered from their factories, gauges and fee distributors from the Voter, and position lifecycle from the NonfungiblePositionManager.

What it indexes

Each event becomes a decoded SQL table.

PoolCreated, PairCreated, GaugeCreated, Swap, Mint, Burn, Collect, Sync, NotifyReward, ClaimRewards, IncreaseLiquidity, DecreaseLiquidity, Transfer

Ported from Graph deployment QmcssauLtPam7J4pmAbvCKVoaBH6mowXhQJpLRMEyoQsEL. Building rather than available, for two measured reasons (2026-08-26). First, the manifest's Voter source at 0x3aF1dD7A2755201F8e2D6dCDA1a61d9f54838f4f has no code on peaq - eth_getCode returns 0x at latest on all three public endpoints - so its five handlers can never have fired and the gauge and fee-distributor factory rules can never discover a child. Second, no public peaq endpoint is archive and none of them errors: eth_getCode on the CL factory gives 6298 bytes at latest and 0x at block 5248285, and wide getLogs at deployment height returns [] rather than failing, so a backfill from 5248275 completes clean and empty. Pool and gauge tables therefore need an archive peaq node to ever populate. Live-tested over 20,002 blocks: decode is correct, 99 rows, but 40 of 44 tables empty. The seven factory rules are hand-written, since init --from-subgraph can only list candidates.

Run it yourself

The nest is a git repository: ABIs, views and a manifest. One command scaffolds a local copy, and nuthatch dev in it backfills and follows the chain against your own RPC.

Source: nuthatch-org/machinex-peaq.

Published data

This nest’s data is not on the public mirror, so there is nothing of it to query from this page. Running it yourself is the way to its data.