API Reference

Key Concepts

Learn the essential principles of AvaCloud and Avalanche L1.

Control who can deploy smart contracts on your blockchain.

1{
2    "name": "ContractAllow",
3    "admins": [
4        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38"
5    ],
6    "enabled": [
7        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D"
8    ],
9    "addressAliases": {
10        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38": "Admin 1",
11        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D": "Enabled User 1"
12    }
13}

Control who can modify the block size and dynamic gas pricing.

1{
2    "name": "GasUpdate",
3    "admins": [
4        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38"
5    ],
6    "enabled": [
7        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D"
8    ],
9    "addressAliases": {
10        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38": "Admin 1",
11        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D": "Enabled User 1"
12    }
13}

Gas Configuration

High

High disk usage and high throughput, low fees and high L1 operator cost (gasLimit: 20,000,000, gasTarget: 60,000,000)

Medium

Medium disk usage and medium throughput, medium fees and medium L1 operator cost (gasLimit: 15,000,000, gasTarget: 45,000,000)

Low

Low disk use and low throughput, higher fees but lower L1 operator cost (gasLimit: 12,000,000, gasTarget: 25,000,000)

Control who can mint additional tokens on your blockchain.

1{
2    "name": "NativeMinter",
3    "admins": [
4        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38"
5    ],
6    "enabled": [
7        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D"
8    ],
9    "addressAliases": {
10        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38": "Admin 1",
11        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D": "Enabled User 1"
12    }
13}

Control which wallet addresses can transact on your blockchain.

1{
2    "name": "TxAllow",
3    "admins": [
4        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38"
5    ],
6    "enabled": [
7        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D"
8    ],
9    "addressAliases": {
10        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38": "Admin 1",
11        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D": "Enabled User 1"
12    }
13}

Designates the address where all fees collected on the L1 will be sent. This address can also be a smart contract. Alternatively, you can allow validators to keep the gas fees on the blocks that they produce. Reward configurations can be adjusted depending on the presence of rewardManagerInitialRewardConfig and the value of allowFeeRecipients, as shown below.

Burn all gas fees

1{
2    "name": "RewardManager",
3    "admins": [
4        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38"
5    ],
6    "enabled": [
7        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D"
8    ],
9    "addressAliases": {
10        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38": "Admin 1",
11        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D": "Enabled User 1"
12    }
13}

Save gas fees for reward distribution

1{
2    "name": "RewardManager",
3    "admins": [
4        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38"
5    ],
6    "enabled": [
7        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D"
8    ],
9    "addressAliases": {
10        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38": "Admin 1",
11        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D": "Enabled User 1"
12    },
13    "rewardManagerInitialRewardConfig": {
14        "allowFeeRecipients": false
15        "rewardAddress": "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38"
16    }
17}

Allow block producers to claim fees

1{
2    "name": "RewardManager",
3    "admins": [
4        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38"
5    ],
6    "enabled": [
7        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D"
8    ],
9    "addressAliases": {
10        "0x2cE101c1b55cB9E88525F1328eA4FDC92AEECA38": "Admin 1",
11        "0x5e5eA9F4C0DA5B3F2333A704529D1C8c8C5E6E2D": "Enabled User 1"
12    },
13    "rewardManagerInitialRewardConfig": {
14        "allowFeeRecipients": true
15        // "rewardAddress": "0x0000000000000000000000000000000000000000"
16    }
17}

To learn more about precompiles check out this article.

L1 States

AvaCloud L1s go through various deployment states.

  1. Development - This indicates the L1 payload request has been successfully made. AvaCloud is running additional checks before performing infra deployment.

  2. InfraPending - Indicates that the L1 infrastructure is under deployment, but not finished yet.

  3. Deployed - Indicates that L1 has been successfully deployed.

  4. Error - Indicates some error has happened. For why it failed, the customer can check “deploymentError” field about the failure.

  5. TornDown - The L1 has been successfully deleted after making a successful teardown request.