OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Developer Tools

Alloy

Alloy is an open-source Rust library of crates for connecting applications to Ethereum-based blockchains. It includes provider, transport, middleware, network, contract, RPC and signer components that developers can combine in blockchain-enabled software.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Alloy — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Alloy when a Rust application needs blockchain connectivity and you want to select from provider, transport, network and related crates. Consult the feature list and examples when choosing optional integrations.

Who it is for

  • Rust developers building applications that need Ethereum or Ethereum-compatible blockchain connectivity.
  • Backend developers assembling provider, transport or middleware integrations.
  • Developers creating Rust tooling for blockchain networks.

Documented uses

  • Connect an application to an Ethereum node through a provider.
  • Query node data such as the latest block number and chain ID.
  • Add contract interaction, RPC types or signer components to a Rust project.
  • Select network and transport features for an application’s blockchain connection.
Before you choose

Requirements & limits

The project is open source under the Apache-2.0 license and is distributed as Rust crates through Cargo.

  • The primary integration is a Rust library, so it fits Rust projects rather than providing a ready-made hosted application.
  • Default features include contracts, an HTTP provider, Ethereum RPC types and a local signer.
  • The full feature adds WebSocket and IPC transports plus commonly used extended RPC APIs, but does not include every optional integration.
  • Node bindings, ENS, genesis and trie support, and cloud or hardware signers require separate opt-in features or crates.
  • The documentation demonstrates a network-generic provider pattern, including an Optimism example using op-alloy.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Add Alloy and select connectivity features

Include Alloy in a Rust project and choose the documented default or expanded provider feature set.

Before you start

  • A Rust project that uses Cargo

Steps

  1. Add the alloy crate with the command below, or specify alloy = "2" in Cargo.toml.

    Documented command
    cargo add alloy

  2. Use the default features for contracts, an HTTP provider, Ethereum RPC types and a local signer.

  3. For WebSocket and IPC transports plus commonly used extended RPC APIs, add Alloy with the full feature.

  4. Enable additional integrations such as node bindings separately when needed; full does not include them.

Expected outcome

The Rust project has Alloy configured with either its default feature set or the documented `full` convenience bundle.

Guide limitations

  • full does not include every optional integration.
  • The setup steps do not cover application-specific configuration or deployment.
Documentation 1 ↗
Source-based practical guide

Connect a provider and query Ethereum node data

Use Alloy’s documented HTTP provider pattern to request the latest block number and chain ID.

Before you start

  • A Rust project with Alloy’s default features
  • An Ethereum node RPC URL

Steps

  1. Create a provider with ProviderBuilder and connect it to the node’s RPC URL.

  2. Use the provider to request the latest block number.

  3. Request the chain ID and handle the results in the application.

Expected outcome

The application has a provider connection pattern for querying the latest block number and chain ID.

Guide limitations

  • The example uses a particular public RPC URL; no provider service terms or reliability are specified.
  • The documented example does not provide deployment instructions.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
2 October 2026
Original website title
alloy-rs/alloy · Official homepage title · retained in its source language
How we review sourcesSuggest a correction

Related options

ethers-rs — Alloy is described by its project documentation as a ground-up rewrite of ethers-rs.