chains
chains copied to clipboard
Canonical type definitions for EIP-155 chains
Looks like Arbitrum mainnet's `average_blocktime_hint` is currently set to 1.3sec: https://github.com/alloy-rs/chains/blob/0eaf7000dc3d21e47c52bfa57a72a87e28861621/src/named.rs#L357 Requesting for this to be updated to ~.25sec Recent block: https://arbiscan.io/block/170000000 Human: Jan-13-2024 09:21:33 AM +UTC Unix: 1705137693 Block...
couldnt find an actual etherscan endpoint -.-
Adds the new SKALE Chains built on top of Base aka the SKALE Base Chains. This PR adds for both testnet and Mainnet
when deserializing `Chain` the output depends on underlying chain kind. I think it would be less surprising to always deserde into the chain id w/ deserde into the name being...
So viem in its chain definitions has multicall3 address. I think this would be helpful for alloy chains definitions also. Multicall3 address are already fairly standardised in most popular chain...
We currently only allow a single `(api_url, explorer_url)` pair per chain. Ideally we would per chain a way to define a type like `Blockscout("foo", "bar")`, `Etherscan("baz", "qux")` To make it...