Skip to main content

What is the Instrument Registry?

The InstrumentRegistry is a universal catalog that assigns unique identifiers to every DeFi position across all chains and protocols. Think of it as the DNS of DeFi: Just like DNS maps domain names to IP addresses, the Instrument Registry maps instrument IDs to protocol adapters and market IDs.

What is an Instrument?

An instrument in 1tx represents a specific DeFi position - a place where you can deposit assets into a protocol. Each instrument is defined by three things:
ComponentDescriptionExample
ProtocolThe DeFi platformAave, Compound, Morpho, Euler, Fluid
AssetThe token you depositUSDC, EURC, DAI
ChainThe blockchainBase, Ethereum
Examples:
  • Aave USDC on Base = 1 instrument
  • Compound USDC on Base = different instrument (same asset, different protocol)
  • Aave USDC on Ethereum = different instrument (same protocol & asset, different chain)
Each instrument gets a unique 32-byte identifier:
0x00002105c053a3e1290845e12a3eea14926472ce7f15da324cdf0700056fc04b
This ID is all you need to query yields, compare options, or execute deposits - no need to understand the underlying protocol specifics.

The Problem

Today’s DeFi landscape is fragmented:
  • No Universal IDs: Each protocol uses different identifiers (Aave uses pool addresses, Compound uses market IDs)
  • No Cross-Chain Standard: Same asset on different chains has different representations
  • No Comparison Framework: Hard to compare USDC on Aave vs USDC on Compound
  • Integration Complexity: Each new protocol requires custom integration logic

How 1tx Solves This

Without 1txWith 1tx
Aave pool address: 0x…Instrument ID: 0x00002105…
Compound market ID: different formatSame standardized format
Different per protocolUniversal identifier
Hard to compare yieldsEasy cross-protocol comparison

Deployed Instruments

Currently registered on Base Mainnet for the router path:

Aave V3 Instruments (5)

  • Aave USDC: 0x00002105c053a3e1290845e12a3eea14926472ce7f15da324cdf0700056fc04b
  • Aave EURC: 0x00002105ee9b5bc74aa022d3a1015fd449abb00dda35a713227ddc04d89db05c
  • Aave USDbC: 0x000021050675848050d62d913b2ac6dc14f70650cd1113d5fdbbec3e432f3ed5
  • Aave GHO: 0x000021059958277ec7a7f000b6b04b905f3f48cf85c08bb0c762bba74dce3be8
  • Aave cbBTC: 0x000021054e6e25355ea1b1aaf504b4c6b30cd98a426913d5828abd5c51f48e92

Compound V3 Instruments (2)

  • Compound USDC: 0x00002105e1d832a44e229e784c3d4afba9a1ca44a288e34f7e5ddcba23155adc
  • Compound USDbC: 0x00002105a6fe9e1b1bc1f2cae0073846842cee59fbab8b444ff4ba3749faaa5b

Morpho Vaults (7)

  • Steakhouse USDC: 0x00002105a9bdcb222682fd224470c8ed2ae152dbc308a4154c5a332e0d94dccb
  • Spark USDC: 0x00002105502f8247374b4bee34e398712f3df7b74c545f3f7b9aec39884ab022
  • Gauntlet USDC Prime: 0x000021057d36355ffddcae0bede6d9c8f4a73b6c2b3e3a66565c7cd350d72f9f
  • Steakhouse Prime USDC: 0x000021055b188115404f4be66d6cc3b540d3e9876b67059e1140ffafacf7b446
  • Re7 eUSD: 0x00002105aa35cdd6c9712f4fc21a5249dc60d59386348ac04041bdcc02668778
  • Clearstar USDC: 0x00002105bbb2bef3f7b15da825cf967932dfff01ed107b8b18ffdd0d90bbf60f
  • MEV Frontier USDC: 0x0000210592187c70f2a787a3fc931dfaea3f66c54a029407aa5ff83ea6fd1859

Euler Earn (1)

  • eeUSDC: 0x00002105c43f72017e35fdc387b7048128c0df8dc2bf81251d190522404829e8

Fluid (3)

  • fUSDC: 0x000021053a846b64b310324cfd96a29473b19dc05495f37cb6c87b8f3d721228
  • fEURC: 0x000021056b6d09c15812cf4d0b80184c57f1abd1da536becf4f42dd444e01f23
  • fGHO: 0x00002105927eaf7d74858d0241fb00e75d8f519093042667cf0df17cbdd7e37e
The deployed set in 1tx-contracts/docs/deployments.md includes Base, Arbitrum, and Unichain instrument sets. For the full address book, see Contract Addresses.

Benefits of Universal IDs

Composability

Any protocol can integrate by supporting the instrument ID standard

Comparability

Compare yields across protocols using the same identifier format

Cross-Chain Ready

Chain ID embedded in ID enables future cross-chain routing

Developer Friendly

Simple 32-byte identifier works everywhere (contracts, APIs, databases)

Next Steps

Atomic Router

Learn how transactions are routed

How It Works

See the complete transaction flow

API Reference

Query instruments via API

Integration Guide

Start integrating 1tx