Deployments

Aori is deployed across multiple blockchain networks to enable seamless cross-chain swaps. Below are the current deployment addresses and network information.

Supported Chains & Contract Addresses

ChainChain KeyChain IDEIDContract Address
Ethereumethereum1301010x0736bdc975af0675b9a045384efed91360d25479
Basebase8453301840xc6868edf1d2a7a8b759856cb8afa333210dfeda6
Arbitrumarbitrum42161301100xc6868edf1d2a7a8b759856cb8afa333210dfeda6
Optimismoptimism10301110xc6868edf1d2a7a8b759856cb8afa333210dfeda6

Network Details

Chain Keys

Chain keys are human-readable identifiers used throughout the Aori SDK and API. These correspond to the blockchain networks where Aori contracts are deployed.

Chain IDs

Standard blockchain network identifiers as defined by chainlist.org.

Endpoint IDs (EID)

LayerZero endpoint identifiers used for cross-chain messaging. These are required for cross-chain operations within the Aori protocol.

Contract Addresses

The main Aori protocol contract addresses on each supported network. These contracts handle order settlement and cross-chain coordination.

Integration Notes

When integrating with Aori:

  • Use Chain Keys: Always use the chain key identifiers (ethereum, base, etc.) in API requests rather than chain IDs
  • Verify Addresses: Double-check contract addresses before any mainnet integration
  • Test Networks: Use testnets for development and testing before deploying to production
  • Stay Updated: Monitor official channels for any deployment updates or new network additions

Getting Network Information

You can programmatically retrieve this information using the Aori SDK:

import { getChains } from '@aori/aori-ts';

// Get all supported chains
const chains = await getChains();

// Find specific chain info
const baseChain = chains.find(chain => chain.chainKey === 'base');
console.log('Base contract:', baseChain.contractAddress);

For more details on working with chain information, see the Chains documentation.