As part of the Hyperbeam Accelerationism manifesto by Decent Land Labs, we continue the mission of bridging the whole component stack of the EVM to HyperBEAM.
And today, we are introducing ~helios@1.0 device, the battle tested EVM consensus light client, encapsulated as a HyperBEAM device.
What is Helios?
Introduced in November 2022 by a16z, Helios is a consensus light client designed for speed, portability, and security. Helios converts an untrusted centralized RPC endpoint into a safe, unmanipulable and verifiable JSON-RPC for its users. It has fast synchronization, requires no storage, and is lightweight.
Introducing ~helios@1.0 device
Given our Rust-flavored tech stack, we have decided to port Helios to HyperBEAM. The ~helios@1.0 device in its current implementation (at the time of writing), initiates the Helios client (and JSON-RPC server) at the start of the HyperBEAM node run. The JSON-RPC server is spawned as a separate process running in parallel behind the 8545 port (standard consensus RPC port).
The light client RPC methods follow Ethereum’s JSON-RPC specification, for the full list of supported methods, please refer to the Helios documentation
Check out the source code of the ~helios@1.0 device in loadnetwork/load_hb repo
Try it now
The ~helios@1.0 device is supported in the experimental HyperBEAM node instance run by us, hb.load.rs – the device is configured with support for Ethereum mainnet, which means, you can curl the eth.rpc.rs JSON-RPC API to interact with the device!
curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' https://eth.rpc.rsWhat’s next
The ~helios@1.0 device is marking our second step in the EVM HyperBEAM after the ~evm@1.0 revm execution machine device (ultraviolet.load.network) – in the next few weeks we will introduce more upgrades to the helios devices making it multichain (EVM) with Load Network Alphanet support!