For the complete documentation index, see llms.txt. This page is also available as Markdown.

Avail

GetBlock provides fast and reliable access to Avail nodes via JSON-RPC API. Connect to the Avail network without running your own infrastructure.

Avail is a modular blockchain that provides scalable, trust-minimized data availability for rollups and other execution layers. It separates data availability from execution: rollups publish their transaction data to Avail, and Avail guarantees — through erasure coding, KZG polynomial commitments, and data-availability sampling by light clients — that the data is verifiably available without any single party having to store or re-execute it.

The Avail Node is a Substrate-based client secured by BABE block production and GRANDPA finality, with a native AVAIL token used for data-availability fees and staking. Applications interact with Avail over the Substrate JSON-RPC (system, chain, state, and author methods), Avail's own Kate RPC for data-availability queries and proofs, and WebSocket subscriptions for live updates.

Key Features

  • Data Availability Layer: Publishes and guarantees the availability of rollup data without re-execution

  • KZG Commitments + Sampling: Erasure-coded data with KZG commitments lets light clients verify availability by sampling a few cells

  • Substrate (BABE + GRANDPA): Substrate-based node with deterministic GRANDPA finality

  • Kate RPC: Avail-specific kate_* methods for block dimensions, matrix rows, cell proofs, and data-inclusion proofs

  • Trust-Minimized Bridging: Data-inclusion proofs (via kate_queryDataProof) let bridges prove availability on Ethereum

  • AVAIL Token: Used for data-availability fees and staking; denominated to 18 decimals

TECHNICAL DISCLAIMER: AUTHORITATIVE API SPECIFICATION.

GetBlock's API reference documentation is provided exclusively for informational purposes and to optimize the developer experience. Avail's Substrate JSON-RPC follows the Substrate/Polkadot RPC specification, and the Kate RPC is defined by the Avail Node implementation; both are documented at docs.availproject.org.

Interfaces

Interface
Transport
Use it for

JSON-RPC

Substrate JSON-RPC 2.0 over HTTP

Request/response queries (system, chain, state, author, payment) and extrinsic submission

Data Availability (Kate)

Substrate JSON-RPC 2.0 over HTTP

Avail-specific kate_* methods: block dimensions, matrix rows, cell proofs, and data-inclusion proofs

WebSocket

Substrate JSON-RPC 2.0 over WebSocket

The same methods plus pub-sub subscriptions (new/finalized heads, storage changes, extrinsic status)

Interface Endpoints

Network Information

Property
Value

Network Name

Avail

Native Currency

AVAIL

Token Decimals

18

SS58 Format

42

Framework

Substrate (data-availability layer)

Consensus

BABE block production with GRANDPA finality

Block Time

~20 seconds

Finality

Deterministic (GRANDPA)

Supported Networks

Network
JSON-RPC (HTTP)
WebSocket (WSS)
Frankfurt, Germany
New York, USA
Singapore, Singapore

Mainnet

✅

✅

✅

✅

✅

Quickstart

1

Setup project

2

Install dependency

3

Add code

4

Run the script

5

Response

1

Setup project

2

Install dependency

3

Add code

4

Run the script

APIs

Support

For technical support and questions:

See Also

Last updated

Was this helpful?