# Blockchain networks

Keep wallet assets, addresses, and networks aligned across Trade API operations.

Product: Client Trade API
Guides follow API reference 0.3.0 and event reference 0.2.0.
Canonical page: https://docs.axiym.io/trade-api/integration-guide/fundamentals/blockchain-networks

A blockchain network identifies the chain used to receive or send a digital
asset. The asset symbol alone is not sufficient: the same symbol can exist on
more than one network, and an address valid on one network must not be assumed
to be valid on another.

## Supported networks

| API value   | Production                          | Sandbox                                  |
| ----------- | ----------------------------------- | ---------------------------------------- |
| `TRON`      | TRON Mainnet                        | Shasta testnet                           |
| `AVALANCHE` | Avalanche C-Chain, chain ID `43114` | Avalanche Fuji C-Chain, chain ID `43113` |

The environment determines whether Axiym uses the production network or its
test network. The API value remains `TRON` or `AVALANCHE`; do not submit
`SHASTA` or `FUJI` as the `network` value.

## Use the network returned by Axiym

Register the owned external wallet on the network where its address is
controlled. For a deposit, send from that registered wallet using the `network`
returned with the receiving Axiym account's deposit instructions. For a
withdrawal, use the registered wallet's `destinationId`.

Do not derive the network from the currency, wallet address, or account
`paymentRails` value. Do not silently substitute another network because it
supports an asset with the same symbol.

## Validate these values together

Before initiating a wallet transfer, confirm:

* the registered external wallet and Axiym account currency;
* the blockchain `network`;
* the wallet address;
* whether the environment uses a test network or production network; and
* any minimum amount or network-fee requirements communicated by Axiym.

A mismatch can make a blockchain transfer delayed or unrecoverable.

## Sandbox and production are separate

Sandbox wallet tests use Shasta or Fuji and the test asset configured for your
sandbox Axiym accounts. Production uses the corresponding mainnet and separately
provisioned production details. Test assets have no production value, and
sandbox addresses or network settings must not be copied into production.

The Client Trade and Direct Trade APIs return the supported network code in deposit
instructions and registered external-wallet resources. Treat this returned
value as authoritative for that resource rather than maintaining an
independent list in your integration.

## Track completion

A wallet deposit or withdrawal can include a `transactionHash`. Store it with
the Axiym resource ID and use the explorer for the corresponding network and
environment when an external network check is needed.

An observed transaction is not a substitute for the corresponding API resource state.
Use the deposit or withdrawal status to determine how Axiym has processed and
posted the operation.