Csur 2025-03-06 #414
Csur 2025-03-06 #414
Conversation
bdrhn9
left a comment
bdrhn9
left a comment
There was a problem hiding this comment.
While deploying contracts, did you use customized technique to manage it? I'm asking because of this dual-block architecture.
As I understand, small blocks (2M gas limit, 2 seconds interval) refers to default EVM blocks and without need any customization in RPC calls. Because test update spent ~300k gas, I won't expect any issue from Airseeker side
data/chains/hyper-evm.json
Outdated
| @@ -0,0 +1,23 @@ | |||
| { | |||
| "alias": "hyper-evm", | |||
There was a problem hiding this comment.
As seen in the docs, HyperEVM is only the EVM component of the Hyperliquid blockchain, while the other part is HyperCore. Since there is only one EVM component, I'd prefer to use hyperliquid.
| { | ||
| "alias": "default", | ||
| "rpcUrl": "https://rpc.hyperliquid.xyz/evm" | ||
| } |
There was a problem hiding this comment.
I recommend adding https://rpc.hypurrscan.io as well. A nslookup check confirms that it originates from a different source.
data/chains/hyper-evm.json
Outdated
| "browserUrl": "https://hyperliquid.cloud.blockscout.com/" | ||
| }, | ||
| "id": "999", | ||
| "name": "HyperEVM", |
There was a problem hiding this comment.
Similarly, HyperEVM identifies EVM front of Hyperliquid chain. So I'd name this chain as Hyperliquid.
Yes I had to use an account that big-blocks is enabled for certain contract deployments. It was inevitable. |
…-testnet, and update related configurations
| }, | ||
| "url": "https://hyperliquid.cloud.blockscout.com/api" | ||
| }, | ||
| "browserUrl": "https://hyperliquid.cloud.blockscout.com/" |
There was a problem hiding this comment.
Maybe the official one is preferable even without contract verification
Related to https://github.com/api3dao/tasks/issues/1649, https://github.com/api3dao/data-feeds/issues/2562
This PR adds following chains: