Today we are excited to announce Load Network’s programmable EVM data integration within the Zentra tech stack. With this integration, Load Network continues to offer its highly scalable and cost efficient programmable EVM data, backed out-of-the-box by Arweave permanence.
What is Zentra?
Zentra is an execution engine for building decentralized applications in Python instead of traditional smart contract languages.
The system uses a hybrid architecture where consensus and RPC operations run on established networks like Base, while Python code execution happens within Zentra nodes. This separation enables complex, long-running, and asynchronous computations that would face gas limitations on conventional blockchains.
“The blockchain’s built-in consensus layer remains responsible only for agreeing on the order and contents of transactions (the “inputs”), while the indexer is responsible for computing the resulting new state.” - Zentra
Zentra treats global state space as a scarce resource to prevent uncontrollable state growth and ensure that anyone can run an indexer. This design encourages developers to write reusable code components, similar to Solana’s program architecture, rather than deploying numerous single-use smart contracts. The approach aims to lower barriers for non-developers who can build dApps using existing, tested code.
Zentra’s execution flow:
- Zentra code deploys to a home chain (currently Sepolia, Base is planned)
- User interactions post as calldata to that chain
- Computation occurs in Python within the Zentra network
- Indexers compute the final result, given the inputs and code enshrined onchain
This architecture maintains the security and finality of the underlying consensus layer while enabling more sophisticated computational capabilities. The platform is designed to be consensus-agnostic, with potential future deployments on additional EVM chains including Load Network.
About the integration: Zentra-sp
The Zentra integration consists of load-backed Zentra storage provider REST API, built on top of load0 programmable evm data. In simple terms, Zentra-sp API takes a Zentra function call’s txid (currently supports base sepolia network), downloads the tx data and finally stores it on the Load Network via load0 storage layer.
Zentra-sp ensures that only Zentra’s sequencer (indexer) protocol specific transactions (defined by tx sender and receiver) are accepted to get stored on load0:
- 0x00000000000000000000000000000000007a656e
- 0xbBe844467051fE04CCE050efB42cF824431d1e52
An example of storing this Zentra’s function transaction data on load0 is as follows:
load0 txid: 0x365d377…64c018c0cd4
Check out the storage provider source code here.
Further collaboration
We took our collaboration with Zentra from the sequencer level a step further to reach Zentra’s userbase. Zentra users will have access to Load Network Cloud Platform and benefits from a cloud credits grants to use Load Cloud’s main products:
- IPFS pinning service with Arweave and load0 storage sidecars
- S3 object storage with Arweave and load0 storage sidecars
Conclusion
The ecosystem of the onchain data center, continues to grow and drive new storage demand for Load Network and the Arweave ecosystem.
Zentra’s usage of load0 data layer, and the Load Cloud showcase the continuous demand of permanent storage, EVM data programmability and interface compatibility. And last but not least, the demand for a web2 storage pipeline with decentralization guarantees at the storage provider layer.