Perpl (perpetual futures on Monad)

perpl · Monad

Perpl's exchange contract emits about seventy percent of Monad's logs and nothing indexed it publicly. Fills, funding, liquidations and markets in real units, from the contract's own 202 events, with the ABI vendored from Perpl's MIT SDK.

statusbuilding
categoryPerpetuals
tier1
complexitymedium
discoveryfixed addresses

What it indexes

Each event becomes a decoded SQL table.

OrderRequestV2, OrderChanged, OrderPlaced, OrderCancelled, MakerOrderFilledV2, TakerOrderFilledV2, PositionOpenedV2, PositionClosed, PositionLiquidated, FundingEventCompleted, ContractAddedV2

Building, 2026-09-04: backfilling 47 million blocks from Perpl's first log (2026-02-11) on Nuthatch 3.3.1 at about 1,250 events a second; parity against Perpl's public candles and funding API is scripted and not yet run. The implementation is unverified and Perpl publishes no ABI - the one here is crates/sdk/abi/dex/Exchange.json from PerplFoundation/dex-sdk (MIT, commit 65e0e897da), and every signature the live contract emits hashes to it. A keyed endpoint is strongly advised: rpc.monad.xyz caps getLogs at 100 blocks and this contract carries 77 logs a block. Set start_block by hand - no Monad endpoint we have found serves historic state, so init cannot detect the deployment block. Tracking: nuthatch-org/nuthatch#1148.

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.

nuthatch init --from https://github.com/nuthatch-org/perpl-nest

Source: nuthatch-org/perpl-nest.

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.