alloy-transport
| Crates.io | alloy-transport |
| lib.rs | alloy-transport |
| version | |
| source | src |
| created_at | 2023-11-15 21:28:58.944095 |
| updated_at | 2024-12-10 11:16:45.863491 |
| description | Low-level Ethereum JSON-RPC transport abstraction |
| homepage | https://github.com/alloy-rs/alloy |
| repository | https://github.com/alloy-rs/alloy |
| max_upload_size | |
| id | 1036855 |
| Cargo.toml error: | TOML parse error at line 23, column 1 | 23 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
core (github:alloy-rs:core)
documentation
README
alloy-transport
Low-level Ethereum JSON-RPC transport abstraction.
This crate handles RPC connection and request management. It builds an
RpcClient on top of the tower Service abstraction, and provides
futures for simple and batch RPC requests as well as a unified TransportError
type.
Typically, this crate should not be used directly. Most EVM users will want to use the alloy-provider crate, which provides a high-level API for interacting with JSON-RPC servers that provide the standard Ethereum RPC endpoints, or the [alloy-rpc-client] crate, which provides a low-level JSON-RPC API without the specific Ethereum endpoints.
Transports
Alloy maintains the following transports:
- alloy-transport-http: JSON-RPC via HTTP.
- alloy-transport-ws: JSON-RPC via Websocket, supports pubsub via alloy-pubsub.
- alloy-transport-ipc: JSON-RPC via IPC, supports pubsub via alloy-pubsub.