WeaveVM (WVM)
  • WeaveVM (WVM)
  • About WeaveVM
    • Overview
    • Network Releases Nomenclature
    • WeaveVM Alphanets
    • Key Features
    • ELI5
  • Using WeaveVM
    • Compatibility
    • Network configurations
    • WeaveVM Bundler
    • WeaveVM Bundler Gateways
    • wvm:// Data Protocol
    • WeaveVM Precompiles
    • WeaveVM-Native JSON-RPC Methods
    • Self-Hosted RPC Proxies
      • Rust Proxy
      • JavaScript Proxy
    • Code & Integrations Examples
      • ether-rs
      • ethers (etherjs)
      • Deploying an ERC20 Token
  • WeaveVM for evm chains
    • Ledger Archiver (any chain)
    • Ledger Archivers: State Reconstruction
    • DA ExEx (Reth-only)
    • Deploying OP-Stack Rollups
  • WeaveVM ExEx
    • About ExExes
    • ExEx.rs
    • WeaveVM ExExes
      • MLExEx
      • Google BigQuery ETL
      • Borsh Serializer
      • Arweave Data Uploader
      • WeaveVM DA ExEx
      • WeaveVM WeaveDrive ExEx
  • WeaveVM Arweave Data Protocols
    • WeaveVM-ExEx Data Protocol
    • WeaveVM Precompiles Data Protocol
  • DA Integrations
    • WeaveVM-EigenDA Proxy Server
    • WeaveVM - Dymension.xyz: DA client for RollAP
  • WeaveVM Stack Hacks
    • About WeaveVM Stack Hacks
    • Data Availability Hacks
  • MEM Lambda
    • About MEM
    • About MEM Lambda
    • Parallel Execution
    • MEM Lambda Sequencer
    • Contract Example: Counter
  • WeaveVM R&D
    • About R&D
    • elciao
    • ERC-7689
    • WeaveVM & VACP
  • Sunset Network Versions
    • About Sunset Network Versions
    • WeaveVM Alphanet V1
Powered by GitBook
On this page
  • Centralized Block Producing
  • Large Block Size
  • High-Throughput DA
  • Parallel Execution
  • EVM interface for Arweave Data: Permanent History
  • Cost Efficient Data Settling
  • WeaveVM is L0 for EVM L1s/L2s
  • Bidirectional data pipeline with Arweave
  1. About WeaveVM

Key Features

Exploring WeaveVM key features

PreviousWeaveVM AlphanetsNextELI5

Last updated 5 months ago

Let's explore the key features of WeaveVM:

Centralized Block Producing

WeaveVM achieves enterprise-like performance by centralizing block production while maintaining trustless and decentralized block validation.

However, "centralized" here means anyone with a sufficient amount of WVM tokens meeting the PoS staking threshold, plus the necessary hardware and internet connectivity (super-node, enterprise hardware), can run a node. This approach is inspired by Vitalik Buterin's work in post.

Block production is centralized, block validation is trustless and highly decentralized, and censorship is still prevented.

These "super nodes" producing WeaveVM network blocks result in a high-performance EVM network.

Large Block Size

Raising the gas limit increases the block size and operations per block, affecting both History growth and State growth (mainly relevant for our point here).

WeaveVM Alphanet V2 has raised the gas limit to 500M gas (doing 500 mg/s), and lowered the gas per non-zero byte to 8. These changes have resulted in a larger max theoretical block size of 62 MB, and consequently, the network data throughput is 62 MBps.

This high data throughput can be handled thanks to the approach of centralized block production by super nodes and hardware acceleration.

High-Throughput DA

Up until now, there's been no real-world, scalable DA layer ready to handle high data throughput with permanent storage. In WeaveVM Alphanet V2, we've already reached 62 MBps with a projection to hit 125 MBps in mainnet.

Parallel Execution

To reduce the gas fees consumed by EVM opcode execution, we're aiming to use a parallel execution EVM client for the Reth node in mainnet.

EVM interface for Arweave Data: Permanent History

WeaveVM uses a set of Reth execution extensions (ExExes) to serialize each block in Borsh, then compress it in Brotli before sending it to Arweave. These computations ensure a cost-efficient, permanent history backup on Arweave. This feature is crucial for other L1s/L2s using WeaveVM for data settling.

In the diagrams below, we show the difference between various compression algorithms applied to Borsh-serialized empty block (zero transactions) and JSON-serialized empty block.

We can see that Borsh serialization combined with Brotli compression gives us the most efficient compression ratio in the data serialization-compression process.

Cost Efficient Data Settling

Even compared to temporary blob-based solutions, WeaveVM still offers a significantly cheaper permanent data solution (calldata).

WeaveVM is L0 for EVM L1s/L2s

As a sovereign rollup, WeaveVM it can be used as either a DA solution or for data settlement (like Ethereum). Since storing data on WeaveVM is very cheap compared to other EVM solutions, the network can be labeled as an L0 for other L1s or L2s.

Bidirectional data pipeline with Arweave

WeaveVM's hyper computation, supercharged hardware, and interface with Arweave result in significantly cheaper data settlement costs on WeaveVM, which include the Arweave fees to cover the archiving costs. .

WeaveVM offers self-DA secured by network economics along with a permanent data archive, secured by .

The WeaveVM team has developed the first precompiles that achieve a native bidirectional data pipeline with the Arweave network. In other words, with these precompiles (currently supported by WeaveVM testnet), you can read data from Arweave and send data to Arweave trustlessly and natively from a Solidity smart contract.

Check the comparison calculator for realtime data
Arweave
Learn more about WeaveVM precompiles in this section.
"The Endgame"
Ethereum Scaling Bottlenecks
Borsh-serialized empty block
JSON-serialized empty block
EVM L2 architectures, including WeaveVM's EVM L0 Framework (ELF)