Availability API
Serves data recorded by the Tiramisu DA layer, such as committed blocks
Last updated
Serves data recorded by the Tiramisu DA layer, such as committed blocks
Last updated
The availability API is the place to get onchain data, like blocks and transactions. It is the primary interface for downstream components like rollups and end users.
The API is designed to be robust and pure. Robust means that if the node hosting the API misses some data, for example from being offline when a certain block was finalized, it will automatically fetch the missing data from a peer, and will eventually fetch and store all finalized data. Pure means that each endpoint is a pure function -- with the exception of occasionally returning 404 for missing data, each endpoint will always give the same response given the same parameters.
Due to purity, this API provides no aggregate queries, like block or transaction counts, which might change as missing data is fetched. Likewise, every endpoint takes some specification of the exact point in the chain the client is looking for, like a block height or hash. There is no "latest block" query. Thus, most real-world use cases will need to complement the availability API with use of the .
While this API has many endpoints, don't be intimidated -- there is a method to the madness. The API is organized around collections of different resources, each of which corresponds to blocks and can be indexed by block height or hash.
Leaves
Headers
Blocks
Block summaries
Payloads
VID common
Each of these resources can be addressed in the following ways:
<resource>/:height
<resource>/hash/:hash
<resource>/payload-hash/:payload-hash
Not all of the indices are implemented for all resources, although in principle they can be. The supported indices are documented below for each endpoint. Future releases will fill in the missing functionality.
Leaves are currently indexed slightly differently from other resources. See documentation on leaf endpoints. Future versions of this API will merge the concept of a leaf and a header, resolving this discrepancy.
In addition, there are endpoints to fetch a range of each resource (<resource>/:form/:until
) and to subscribe to a WebSockets stream (/stream/<resource>/:from
).
BlockSummary
BlockResponse
LeafResponse
PayloadResponse
VidCommonResponse
/availability/leaf
/availability/leaf/:height
/availability/leaf/hash/:hash
height
integer
Height of the leaf to fetch
hash
tagged<COMMIT>
Hash of the leaf to fetch
LeafResponse
/availability/leaf/:from/:until
Retrieve a range of consecutive leaves.
from
integer
Height of the first leaf to fetch
until
integer
Height just after the last leaf to fetch
[LeafResponse]
/availability/stream/leaves/:height
Subscribe to a stream of leaves, in order, starting from the given height.
height
integer
Height of the first leaf to yield
LeafResponse
/availability/header
/availability/header/:height
/availability/header/hash/:hash
/availability/header/payload-hash/:payload-hash
height
integer
Height of the header to fetch
hash
tagged<BLOCK>
Hash of the header to fetch
payload-hash
tagged<HASH>
Hash of the payload of the header to fetch. Note that block payloads are not necessarily unique. If there are multiple blocks whose payload matches this hash, .
Header
/availability/header/:from/:until
Retrieve a range of consecutive headers.
from
integer
Height of the first header to fetch
until
integer
Height just after the last header to fetch
[Header]
/availability/stream/headers/:height
Subscribe to a stream of headers, in order, starting from the given height.
height
integer
Height of the first header to yield
Header
/availability/block
/availability/block/:height
/availability/block/hash/:hash
/availability/block/payload-hash/:payload-hash
height
integer
Height of the block to fetch
hash
tagged<BLOCK>
Hash of the block to fetch
payload-hash
tagged<HASH>
Hash of the payload of the block to fetch. Note that block payloads are not necessarily unique. If there are multiple blocks whose payload matches this hash, .
BlockResponse
/availability/block/:from/:until
Retrieve a range of consecutive blocks.
from
integer
Height of the first block to fetch
until
integer
Height just after the last block to fetch
[BlockResponse]
/availability/stream/blocks/:height
Subscribe to a stream of blocks, in order, starting from the given height.
height
integer
Height of the first block to yield
BlockResponse
/availability/block/summary
/availability/block/summary/:height
height
integer
Height of the block to fetch
BlockSummary
/availability/block/summaries/:from/:until
Retrieve a range of consecutive block summaries.
from
integer
Height of the first block summary to fetch
until
integer
Height just after the last block summary to fetch
[BlockSummary]
/availability/payload
/availability/payload/:height
/availability/payload/block-hash/:block-hash
/availability/payload/hash/:hash
height
integer
Height of the block whose payload should be fetched
block-hash
tagged<BLOCK>
Hash of the block whose payload should be fetched
hash
tagged<HASH>
Hash of the payload to fetch. Note that block payloads are not necessarily unique. If there are multiple payloads matching this hash, .
PayloadResponse
/availability/payload/:from/:until
Retrieve a range of consecutive payloads.
from
integer
Height of the first payload to fetch
until
integer
Height just after the last payload to fetch
[PayloadResponse]
/availability/stream/payloads/:height
Subscribe to a stream of payloads, in order, starting from the given height.
height
integer
Height of the first payload to yield
PayloadResponse
/availability/vid/common
/availability/vid/common/:height
/availability/vid/common/hash/:hash
/availability/vid/common/payload-hash/:payload-hash
height
integer
Height of the block whose VID common data should be fetched
hash
tagged<BLOCK>
Hash of the block whose VID common data should be fetched
payload-hash
tagged<HASH>
Hash of the payload of the block whose VID common data should be fetched. Note that block payloads are not necessarily unique. If there are multiple blocks whose payload matches this hash, .
VidCommonResponse
/availability/stream/vid/common/:height
Subscribe to a stream of VID common objects, in order, starting from the given height.
height
integer
Height of the first VID common to yield
VidCommonResponse
/availability/block/:height/namespace/:namespace
Get the list of transactions in a block from a given namespace, along with a proof that these are only and all such transactions from that block. Note that the proof may be null
if transactions
is empty, in which case the caller should check the namespace table for the specified block to confirm that :namespace
is not present.
height
integer
Height of the block containing the desired namespace
namespace
integer
ID of the desired namespace
/availability/transaction
/availability/transaction/:height/:index
/availability/transaction/hash/:hash
height
integer
Height of the block containing the desired transaction
index
integer
0-based position of the desired transaction in its block
hash
tagged<TX>
Hash of the desired transaction. Note that transactions are not necessarily unique. If there are multiple transactions matching this hash, .
/availability/limits
Get implementation-defined limits restricting certain requests.
small_object_range_limit
: the maximum number of small objects which can be loaded in a single range query. Currently small objects include leaves only. In the future this limit will also apply to headers, block summaries, and VID common, however
loading of headers and block summaries is currently implemented by loading the entire block
imperfect VID parameter tuning means that VID common can be much larger than it should
large_object_range_limit
: the maximum number of large objects which can be loaded in a single range query. Large objects include anything that might contain a full payload or an object proportional in size to a payload. Note that this limit applies to the entire class of objects: we do not check the size of objects while loading to determine which limit to apply. If an object belongs to a class which might contain a large payload, the large object limit always applies.
Returns
/state-cert/epoch
Get the light client state update certificate for the given epoch.
The light client state update certificate consists of the list of Schnorr signatures of the light client state at the end of the epoch. This is used to update light client state in the contract so that it have the new stake table information for the next epoch.
epoch
integer
Epoch number containing the desired state cert
Returns
The response contains the hash of the transaction, the hash and height of the block that contains it, and its index within that block. It also contains a TransactionInclusionProof
, which proves inclusion of this transaction in the block with block_hash
. The specific format of this type is not currently specified, but it can be deserialized and interpreted in Rust using the type.