Create L1
Deploys a new L1 under the token's orgID.
Last updated
Was this helpful?
Deploys a new L1 under the token's orgID.
Last updated
Was this helpful?
Creating an L1 uses and async deployment pattern. Once a successful request is made the L1 will move to the Development
state while AvaCloud performs checks on deployment details. Users can check the status of an L1 deployment using the endpoint.
Idempotency-Key*
"f47ac10b-58cd-4372-a567-0e02b2c3d479"
A unique key generated by the API caller, that the server uses to recognize subsequent retries of the same request.
How you create unique keys is up to you, but we suggest using V4 UUIDs, or another random string with enough entropy to avoid collisions.
*required field
Different components of your L1 can be deployed across various geographic locations, each with its own specific purposes (e.g. validator, RPC, etc.). Use the table below to see which infrastructure is supported between regions and networks (testnet vs mainnet). These regional configurations can be specified in the infraPlan
section of your request.
us-east-1
N. Virginia, USA
us-west-2
Portland, Oregon, USA
eu-central-1
Frankfurt, Germany
ap-northeast-1
Tokyo, Japan
ap-northeast-2
Seoul, South Korea
ap-southeast-1
Singapore
Precompiled contracts can be deployed on your L1 for faster execution of certain functions. Each precompile has at least one admin as well as the option to add enabled users. Admins can manage and configure precompile contracts, while enabled users are granted restricted access.
AvaCloud L1s go through various deployment states during the creation of an L1, such as:
Development
- This indicates the L1 payload request has been successfully made. AvaCloud is running additional checks before performing infra deployment.
InfraPending
- Indicates that the L1 infrastructure is under deployment, but not finished yet.
Deployed
- Indicates that L1 has been successfully deployed.
Error
- Indicates some error has happened. For why it failed, the customer can check “deploymentError” field about the failure.
401
Unauthorized
The authentication token is typically either missing, expired, or invalid
429
Too Many Requests
The number of allowed requests per minute has been exceeded
409
The idempotency key has already been used on a previous request
500
One of the required parameters is missing from the request body (e.g. name
, evmChainID
, etc.)
400
The airdrop address is missing or a zero address
400
The airdrop value is not a positive integer
400
The precompile is missing an admin
400
The admin address in the Transaction precompile is missing from the airdrop address list
400
The transformed name has already been used
400
The chain ID has already been used
400
400
See the section to view all gas configurations
See the Validator column in the to view all regions for a network
See the Debug Full and Debug Lite columns in the to view all regions for a network
See the RPC / WebSocket column in the to view all regions for a network
Use the endpoint to see available plans
See the RPC / WebSocket column in the to view all regions for a network
See the Validator column in the to view all regions for a network
See the RPC / WebSocket column in the to view all regions for a network
See the section for a list of available precompiles
The plan is not recognized as one of the valid
The region is not recognized as one of the valid
Creates a new L1
Idempotency key for creating L1