# \~helios\@1.0 device

### About

The `~helios@1.0` device is an EVM/Ethereum consensus light client built into the HyperBEAM devices stack. With helios, node operators can trustlessly connect to EVM RPCs with a very lightweight, multichain and secure setup, and no historical syncing overhead. With this device, every hyperbeam node can turn into a verifiable EVM RPC endpoint.

#### What is Helios?

> Helios is a trustless, efficient, and portable multichain light client written in Rust.

> Helios converts an untrusted centralized RPC endpoint into a safe unmanipulable local RPC for its users. It syncs in seconds, requires no storage, and is lightweight enough to run on mobile devices.

> Helios has a small binary size and compiles into WebAssembly. This makes it a perfect target to embed directly inside wallets and dapps.

Check out the official repository [here](https://github.com/a16z/helios)

### \~helios\@1.0 device

The `~helios@1.0` as per its current implementation, 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 device supports all of the methods supported by helios. Check the full list [here](https://github.com/a16z/helios/blob/master/rpc.md)

#### Endpoint

As this device is supported on the [hb.load.rs](https://hb.load.rs) hyperbeam node, it's explicitly assigned the `eth.rpc.rs` endpoint for the Ethereum mainnet network.

#### Example

**local**

```bash
curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' http://127.0.0.1:8545
```

**using rpc.rs**

```bash
curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' https://eth.rpc.rs
```

device source code: <https://github.com/loadnetwork/load_hb/tree/main/native/helios_nif>&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.load.network/load-hyperbeam/helios-1.0-device.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
