Quickstart
Get set up with the onchain data center
Let's make it easy to get going with Load Network. In this doc, we'll go through the simplest ways to use Load across the most common use cases:
Upload data
As a non-developer: LCP
The easiest way to interface with Load Network storage capabilities is through the cloud web app: cloud.load.network, Load Cloud Platform. The LCP platform is powered by HyperBEAM's LS3 storage layer and offer programmatic access through load_acc API keys.
As a developer
Load S3 Temporary Data Storage Layer (highly recommended)
The best data pipeline for massive uploads is to use the Load [email protected] HyperBEAM powered storage layer. The LS3 storage layer, run through a special set of HyperBEAM nodes, have the S3 objects serialized as ANS-104 DataItems by default, maintaining provenance and integrity when the uploader wishes to move the S3 object from the temporal storage layer to Arweave in a single HTTP API request.
Highly scalable bundling service
To load huge amount of data to Load Network EVM L1 without being tied to the technical network limitations (tx size, block size, network throughput), you can use the load0 bundling service. It's a straightforward REST-based bundling service that let you upload data and retrieve it instantly, at scale:
curl -X POST "https://load0.network/upload" \
--data-binary "@./video.mp4" \
-H "Content-Type: video/mp4"For more examples, check out the load0 documentation
Using ARIO's Turbo SDK
One of the coolest features offered by the LS3 layer's compatibility with the ANS-104 data standard is the out-of-the-box compatibility with the Arweave ecosystem despite being an offchain temporary storage layer. For that reason, we have built an ANS-104 upload service on top of LS3, compatible with ARIO's Turbo standard, meaning you can use the Turbo official SDK along with Load's custom upload service endpoint to store temporary Arweave dataitems. check out how to use it and learn more about xANS-104 data provenance, lineage and governance here.
Integrating ledger storage
Chains like Avalanche, Metis and RSS3 use Load Network as a decentralized archive node. This works by feeding all new and historical blocks to an archiving service you can run yourself, pointed to your network's RPC.
As well as storing all real-time and historical data, Load Network can be used to reconstruct full chain state, effectively replicating exactly what archive nodes do, but with a decentralized storage layer underneath. Read here to learn how.
Using Load DA
With 125mb/s data throughput and long-term data guarantees, Load Network can handle DA for every known L2, with 99.8% room to spare.
Right now there are 4 ways you can integrate Load Network for DA:
DIY
DIY docs are a work in progress, but the commit to add support for Load Network in Dymension can be used as a guide to implement Load DA elsewhere.
Migrate from another storage layer
If your data is already on another storage layer like IPFS, Filecoin, Swarm or AWS S3, you can use specialized importer tools to migrate.
Load S3 Storage Layer
The HyperBEAM Load S3 node provides a 1:1 compatible development interface for applications using AWS S3 for storage, keeping method names and parameters in tact so the only change should be one line: the endpoint.
Filecoin
The load-lassie import tool is the recommended way to easily migrate data stored via Filecoin.
Just provide the CID you want to import to the API, e.g.:
https://lassie.load.rs/import/<CID>
The importer is also self-hostable and further documented here.
Swarm
Switching from Swarm to Load is as simple as changing the gateway you already use to resolve content from Swarm.
before: https://api.gateway.ethswarm.org/bzz/<hash>
after: https://swarm.load.rs/bzz/<hash>
The first time Load's Swarm gateway sees a new hash, it uploads it to Load Network and serves it directly for subsequent calls. This effectively makes your Swarm data permanent on Load while maintaining the same hash.
Last updated