Skip to content

Tools & infrastructure

RPC providers, indexers, oracles, explorers, and the tooling ecosystem around Nexwest.

Updated Nov 4, 2026Builders2 min read
On this page

The ecosystem around Nexwest covers the pieces you should not rebuild: RPC, indexing, oracles, analytics, and custody.

RPC and nodes

ProviderServiceNotes
Nexwest FoundationPublic RPCRate-limited, mainnet and testnet
NorthstarDedicated RPCArchive and trace support
LatticeRPC + websocketsGlobal edge locations

Public RPC is suitable for development. Production applications should use a dedicated provider or run a node.

Indexing

ToolUse
Nexwest Indexer APIOrders, fills, positions, and vault history
PonderEVM event indexing
SubstreamsHigh-throughput custom indexing

The Indexer API is eventually consistent. For fills and positions that must be exact at a point in time, query the chain or the Info endpoint.

Oracles

Nexwest uses a validator-signed price index for perps. Builders can read the same index through:

  • oraclePx in activeAssetCtx,
  • the read precompile at 0x0000000000000000000000000000000000000807,
  • the public price feed on the explorer.

Do not use the last traded price as an oracle. It can be manipulated within a block.

Explorers

ExplorerUse
Nexwest ExplorerBlocks, transactions, accounts, order events
Nexwest TraceExecution traces and state diffs

Wallets and custody

Supported integrations include Rabby, MetaMask, Coinbase Wallet, WalletConnect, Fireblocks, and Safe. Smart-wallet signatures are supported for accounts that implement ERC-1271.

Test before you trust

Every provider is independent. Test failover, rate limits, and data consistency before relying on a single provider in production.

Analytics

ToolData
Nexwest AnalyticsVolume, open interest, fees, vault PnL
DuneSQL over decoded events
FlowsWallet-level flow analytics

Was this page helpful?