FAQ

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.17.0. The library tracks Zig stable releases; CI runs against the pinned minimum version.

How fast is eth.zig, and how is that measured?

The benchmark suite tracks the ten operations that dominate bot and searcher hot loops (Keccak-256, secp256k1 sign/recover, transaction hashing, ABI encode/decode, u256 mulDiv, a Uniswap V4 swap step and Universal Router decoding). Each release is compared against eth.zig's previous releases on the same machine.

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 18/26 benchmarks (alloy 1.6/2.0, run 2026-06-10), with the biggest wins in RLP transaction encoding (24.33x), ABI decoding (8.41x), secp256k1 sign+recover (4.23x), secp256k1 signing (2.34x), u256 division (3.43x), and mulDiv (1.82x), plus 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.