Overview (main vs test networks)

All examples use the test network so they can be easily run with faucet funds instead of real funds. This main differences between test and main network interactions is which network alias, tokens and contract addresses should be used when interacting with the network and anchors. The Anchor Metadata and Resolver handle identifying which Anchor's are available and what their endpoints are. This makes it very easy to switch between test and main.

For the latest tokens and supported assets on the main network, refer to the Anchor Resolver Metadata.

https://static.network.keeta.com/metadata/currencyMapstatic.network.keeta.com

https://static.network.keeta.com/metadata/servicesstatic.network.keeta.com

Below is a summary of the chain/network ID's, token and contract addresses between the two environments.

Network and Chain ID's

Chain

Keeta

Base

Ethereum

Arbitrum

Test

1413829460

84532

11155111

421614

Main

21378

8453

1

42161

For the most up to date tokens and contracts supported, use the Anchor Metadata to determine correct tokens and contract addresses. Below is one example for USDC

USDC Token on TEST

Chain

Keeta

Base

Ethereum

Arbitrum

Test

keeta_apna75yhhvnv4ei7ape55hndk4yepno7a7i2mhtiwahiygixjcnmvswxhnmnk

0x036CbD53842c5426634e7929541eC2318f3dCF7e

0x1c7D4B196Cb0C7B01d743fbc6116a902379C7238

0x75faf114eafb1BDbe2F0316DF893fd58CE46AA4d

USDC Token on MAIN

Chain

Keeta

Base

Ethereum

Arbitrum

Test

keeta_amnkge74xitii5dsobstldatv3irmyimujfjotftx7plaaaseam4bntb7wnna

0x833589fcd6edb6e08f4c7c32d4f71b54bda02913

0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48

0xaf88d065e77c8cC2239327C5EDb3A432268e5831