It's a service that wraps the , exposing endpoints for interacting with the EigenDA disperser in conformance to the , and adding disperser verification logic. This simplifies integrating EigenDA into various rollup frameworks by minimizing the footprint of changes needed within their respective services.
About WeaveVM-EigenDA Side Server Proxy Integration
It's a WeaveVM integration as a secondary backend of eigenda-proxy. In this scope, WeaveVM provides an EVM gateway/interface for EigenDA blobs on Arweave's Permaweb, removing the need for trust assumptions and relying on centralized third party services to sync historical data and provides a "pay once, save forever" data storage feature for EigenDA blobs.
Key Details
WeaveVM is a data-centric sovereign EVM L1, specialized with high data throughput (~60 MB/s in Alphanet v3) and permanent data storage interface with Arweave.
Current maximum encoded blob size is 8 MiB (8_388_608 bytes).
WeaveVM currently operating in public testnet (Alphanet) - not recommended to use it in production environment.
Prerequisites and Resources
Review the configuration parameters table and .env file settings for the Holesky network.
Obtain test tWVM tokens through our for testing purposes.
Monitor your transactions using the .
Usage Examples
Please double check .env file values you start eigenda-proxy binary with env vars.
They may conflict with flags.
curl -X POST "http://127.0.0.1:3100/put?commitment_mode=simple" \
--data-binary "some data that will successfully be written to EigenDA" \
-H "Content-Type: application/octet-stream" \
--output response.bin
is a tool by Consensys which allows remote signing.
Using a remote signer comes with risks, please read the web3signer docs. However this is a recommended way to sign transactions for enterprise users and production environments.
Web3Signer is not maintained by WeaveVM team.
Example of the most simple local web3signer deployment (for testing purposes):