ethernauta

To structure Ethereum JSON-RPC methods safely, use typed resolver shapes that distinguish readable, writable, and signable operations, enforcing factories over early execution. This prevents implementation drift by aligning new code with strict package boundaries and schema-validated invariants.

The best way to handle multi-transport fallback for Ethereum JSON-RPC requests is using Promise.any() for transport dispatch. This standardizes fallback behavior across multiple transports, replacing sequential logic or Promise.all() to ensure safer and more reliable request routing.

CAIP-2 chain-id handling for wallet signing flows works by enforcing strict chain identifiers across signer-provider splits. It ensures correct network targeting during wallet interactions, using postMessage correlation IDs to securely route and validate extension messaging protocols.

Valibot validation boundaries are used in an Ethereum library to enforce security and correctness invariants on every data boundary. Applying Valibot ensures that parameters and results are strictly schema-validated, preventing invalid data from entering wallet-side signing or JSON-RPC flows.

To add a new eth_* method following Ethernauta's factory pattern, implement the method using typed resolver shapes, validate parameters and results with Valibot schemas, dispatch via Promise.any across transports, and export it through the correct package index paths.

Wiring wallet-side signing flows without strict package layering risks circular dependencies and security leaks. Correct implementation requires keeping wallet and EIP modules layered on top of transport utilities, ensuring signer-provider splits and strict naming conventions are maintained.