How to deploy an Avail Light Client?
NOTE: Spheron Compute offers the flexibility to create custom configurations for your instance.
Spheron allows you to deploy a compute instance pre-installed with Avail, all set up and ready to use on the Akash Network. To deploy a Avail light client:
- Click "New Cluster" on the top right corner.
- Choose "Compute" to use CPU-based instances for running containers.
- Choose your desired Compute Type option under Compute Type.
- Select Start from Marketplace App.
- Pick Avail Light Client from the marketplace.
- Select your preferred Region, if any. If you do not add a region, the container will be deployed in any region for Spot, or in the us-east region for On Demand. Click here to know more.
- Spheron will automatically select the recommended plan for the specific template. If you intend to move forward with the recommended plan, just Click "Deploy" to initiate deployment.
- Select the instance plan that suits your needs. You can use the "Create Custom Plan" toggle to create custom plans for your CPU based instance.
- Configure Storage (SSD) plan for your instance. Use the "Add Persistent Storage" toggle to add persistent storage for your instance.
- Update the name and the chain details under arguments in advanced configuration, if required. You can add more advanced configuration if required. Click here to know more.
- Click "Deploy" to initiate deployment.
Deploy Your Own
Deploy your own Avail Light Client with Spheron:
Verify Installation
- The Avail Light Client can be accessed only after the Compute Instance is provisioned. Thus, you need to wait for the installation to complete before you can start using it.
- As the node starts, the Instance Logs will display the output about the operations performed. If you see messages that blocks are being proposed and finalized, you have a running node.
2023-06-04T02:56:31.871284Z INFO avail_light::telemetry: Metrics server on http://0.0.0.0:9520/metrics
2023-06-04T02:56:31.884271Z INFO avail_light::http: RPC running on http://127.0.0.1:7000
2023-06-04T02:56:31.884386Z INFO avail_light::network: Local peer id: PeerId("12D3KooWQ77VEayXfSPWcj6ucAGcjZRTL8ANmtjsuULoyToGSBoo"). Public key: Ed25519(PublicKey(compressed): d44de4113b372855a655f1675325379705aa7a273698194e8e6814dab7791a).
2023-06-04T02:56:31.884605Z INFO Server::run{addr=127.0.0.1:7000}: warp::server: listening on http://127.0.0.1:7000
2023-06-04T02:56:31.892181Z INFO avail_light::network::event_loop: Local node is listening on "/ip4/127.0.0.1/udp/37000/quic-v1"
2023-06-04T02:56:31.892487Z INFO avail_light: Bootstraping the DHT with bootstrap nodes...
2023-06-04T02:56:31.892487Z INFO avail_light::network::event_loop: Local node is listening on "/ip4/192.168.1.146/udp/37000/quic-v1"
2023-06-04T02:56:31.892540Z INFO avail_light::network::event_loop: Local node is listening on "/ip4/127.0.0.1/tcp/37000"
2023-06-04T02:56:31.892745Z INFO avail_light::network::event_loop: Local node is listening on "/ip4/192.168.1.146/tcp/37000"
2023-06-04T02:56:42.220179Z INFO avail_light::rpc: Connection established to the node: wss://goldberg.avail.tools:443/ws <v1.6.0-99b85257d6b/data-avail/9>
2023-06-04T02:56:42.444576Z INFO avail_light::light_client: Starting light client...
2023-06-04T02:56:43.453935Z INFO avail_light::subscriptions: Received finalized block header header.number=2074
2023-06-04T02:56:43.455236Z INFO avail_light::light_client: Processing finalized block block_number=2074 block_delay=0
2023-06-04T02:56:43.456055Z INFO avail_light::light_client: Random cells generated: 4 block_number=2074 cells_requested=4
For more information, refer to the Avail docs (opens in a new tab).