https://github.com/alloy-rs/op-alloy
Transports, Middleware, and Networks for the OP Stack built on Alloy
https://github.com/alloy-rs/op-alloy
blockchain ethereum optimism
Last synced: 6 days ago
JSON representation
Transports, Middleware, and Networks for the OP Stack built on Alloy
- Host: GitHub
- URL: https://github.com/alloy-rs/op-alloy
- Owner: alloy-rs
- License: apache-2.0
- Created: 2024-04-05T21:01:05.000Z (11 months ago)
- Default Branch: main
- Last Pushed: 2025-02-12T16:12:46.000Z (9 days ago)
- Last Synced: 2025-02-12T16:32:41.429Z (9 days ago)
- Topics: blockchain, ethereum, optimism
- Language: Rust
- Homepage: https://alloy-rs.github.io/op-alloy/
- Size: 5.53 MB
- Stars: 54
- Watchers: 9
- Forks: 47
- Open Issues: 15
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE-APACHE
- Codeowners: .github/CODEOWNERS
- Security: SECURITY.md
Awesome Lists containing this project
- awesome-ethereum-rust - op-alloy
README
# op-alloy
Built on [Alloy][alloy], op-alloy aggregates the OP stack's unique primitives from [Maili][maili],
to the subset of L1 types used by Optimistic rollups.
## Usage
The following crates are provided by `op-alloy`.
- [`op-alloy-consensus`][op-alloy-consensus]
- [`op-alloy-network`][op-alloy-network]
- [`op-alloy-rpc-jsonrpsee`][op-alloy-rpc-jsonrpsee]
- [`op-alloy-rpc-types-engine`][op-alloy-rpc-types-engine]
- [`op-alloy-rpc-types`][op-alloy-rpc-types]
## Development Status
`op-alloy` is currently in active development, and is not yet ready for use in production.
## Supported Rust Versions (MSRV)
The current MSRV (minimum supported rust version) is 1.81.
Unlike Alloy, op-alloy may use the latest stable release,
to benefit from the latest features.
The MSRV is not increased automatically, and will be updated
only as part of a patch (pre-1.0) or minor (post-1.0) release.
## Contributing
op-alloy is built by open source contributors like you, thank you for improving the project!
A [contributing guide][contributing] is available that sets guidelines for contributing.
Pull requests will not be merged unless CI passes, so please ensure that your contribution follows the
linting rules and passes clippy.
## `no_std`
op-alloy is intended to be `no_std` compatible, initially for use in [kona][kona].
The following crates support `no_std`.
Notice, provider crates do not support `no_std` compatibility.
- [`op-alloy-consensus`][op-alloy-consensus]
- [`op-alloy-rpc-types`][op-alloy-rpc-types]
- [`op-alloy-rpc-types-engine`][op-alloy-rpc-types-engine]
If you would like to add no_std support to a crate,
please make sure to update [scripts/check_no_std.sh][check-no-std].
## Credits
op-alloy is inspired by the work of several teams and projects, most notably [the Alloy project][alloy].
This would not be possible without the hard work from open source contributors. Thank you.
## License
Licensed under either of Apache License, Version
2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in these crates by you, as defined in the Apache-2.0 license,
shall be dual licensed as above, without any additional terms or conditions.
[check-no-std]: ./scripts/check_no_std.sh
[maili]: https://github.com/op-rs/maili
[kona]: https://github.com/op-rs/kona
[alloy]: https://github.com/alloy-rs/alloy
[contributing]: https://alloy-rs.github.io/op-alloy
[op-alloy-consensus]: https://crates.io/crates/op-alloy-consensus
[op-alloy-network]: https://crates.io/crates/op-alloy-network
[op-alloy-rpc-jsonrpsee]: https://crates.io/crates/op-alloy-rpc-jsonrpsee
[op-alloy-rpc-types-engine]: https://crates.io/crates/op-alloy-rpc-types-engine
[op-alloy-rpc-types]: https://crates.io/crates/op-alloy-rpc-types