Practical overview
When it fits
Use it when building or evaluating a rollup workflow that submits data to NEAR and needs a way to check submission inclusion. Plan explicitly for contract deployment, sidecar configuration and data retrieval through archival nodes or indexers.
Who it is for
- Rollup teams evaluating NEAR for data-availability storage.
- Developers integrating blob submission and verification into rollup systems.
- Rust developers who want to use the project’s DA RPC client.
Documented uses
- Store arbitrary data blobs without placing blob contents directly in NEAR blockchain state.
- Submit rollup sequencing data and obtain transaction IDs for a blob commitment.
- Check transaction or receipt inclusion with the NEAR light client.
- Connect rollup software to NEAR DA through an HTTP sidecar or Rust client.
Requirements & limits
The repository is public and licensed under MIT. Its documented setup requires a funded NEAR account and development tooling; the project describes deploying the contract and sidecar yourself.
- Blob contents are not stored directly in NEAR blockchain state; the design relies on NEAR receipt consensus and transaction data retention outside state.
- A blob commitment can comprise multiple NEAR transaction IDs, depending on blob size.
- The README describes at least three NEAR epochs of function-input retention on full nodes, with longer retention possible from archival nodes; indexers can also provide data.
- The project recommends the HTTP sidecar for most rollup SDKs, while retaining a Rust client crate for Rust applications.
- The README identifies integrations with OP Stack, Polygon CDK and Arbitrum Nitro, but says reference implementations are in flux and may not be production-grade.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Prepare the contract and sidecar setup
Set up the documented prerequisites and configuration path for deploying a NEAR DA contract and sidecar.
Before you start
- A NEAR account with funds and permission to deploy the contract.
- Rust, Go, CMake and related native build tools; alternatively, the README describes using Nix with direnv.
- The near-cli-rs version of NEAR CLI, contract keys, and synced Git submodules if the repository was cloned without them.
Steps
Clone the repository and prepare its documented development prerequisites.
Build your contract with the command below if using your own contract, and set the required keys and deployment address as described in the repository.
make build-contractsConfigure the sidecar through
http-config.jsonor its documented PUT/configureoption, then deploy it using the repository’s Docker Compose file.
Expected outcome
The documented setup path prepares a contract and configures the HTTP sidecar to interact with NEAR DA.
Guide limitations
- This guide covers setup, not a completed deployment or a blob submission.
- Contract deployment requires appropriate permission; the README notes the reference integrations are in flux and not necessarily production-grade.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- Nuffle-Labs/data-availability · Official homepage title · retained in its source language

