FAQ
Frequently asked questions about eth.zig.
Is eth.zig production-ready?
eth.zig is at v0.2.2. All listed features are complete and tested, but the library is young. It's suitable for infrastructure projects, bots, and tools. Evaluate for your risk tolerance before using in high-value production systems.
What Zig version do I need?
Zig >= 0.15.2. The library tracks Zig stable releases and is also tested against nightly builds in CI.
How does secp256k1 signing compare to alloy.rs?
eth.zig wins on secp256k1 signing -- 2.10x faster than alloy.rs for signing and 4.04x faster for sign+recover.
eth.zig wins 23 of 26 benchmarks overall. alloy.rs wins only on address hex parsing (1.36x, SIMD).
Does eth.zig support all Ethereum transaction types?
Yes:
- Legacy (Type 0) -- pre-EIP-1559
- EIP-2930 (Type 1) -- access lists
- EIP-1559 (Type 2) -- priority fees
- EIP-4844 (Type 3) -- blob transactions
EIP-7702 transactions are planned.
Which chains are supported?
eth.zig includes chain definitions for:
- Ethereum (mainnet + Sepolia + Holesky)
- Arbitrum (One + Sepolia)
- Optimism (mainnet + Sepolia)
- Base (mainnet + Sepolia)
- Polygon (mainnet + Amoy)
Any EVM-compatible chain works -- these are just convenience configurations.
Can I use eth.zig for MEV / HFT?
Yes, that's a primary use case. eth.zig beats alloy.rs on 23/26 benchmarks, with the biggest wins in secp256k1 signing (2.10x), ABI decoding (8.00x), u256 arithmetic (up to 3.43x), mulDiv (1.71x), and comptime selectors (zero-cost at runtime).
How do I report a security vulnerability?
See SECURITY.md. Email security@strobelabs.com. We acknowledge reports within 48 hours.
Is there a Discord or community chat?
Follow @StrobeLabs on Twitter for updates. Community channels are coming soon.
How can I contribute?
See the Contributing guide. We welcome PRs, bug reports, and feature requests.