CipherLabs
/
hyperlane-monorepo
mirror of https://github.com/hyperlane-xyz/hyperlane-monorepo
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
The home for Hyperlane core contracts, sdk packages, and other infrastructure
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2857 Commits
486 Branches
328 Tags
236 MiB
Tag: Branch: Tree: 63d58cd612
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '63d58cd612'
${ noResults }
hyperlane-monorepo/rust/sealevel/environments/mainnet3/chain-config.json

3455 lines
78 KiB
Raw Normal View History Unescape

feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
{
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"ancient8": {
"blockExplorers": [
{
"apiUrl": "https://scan.ancient8.gg/api",
"family": "blockscout",
"name": "Ancient8 Explorer",
"url": "https://scan.ancient8.gg"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 888888888,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Ancient8",
"domainId": 888888888,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://safe.ancient8.gg/txs/",
"isTestnet": false,
"name": "ancient8",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.ancient8.gg"
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "opstack"
},
"alephzeroevm": {
"blockExplorers": [
{
"apiUrl": "https://evm-explorer.alephzero.org/api",
"family": "blockscout",
"name": "Aleph Zero Explorer",
"url": "https://evm-explorer.alephzero.org"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
"reorgPeriod": 5
},
"chainId": 41455,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Aleph Zero EVM",
"displayNameShort": "Aleph Zero EVM",
"domainId": 41455,
"gasCurrencyCoinGeckoId": "aleph-zero",
"index": {
"from": 3421962
},
"name": "alephzeroevm",
"nativeToken": {
"decimals": 18,
"name": "AZERO",
"symbol": "AZERO"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.alephzero.raas.gelato.cloud"
},
{
"http": "https://alephzero.drpc.org"
}
],
"technicalStack": "arbitrumnitro"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"apechain": {
"blockExplorers": [
{
"apiUrl": "https://apechain.calderaexplorer.xyz/api",
"family": "blockscout",
"name": "ApeChain Explorer",
"url": "https://apechain.calderaexplorer.xyz"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 0.2,
"reorgPeriod": 5
},
"chainId": 33139,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "ApeChain",
"domainId": 33139,
"gasCurrencyCoinGeckoId": "apecoin",
"index": {
"from": 1759561
},
"name": "apechain",
"nativeToken": {
"decimals": 18,
"name": "ApeCoin",
"symbol": "APE"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.apechain.com/http"
}
],
"technicalStack": "arbitrumnitro"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"arbitrum": {
"blockExplorers": [
{
"apiUrl": "https://api.arbiscan.io/api",
"family": "etherscan",
"name": "Arbiscan",
"url": "https://arbiscan.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 42161,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Arbitrum",
"domainId": 42161,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://safe-transaction-arbitrum.safe.global/",
"index": {
"from": 143649797
},
"name": "arbitrum",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://arbitrum.llamarpc.com"
},
{
"http": "https://rpc.ankr.com/arbitrum"
},
{
"http": "https://arb1.arbitrum.io/rpc"
}
],
"technicalStack": "arbitrumnitro"
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"arbitrumnova": {
"blockExplorers": [
{
"apiUrl": "https://api-nova.arbiscan.io/api",
"family": "etherscan",
"name": "Arbiscan Nova",
"url": "https://nova.arbiscan.io/"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
"reorgPeriod": 5
},
"chainId": 42170,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Arbitrum Nova",
"domainId": 42170,
"gasCurrencyCoinGeckoId": "ethereum",
"index": {
"from": 78794208
},
"name": "arbitrumnova",
"nativeToken": {
"decimals": 18,
"name": "Ethereum",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://nova.arbitrum.io/rpc"
}
],
"technicalStack": "arbitrumnitro"
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"astar": {
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"blockExplorers": [
{
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"apiUrl": "https://astar.blockscout.com/api",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"family": "blockscout",
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"name": "Astar Explorer",
"url": "https://astar.blockscout.com"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
],
"blocks": {
"confirmations": 1,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"estimateBlockTime": 13,
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"reorgPeriod": "finalized"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"chainId": 592,
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"displayName": "Astar",
"domainId": 592,
"gasCurrencyCoinGeckoId": "astar",
"name": "astar",
"nativeToken": {
"decimals": 18,
"name": "Astar",
"symbol": "ASTR"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://evm.astar.network"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "polkadotsubstrate"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"astarzkevm": {
"blockExplorers": [
{
"apiUrl": "https://astar-zkevm.explorer.startale.com/api",
"family": "blockscout",
"name": "Astar zkEVM Explorer",
"url": "https://astar-zkevm.explorer.startale.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 3776,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Astar zkEVM",
"domainId": 3776,
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"gasCurrencyCoinGeckoId": "ethereum",
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"name": "astarzkevm",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"nativeToken": {
"decimals": 18,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"name": "Ethereum",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"http": "https://rpc.startale.com/astar-zkevm"
},
{
"http": "https://astar-zkevm-rpc.dwellir.com"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "polygoncdk"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"avalanche": {
"blockExplorers": [
{
"apiUrl": "https://api.routescan.io/v2/network/mainnet/evm/43114/etherscan/api",
"family": "routescan",
"name": "SnowTrace",
"url": "https://snowtrace.io"
}
],
"blocks": {
"confirmations": 3,
"estimateBlockTime": 2,
"reorgPeriod": 3
},
"chainId": 43114,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Avalanche",
"domainId": 43114,
"gasCurrencyCoinGeckoId": "avalanche-2",
"gnosisSafeTransactionServiceUrl": "https://safe-transaction-avalanche.safe.global/",
"name": "avalanche",
"nativeToken": {
"decimals": 18,
"name": "Avalanche",
"symbol": "AVAX"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.ankr.com/avalanche"
},
{
"http": "https://api.avax.network/ext/bc/C/rpc",
"pagination": {
"maxBlockRange": 100000,
"minBlockNumber": 6765067
}
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"b3": {
"blockExplorers": [
{
"apiUrl": "https://explorer.b3.fun/api",
"family": "blockscout",
"name": "B3 Explorer",
"url": "https://explorer.b3.fun"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 1,
"reorgPeriod": 5
},
"chainId": 8333,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "B3",
"domainId": 8333,
"gasCurrencyCoinGeckoId": "ethereum",
"name": "b3",
"nativeToken": {
"decimals": 18,
"name": "Ethereum",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://mainnet-rpc.b3.fun"
}
],
"technicalStack": "opstack"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"base": {
"blockExplorers": [
{
"apiUrl": "https://api.basescan.org/api",
"family": "etherscan",
"name": "BaseScan",
"url": "https://basescan.org"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 10
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 8453,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Base",
"domainId": 8453,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://safe-transaction-base.safe.global/",
"name": "base",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://base.publicnode.com/"
},
{
"http": "https://mainnet.base.org"
},
{
"http": "https://base.blockpi.network/v1/rpc/public"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "opstack"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"bitlayer": {
"blockExplorers": [
{
"apiUrl": "https://api.btrscan.com/scan/api",
"family": "other",
"name": "Bitlayer Explorer",
"url": "https://www.btrscan.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 20
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 200901,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Bitlayer",
"domainId": 200901,
"gasCurrencyCoinGeckoId": "bitcoin",
"name": "bitlayer",
"nativeToken": {
"decimals": 18,
"name": "Bitcoin",
"symbol": "BTC"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.bitlayer.org"
},
{
"http": "https://rpc.bitlayer-rpc.com"
},
{
"http": "https://rpc.ankr.com/bitlayer"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"blast": {
"blockExplorers": [
{
"apiUrl": "https://api.routescan.io/v2/network/mainnet/evm/81457/etherscan/api",
"family": "routescan",
"name": "Blast Explorer",
"url": "https://blastexplorer.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 81457,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Blast",
"domainId": 81457,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://transaction.blast-safe.io",
"name": "blast",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.blast.io"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
{
"http": "https://rpc.ankr.com/blast"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "opstack"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"bob": {
"blockExplorers": [
{
"apiUrl": "https://explorer.gobob.xyz/api",
"family": "blockscout",
"name": "BOB Explorer",
"url": "https://explorer.gobob.xyz"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 60808,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "BOB",
"domainId": 60808,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://transaction.safe.gobob.xyz",
"name": "bob",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.gobob.xyz"
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "opstack"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"bsc": {
"blockExplorers": [
{
"apiUrl": "https://api.bscscan.com/api",
"family": "etherscan",
"name": "BscScan",
"url": "https://bscscan.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"reorgPeriod": "finalized"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 56,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Binance Smart Chain",
"displayNameShort": "Binance",
"domainId": 56,
"gasCurrencyCoinGeckoId": "binancecoin",
"gnosisSafeTransactionServiceUrl": "https://safe-transaction-bsc.safe.global/",
"name": "bsc",
"nativeToken": {
"decimals": 18,
"name": "BNB",
"symbol": "BNB"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.ankr.com/bsc"
},
{
"http": "https://bsc.drpc.org"
},
{
"http": "https://bscrpc.com"
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "other",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"transactionOverrides": {
"gasPrice": 3000000000
}
},
"celo": {
"blockExplorers": [
{
"apiUrl": "https://api.celoscan.io/api",
"family": "etherscan",
"name": "CeloScan",
"url": "https://celoscan.io"
},
{
"apiUrl": "https://explorer.celo.org/mainnet/api",
"family": "blockscout",
"name": "Blockscout",
"url": "https://explorer.celo.org"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 5,
"reorgPeriod": 0
},
"chainId": 42220,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Celo",
"domainId": 42220,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"gasCurrencyCoinGeckoId": "celo",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"gnosisSafeTransactionServiceUrl": "https://safe-transaction-celo.safe.global/",
"name": "celo",
"nativeToken": {
"decimals": 18,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"name": "Celo",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"symbol": "CELO"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://forno.celo.org"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"cheesechain": {
"blockExplorers": [
{
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"apiUrl": "https://fetascan.xyz/api",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"family": "blockscout",
"name": "Fetascan",
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"url": "https://fetascan.xyz"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
],
"blocks": {
"confirmations": 1,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"estimateBlockTime": 30,
"reorgPeriod": 1
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 383353,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "CheeseChain",
"domainId": 383353,
"gasCurrencyCoinGeckoId": "cheese-2",
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"gnosisSafeTransactionServiceUrl": "https://prod.cheese.transaction.keypersafe.xyz/",
"index": {
"from": 50650
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"name": "cheesechain",
"nativeToken": {
"decimals": 18,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"name": "Cheese",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"symbol": "CHEESE"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://cheesechain.calderachain.xyz/http"
}
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
],
"technicalStack": "arbitrumnitro"
},
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"chiliz": {
"blockExplorers": [
{
"apiUrl": "https://api.routescan.io/v2/network/mainnet/evm/88888/etherscan/api",
"family": "routescan",
"name": "Chiliscan",
"url": "https://chiliscan.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
"reorgPeriod": 9
},
"chainId": 88888,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Chiliz",
"domainId": 88888,
"gasCurrencyCoinGeckoId": "chiliz",
"name": "chiliz",
"nativeToken": {
"decimals": 18,
"name": "Chiliz",
"symbol": "CHZ"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.ankr.com/chiliz"
},
{
"http": "https://chiliz.publicnode.com"
}
],
"technicalStack": "other",
"transactionOverrides": {
"maxPriorityFeePerGas": 1000000000
}
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"coredao": {
"blockExplorers": [
{
"apiUrl": "https://scan.coredao.org/api",
"family": "other",
"name": "Core Explorer",
"url": "https://scan.coredao.org"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 21
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 1116,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Core",
"domainId": 1116,
"gasCurrencyCoinGeckoId": "coredaoorg",
"name": "coredao",
"nativeToken": {
"decimals": 18,
"name": "CoreDAO",
"symbol": "CORE"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.coredao.org"
},
{
"http": "https://core.public.infstones.com"
},
{
"http": "https://rpc.ankr.com/core"
},
{
"http": "https://core.drpc.org"
},
{
"http": "https://rpc-core.icecreamswap.com"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"cyber": {
"blockExplorers": [
{
"apiUrl": "https://api.socialscan.io/cyber",
"family": "other",
"name": "Cyber Mainnet Explorer",
"url": "https://cyberscan.co"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 7560,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Cyber",
"domainId": 7560,
"gasCurrencyCoinGeckoId": "ethereum",
"name": "cyber",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.cyber.co"
},
{
"http": "https://cyber.alt.technology"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "opstack"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"degenchain": {
"blockExplorers": [
{
"apiUrl": "https://explorer.degen.tips/api/eth-rpc",
"family": "blockscout",
"name": "Degen Chain Explorer",
"url": "https://explorer.degen.tips"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 10,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 666666666,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Degen",
"domainId": 666666666,
"gasCurrencyCoinGeckoId": "degen-base",
"index": {
"from": 23783929
},
"name": "degenchain",
"nativeToken": {
"decimals": 18,
"name": "Degen",
"symbol": "DEGEN"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.degen.tips"
}
],
"technicalStack": "arbitrumnitro"
},
"dogechain": {
"blockExplorers": [
{
"apiUrl": "https://explorer.dogechain.dog/api",
"family": "blockscout",
"name": "Dogechain Explorer",
"url": "https://explorer.dogechain.dog"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 2000,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Dogechain",
"domainId": 2000,
"gasCurrencyCoinGeckoId": "dogecoin",
"name": "dogechain",
"nativeToken": {
"decimals": 18,
"name": "Dogecoin",
"symbol": "DOGE"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.dogechain.dog"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "polygoncdk"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"eclipsemainnet": {
chore: update SVM ISMs (#4509) ### Description - Updates the enrolled sets on the default ISMs of eclipsemainnet and solanamainnet ### Drive-by changes - stopped reading `type` completely for the multisig ISM configs -- this isn't needed whatsoever and caused issues bc the sealevel tooling would expect a number but infra would generate a string w/ the ISM type name - to support string chain_ids (the case on Cosmos), added some logic - removed `testnet3`, not needed anymore ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
2 months ago
"blockExplorers": [
{
"apiUrl": "https://explorer.eclipse.xyz/api",
"family": "other",
"name": "Eclipse Explorer",
"url": "https://explorer.eclipse.xyz/"
}
],
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"blocks": {
"confirmations": 1,
"estimateBlockTime": 0.4,
"reorgPeriod": 0
},
"chainId": 1408864445,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Eclipse",
"domainId": 1408864445,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"gasCurrencyCoinGeckoId": "ethereum",
"name": "eclipsemainnet",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"nativeToken": {
"decimals": 9,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "sealevel",
"rpcUrls": [
{
"http": "https://mainnetbeta-rpc.eclipse.xyz"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"endurance": {
"blockExplorers": [
{
"apiUrl": "https://explorer-endurance.fusionist.io/api",
"family": "blockscout",
"name": "Endurance Explorer",
"url": "https://explorer-endurance.fusionist.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 12,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 15
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 648,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Endurance",
"domainId": 648,
"gasCurrencyCoinGeckoId": "endurance",
"gnosisSafeTransactionServiceUrl": "https://safewallet.fusionist.io/cgw/api",
"name": "endurance",
"nativeToken": {
"decimals": 18,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"name": "Fusionist",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"symbol": "ACE"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc-endurance.fusionist.io"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"ethereum": {
"blockExplorers": [
{
"apiUrl": "https://api.etherscan.io/api",
"family": "etherscan",
"name": "Etherscan",
"url": "https://etherscan.io"
},
{
"apiUrl": "https://eth.blockscout.com/api",
"family": "blockscout",
"name": "Blockscout",
"url": "https://blockscout.com/eth/mainnet"
}
],
"blocks": {
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"confirmations": 2,
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"estimateBlockTime": 13,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 15
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 1,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Ethereum",
"domainId": 1,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"gasCurrencyCoinGeckoId": "ethereum",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"gnosisSafeTransactionServiceUrl": "https://safe-transaction-mainnet.safe.global/",
"name": "ethereum",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://ethereum.publicnode.com"
},
{
"http": "https://cloudflare-eth.com"
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "other"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
chore: update SVM ISMs (#4509) ### Description - Updates the enrolled sets on the default ISMs of eclipsemainnet and solanamainnet ### Drive-by changes - stopped reading `type` completely for the multisig ISM configs -- this isn't needed whatsoever and caused issues bc the sealevel tooling would expect a number but infra would generate a string w/ the ISM type name - to support string chain_ids (the case on Cosmos), added some logic - removed `testnet3`, not needed anymore ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
2 months ago
"everclear": {
"blockExplorers": [
{
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"apiUrl": "https://scan.everclear.org/api",
chore: update SVM ISMs (#4509) ### Description - Updates the enrolled sets on the default ISMs of eclipsemainnet and solanamainnet ### Drive-by changes - stopped reading `type` completely for the multisig ISM configs -- this isn't needed whatsoever and caused issues bc the sealevel tooling would expect a number but infra would generate a string w/ the ISM type name - to support string chain_ids (the case on Cosmos), added some logic - removed `testnet3`, not needed anymore ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
2 months ago
"family": "blockscout",
"name": "Everclear Explorer",
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"url": "https://scan.everclear.org"
chore: update SVM ISMs (#4509) ### Description - Updates the enrolled sets on the default ISMs of eclipsemainnet and solanamainnet ### Drive-by changes - stopped reading `type` completely for the multisig ISM configs -- this isn't needed whatsoever and caused issues bc the sealevel tooling would expect a number but infra would generate a string w/ the ISM type name - to support string chain_ids (the case on Cosmos), added some logic - removed `testnet3`, not needed anymore ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
2 months ago
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 2
chore: update SVM ISMs (#4509) ### Description - Updates the enrolled sets on the default ISMs of eclipsemainnet and solanamainnet ### Drive-by changes - stopped reading `type` completely for the multisig ISM configs -- this isn't needed whatsoever and caused issues bc the sealevel tooling would expect a number but infra would generate a string w/ the ISM type name - to support string chain_ids (the case on Cosmos), added some logic - removed `testnet3`, not needed anymore ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
2 months ago
},
"chainId": 25327,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Everclear",
"domainId": 25327,
"gasCurrencyCoinGeckoId": "ethereum",
"index": {
"from": 37
},
"name": "everclear",
"nativeToken": {
"decimals": 18,
"name": "Ethereum",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.everclear.raas.gelato.cloud"
}
],
"technicalStack": "arbitrumnitro"
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"fantom": {
"blockExplorers": [
{
"apiUrl": "https://api.ftmscan.com/api",
"family": "etherscan",
"name": "FTMScan",
"url": "https://ftmscan.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
"reorgPeriod": 5
},
"chainId": 250,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Fantom Opera",
"domainId": 250,
"gasCurrencyCoinGeckoId": "fantom",
"name": "fantom",
"nativeToken": {
"decimals": 18,
"name": "Fantom",
"symbol": "FTM"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpcapi.fantom.network"
},
{
"http": "https://fantom-rpc.publicnode.com"
},
{
"http": "https://fantom-pokt.nodies.app"
},
{
"http": "https://rpc.fantom.network"
},
{
"http": "https://rpc2.fantom.network"
},
{
"http": "https://rpc3.fantom.network"
}
],
"technicalStack": "other"
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"flare": {
"blockExplorers": [
{
"apiUrl": "https://flare-explorer.flare.network/api",
"family": "blockscout",
"name": "Flare Explorer",
"url": "https://flare-explorer.flare.network"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 3
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 14,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Flare",
"domainId": 14,
"gasCurrencyCoinGeckoId": "flare-networks",
"name": "flare",
"nativeToken": {
"decimals": 18,
"name": "Flare",
"symbol": "FLR"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://flare-api.flare.network/ext/C/rpc"
},
{
"http": "https://flare.solidifi.app/ext/C/rpc"
},
{
"http": "https://flare.rpc.thirdweb.com"
},
{
"http": "https://rpc.ankr.com/flare"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
},
"flow": {
"blockExplorers": [
{
"apiUrl": "https://evm.flowscan.io/api",
"family": "blockscout",
"name": "EVM on Flow Explorer",
"url": "https://evm.flowscan.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 1,
"reorgPeriod": 25
},
"chainId": 747,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "EVM on Flow",
"domainId": 747,
"gasCurrencyCoinGeckoId": "flow",
"isTestnet": false,
"name": "flow",
"nativeToken": {
"decimals": 18,
"name": "Flow",
"symbol": "FLOW"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://mainnet.evm.nodes.onflow.org"
}
],
"technicalStack": "other",
"transactionOverrides": {
"gasPrice": 100000000
}
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"fraxtal": {
"blockExplorers": [
{
"apiUrl": "https://api.fraxscan.com/api",
"family": "etherscan",
"name": "Fraxscan",
"url": "https://fraxscan.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 252,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Fraxtal",
"domainId": 252,
"gasCurrencyCoinGeckoId": "frax-ether",
"gnosisSafeTransactionServiceUrl": "https://transaction-frax.safe.optimism.io",
"name": "fraxtal",
"nativeToken": {
"decimals": 18,
"name": "Frax Ether",
"symbol": "frxETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.frax.com"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
{
"http": "https://fraxtal.drpc.org"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "opstack"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"fusemainnet": {
"blockExplorers": [
{
"apiUrl": "https://explorer.fuse.io/api",
"family": "etherscan",
"name": "FuseExplorer",
"url": "https://explorer.fuse.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 5,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 19
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 122,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Fuse",
"domainId": 122,
"gasCurrencyCoinGeckoId": "fuse-network-token",
"gnosisSafeTransactionServiceUrl": "https://transaction-fuse.safe.fuse.io",
"name": "fusemainnet",
"nativeToken": {
"decimals": 18,
"name": "FUSE",
"symbol": "FUSE"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.fuse.io"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
{
"http": "https://fuse.drpc.org"
},
{
"http": "https://fuse.liquify.com"
},
{
"http": "https://fuse-pokt.nodies.app"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"gnosis": {
"blockExplorers": [
{
"apiUrl": "https://api.gnosisscan.io/api",
"family": "etherscan",
"name": "GnosisScan",
"url": "https://gnosisscan.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 5,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 100,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Gnosis",
"domainId": 100,
"gasCurrencyCoinGeckoId": "xdai",
"gnosisSafeTransactionServiceUrl": "https://safe-transaction-gnosis-chain.safe.global/",
"name": "gnosis",
"nativeToken": {
"decimals": 18,
"name": "xDai",
"symbol": "xDai"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.gnosischain.com",
"pagination": {
"maxBlockRange": 10000,
"minBlockNumber": 25997478
}
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"gravity": {
"blockExplorers": [
{
"apiUrl": "https://explorer.gravity.xyz/api",
"family": "blockscout",
"name": "Gravity Alpha Explorer",
"url": "https://explorer.gravity.xyz"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 1,
"reorgPeriod": 5
},
"chainId": 1625,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Gravity Alpha Mainnet",
"displayNameShort": "Gravity",
"domainId": 1625,
"gasCurrencyCoinGeckoId": "g-token",
"index": {
"from": 13374779
},
"name": "gravity",
"nativeToken": {
"decimals": 18,
"name": "Gravity",
"symbol": "G"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.gravity.xyz"
}
],
"technicalStack": "arbitrumnitro"
},
"harmony": {
"blockExplorers": [
{
"apiUrl": "https://explorer.harmony.one/api",
"family": "blockscout",
"name": "Harmony Explorer",
"url": "https://explorer.harmony.one"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
"reorgPeriod": 5
},
"chainId": 1666600000,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Harmony One",
"domainId": 1666600000,
"gasCurrencyCoinGeckoId": "harmony",
"name": "harmony",
"nativeToken": {
"decimals": 18,
"name": "ONE",
"symbol": "ONE"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://api.harmony.one"
},
{
"http": "https://api.s0.t.hmny.io"
},
{
"http": "https://1rpc.io/one"
},
{
"http": "https://rpc.ankr.com/harmony"
}
],
"technicalStack": "other"
},
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"immutablezkevm": {
"blockExplorers": [
{
"apiUrl": "https://explorer.immutable.com/api/eth-rpc",
"family": "blockscout",
"name": "Immutable Explorer",
"url": "https://explorer.immutable.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
"reorgPeriod": 20
},
"chainId": 13371,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Immutable zkEVM",
"domainId": 13371,
"gasCurrencyCoinGeckoId": "immutable-x",
"name": "immutablezkevm",
"nativeToken": {
"decimals": 18,
"name": "Immutable",
"symbol": "IMX"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.immutable.com"
},
{
"http": "https://immutable.gateway.tenderly.co"
}
],
"technicalStack": "other",
"transactionOverrides": {
"maxFeePerGas": 100000000000,
"maxPriorityFeePerGas": 100000000000
}
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"inevm": {
"blockExplorers": [
{
"apiUrl": "https://inevm.calderaexplorer.xyz/api",
"family": "blockscout",
"name": "Caldera inEVM Explorer",
"url": "https://inevm.calderaexplorer.xyz"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 3
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 2525,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Injective EVM",
"displayNameShort": "inEVM",
"domainId": 2525,
"gasCurrencyCoinGeckoId": "injective-protocol",
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"index": {
"from": 37
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"name": "inevm",
"nativeToken": {
"decimals": 18,
"name": "Injective",
"symbol": "INJ"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://inevm.calderachain.xyz/http"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
{
"http": "https://mainnet.rpc.inevm.com/http"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
],
"technicalStack": "arbitrumnitro"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"injective": {
"bech32Prefix": "inj",
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"blockExplorers": [
{
"apiUrl": "https://www.mintscan.io/injective",
"family": "other",
"name": "Mintscan",
"url": "https://www.mintscan.io/injective"
}
],
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"blocks": {
"confirmations": 1,
"estimateBlockTime": 1,
"reorgPeriod": 10
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"canonicalAsset": "inj",
chore: update SVM ISMs (#4509) ### Description - Updates the enrolled sets on the default ISMs of eclipsemainnet and solanamainnet ### Drive-by changes - stopped reading `type` completely for the multisig ISM configs -- this isn't needed whatsoever and caused issues bc the sealevel tooling would expect a number but infra would generate a string w/ the ISM type name - to support string chain_ids (the case on Cosmos), added some logic - removed `testnet3`, not needed anymore ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
2 months ago
"chainId": "injective-1",
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"contractAddressBytes": 20,
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Injective",
"domainId": 6909546,
"gasCurrencyCoinGeckoId": "injective-protocol",
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"gasPrice": {
"amount": "700000000",
"denom": "inj"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"grpcUrls": [
{
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"http": "https://injective-grpc.goldenratiostaking.net:443"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
],
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"index": {
"chunk": 25,
"from": 58419500
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"name": "injective",
"nativeToken": {
"decimals": 18,
"denom": "inj",
"name": "Injective",
"symbol": "INJ"
},
"protocol": "cosmos",
"restUrls": [
{
"http": "https://sentry.lcd.injective.network:443"
}
],
"rpcUrls": [
{
"http": "https://sentry.tm.injective.network:443"
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"slip44": 118,
"technicalStack": "other"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"kaia": {
"blockExplorers": [
{
"apiUrl": "https://api-cypress.klaytnscope.com/api",
"family": "etherscan",
"name": "Kaiascope",
"url": "https://kaiascope.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 1,
"reorgPeriod": 5
},
"chainId": 8217,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Kaia",
"domainId": 8217,
"gasCurrencyCoinGeckoId": "kaia",
"name": "kaia",
"nativeToken": {
"decimals": 18,
"name": "Kaia",
"symbol": "KLAY"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://public-en.node.kaia.io"
}
],
"technicalStack": "other"
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"kroma": {
"blockExplorers": [
{
"apiUrl": "https://blockscout.kroma.network/api",
"family": "blockscout",
"name": "Kroma Explorer",
"url": "https://blockscout.kroma.network"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 255,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Kroma",
"domainId": 255,
"gasCurrencyCoinGeckoId": "ethereum",
"name": "kroma",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc-kroma.rockx.com"
},
{
"http": "https://api.kroma.network"
},
{
"http": "https://1rpc.io/kroma"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "opstack"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"linea": {
"blockExplorers": [
{
"apiUrl": "https://api.lineascan.build/api",
"family": "etherscan",
"name": "LineaScan",
"url": "https://lineascan.build"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 59144,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Linea",
"domainId": 59144,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://transaction.safe.linea.build",
"name": "linea",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.linea.build"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
{
"http": "https://linea.blockpi.network/v1/rpc/public"
},
{
"http": "https://1rpc.io/linea"
},
{
"http": "https://linea.drpc.org"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"lisk": {
"blockExplorers": [
{
"apiUrl": "https://blockscout.lisk.com/api/eth-rpc",
"family": "blockscout",
"name": "Lisk Explorer",
"url": "https://blockscout.lisk.com"
}
],
"blocks": {
"confirmations": 3,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 1135,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Lisk",
"domainId": 1135,
"gasCurrencyCoinGeckoId": "ethereum",
"name": "lisk",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.api.lisk.com"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "opstack"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"lukso": {
"blockExplorers": [
{
"apiUrl": "https://explorer.execution.mainnet.lukso.network/api",
"family": "blockscout",
"name": "LUKSO Mainnet Explorer",
"url": "https://explorer.execution.mainnet.lukso.network"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 12,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 15
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 42,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "LUKSO",
"domainId": 42,
"gasCurrencyCoinGeckoId": "lukso-token-2",
"name": "lukso",
"nativeToken": {
"decimals": 18,
"name": "LUKSO",
"symbol": "LYX"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.mainnet.lukso.network"
},
{
"http": "https://rpc.lukso.sigmacore.io"
},
{
"http": "https://42.rpc.thirdweb.com"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
},
"lumia": {
"blockExplorers": [
{
"apiUrl": "https://explorer.lumia.org/api/eth-rpc",
"family": "blockscout",
"name": "Lumia Prism Explorer",
"url": "https://explorer.lumia.org"
}
],
"blocks": {
"confirmations": 3,
"estimateBlockTime": 4,
"reorgPeriod": 5
},
"chainId": 994873017,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Lumia Prism",
"domainId": 994873017,
"gasCurrencyCoinGeckoId": "orion-protocol",
"name": "lumia",
"nativeToken": {
"decimals": 18,
"name": "Lumia",
"symbol": "LUMIA"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://994873017.rpc.thirdweb.com"
},
{
"http": "https://mainnet-rpc.lumia.org"
}
],
"technicalStack": "polygoncdk"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"mantapacific": {
"blockExplorers": [
{
"apiUrl": "https://pacific-explorer.manta.network/api",
"family": "blockscout",
"name": "Manta Pacific Explorer",
"url": "https://pacific-explorer.manta.network"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"chainId": 169,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Manta Pacific",
"displayNameShort": "Manta",
"domainId": 169,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://transaction.safe.manta.network",
"isTestnet": false,
"name": "mantapacific",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://pacific-rpc.manta.network/http"
},
{
"http": "https://manta.nirvanalabs.xyz/mantapublic"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "opstack"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"mantle": {
"blockExplorers": [
{
"apiUrl": "https://explorer.mantle.xyz/api",
"family": "blockscout",
"name": "Mantle Mainnet Explorer",
"url": "https://explorer.mantle.xyz"
}
],
"blocks": {
"confirmations": 3,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 2
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 5000,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Mantle",
"domainId": 5000,
"gasCurrencyCoinGeckoId": "mantle",
"gnosisSafeTransactionServiceUrl": "https://transaction.multisig.mantle.xyz",
"name": "mantle",
"nativeToken": {
"decimals": 18,
"name": "Mantle",
"symbol": "MNT"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.mantle.xyz"
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "opstack"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"merlin": {
"blockExplorers": [
{
"apiUrl": "https://scan.merlinchain.io/api",
"family": "other",
"name": "Merlin Explorer",
"url": "https://scan.merlinchain.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 4200,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Merlin",
"domainId": 4200,
"gasCurrencyCoinGeckoId": "merlin-chain-bridged-wrapped-btc-merlin",
"name": "merlin",
"nativeToken": {
"decimals": 18,
"name": "Bitcoin",
"symbol": "BTC"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.merlinchain.io"
},
{
"http": "https://merlin.blockpi.network/v1/rpc/public"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "polygoncdk"
},
"metall2": {
"blockExplorers": [
{
"apiUrl": "https://explorer.metall2.com/api",
"family": "blockscout",
"name": "Metal L2 Explorer",
"url": "https://explorer.metall2.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
"reorgPeriod": 5
},
"chainId": 1750,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Metal L2",
"domainId": 1750,
"gasCurrencyCoinGeckoId": "ethereum",
"isTestnet": false,
"name": "metall2",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.metall2.com"
}
],
"technicalStack": "opstack"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"metis": {
"blockExplorers": [
{
"apiUrl": "https://andromeda-explorer.metis.io/api/eth-rpc",
"family": "blockscout",
"name": "Metis Andromeda Explorer",
"url": "https://andromeda-explorer.metis.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 5,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 1088,
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"displayName": "Metis Andromeda",
"domainId": 1088,
"gasCurrencyCoinGeckoId": "metis-token",
"index": {
"from": 17966274
},
"name": "metis",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"nativeToken": {
"decimals": 18,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"name": "Metis",
"symbol": "METIS"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"protocol": "ethereum",
"rpcUrls": [
{
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"http": "https://andromeda.metis.io/?owner=1088"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "opstack"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"mint": {
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"blockExplorers": [
{
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"apiUrl": "https://explorer.mintchain.io/api/eth-rpc",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"family": "blockscout",
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"name": "Mint Explorer",
"url": "https://explorer.mintchain.io"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
],
"blocks": {
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"confirmations": 1,
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"chainId": 185,
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"displayName": "Mint",
"domainId": 185,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://transaction-mint.safe.optimism.io",
"name": "mint",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"nativeToken": {
"decimals": 18,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"name": "Ether",
"symbol": "ETH"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"protocol": "ethereum",
"rpcUrls": [
{
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"http": "https://rpc.mintchain.io"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "opstack"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"mode": {
"blockExplorers": [
{
"apiUrl": "https://explorer.mode.network/api",
"family": "blockscout",
"name": "Mode Explorer",
"url": "https://explorer.mode.network"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 34443,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Mode",
"domainId": 34443,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://transaction-mode.safe.optimism.io",
"name": "mode",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://mainnet.mode.network"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
{
"http": "https://mode.drpc.org"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "opstack"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"molten": {
"blockExplorers": [
{
"apiUrl": "https://molten.calderaexplorer.xyz/api",
"family": "blockscout",
"name": "Caldera Molten Explorer",
"url": "https://molten.calderaexplorer.xyz"
}
],
"blocks": {
"confirmations": 1,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"estimateBlockTime": 30,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"reorgPeriod": 0
},
"chainId": 360,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Molten",
"domainId": 360,
"gasCurrencyCoinGeckoId": "molten-2",
"index": {
"from": 4707345
},
"name": "molten",
"nativeToken": {
"decimals": 18,
"name": "Molten",
"symbol": "MOLTEN"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://molten.calderachain.xyz/http"
}
],
"technicalStack": "arbitrumnitro"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"moonbeam": {
"blockExplorers": [
{
"apiUrl": "https://api-moonbeam.moonscan.io/api",
"family": "etherscan",
"name": "MoonScan",
"url": "https://moonscan.io"
}
],
"blocks": {
"confirmations": 2,
"estimateBlockTime": 12,
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"reorgPeriod": "finalized"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 1284,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Moonbeam",
"domainId": 1284,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"gasCurrencyCoinGeckoId": "moonbeam",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"gnosisSafeTransactionServiceUrl": "https://transaction.multisig.moonbeam.network",
"name": "moonbeam",
"nativeToken": {
"decimals": 18,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"name": "Moonbeam",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"symbol": "GLMR"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.api.moonbeam.network"
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "polkadotsubstrate",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"transactionOverrides": {
"maxFeePerGas": 350000000000,
"maxPriorityFeePerGas": 50000000000
}
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"morph": {
"blockExplorers": [
{
"apiUrl": "https://explorer-api.morphl2.io/api",
"family": "blockscout",
"name": "Morph Explorer",
"url": "https://explorer.morphl2.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 4,
"reorgPeriod": 5
},
"chainId": 2818,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Morph",
"domainId": 2818,
"gasCurrencyCoinGeckoId": "ethereum",
"name": "morph",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.morphl2.io"
}
],
"technicalStack": "other"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"neutron": {
"bech32Prefix": "neutron",
"blockExplorers": [
{
"apiUrl": "https://www.mintscan.io/neutron",
"family": "other",
"name": "Mintscan",
"url": "https://www.mintscan.io/neutron"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
"reorgPeriod": 1
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"canonicalAsset": "untrn",
chore: update SVM ISMs (#4509) ### Description - Updates the enrolled sets on the default ISMs of eclipsemainnet and solanamainnet ### Drive-by changes - stopped reading `type` completely for the multisig ISM configs -- this isn't needed whatsoever and caused issues bc the sealevel tooling would expect a number but infra would generate a string w/ the ISM type name - to support string chain_ids (the case on Cosmos), added some logic - removed `testnet3`, not needed anymore ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
2 months ago
"chainId": "neutron-1",
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"contractAddressBytes": 32,
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Neutron",
"domainId": 1853125230,
"gasCurrencyCoinGeckoId": "neutron-3",
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"gasPrice": {
"amount": "0.0053",
"denom": "untrn"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"grpcUrls": [
{
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"http": "http://grpc-kralum.neutron-1.neutron.org:80"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
],
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"index": {
"chunk": 5,
"from": 4000000
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"name": "neutron",
"nativeToken": {
"decimals": 6,
"denom": "untrn",
"name": "Neutron",
"symbol": "NTRN"
},
"protocol": "cosmos",
"restUrls": [
{
"http": "https://rest-lb.neutron.org"
}
],
"rpcUrls": [
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
{
"http": "https://rpc-arch.mainnet.neutron.tm.p2p.org"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
{
"http": "https://rpc-kralum.neutron-1.neutron.org"
}
],
"slip44": 118,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "other",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"transactionOverrides": {
"gasPrice": "0.0075"
}
},
chore: update SVM ISMs (#4509) ### Description - Updates the enrolled sets on the default ISMs of eclipsemainnet and solanamainnet ### Drive-by changes - stopped reading `type` completely for the multisig ISM configs -- this isn't needed whatsoever and caused issues bc the sealevel tooling would expect a number but infra would generate a string w/ the ISM type name - to support string chain_ids (the case on Cosmos), added some logic - removed `testnet3`, not needed anymore ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
2 months ago
"oortmainnet": {
"blockExplorers": [
{
"apiUrl": "https://mainnet-scan.oortech.com/api",
"family": "other",
"name": "Oort Olympus Explorer",
"url": "https://mainnet-scan.oortech.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
"reorgPeriod": 0
},
"chainId": 970,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Oort",
"domainId": 970,
"gasCurrencyCoinGeckoId": "oort",
"name": "oortmainnet",
"nativeToken": {
"decimals": 18,
"name": "Oort",
"symbol": "OORT"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://mainnet-rpc.oortech.com"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
chore: update SVM ISMs (#4509) ### Description - Updates the enrolled sets on the default ISMs of eclipsemainnet and solanamainnet ### Drive-by changes - stopped reading `type` completely for the multisig ISM configs -- this isn't needed whatsoever and caused issues bc the sealevel tooling would expect a number but infra would generate a string w/ the ISM type name - to support string chain_ids (the case on Cosmos), added some logic - removed `testnet3`, not needed anymore ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
2 months ago
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"optimism": {
"blockExplorers": [
{
"apiUrl": "https://api-optimistic.etherscan.io/api",
"family": "etherscan",
"name": "Etherscan",
"url": "https://optimistic.etherscan.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 10
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 10,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Optimism",
"domainId": 10,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://safe-transaction-optimism.safe.global/",
"name": "optimism",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://mainnet.optimism.io"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "opstack"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"orderly": {
"blockExplorers": [
{
"apiUrl": "https://explorer.orderly.network/api",
"family": "blockscout",
"name": "Orderly L2 Explorer",
"url": "https://explorer.orderly.network"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
"reorgPeriod": 5
},
"chainId": 291,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Orderly L2",
"domainId": 291,
"gasCurrencyCoinGeckoId": "ethereum",
"name": "orderly",
"nativeToken": {
"decimals": 18,
"name": "Ethereum",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.orderly.network"
},
{
"http": "https://l2-orderly-mainnet-0.t.conduit.xyz"
}
],
"technicalStack": "opstack"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"osmosis": {
"bech32Prefix": "osmo",
"blockExplorers": [
{
"apiUrl": "https://www.mintscan.io/osmosis",
"family": "other",
"name": "Mintscan",
"url": "https://www.mintscan.io/osmosis"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
"reorgPeriod": 1
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"canonicalAsset": "uosmo",
chore: update SVM ISMs (#4509) ### Description - Updates the enrolled sets on the default ISMs of eclipsemainnet and solanamainnet ### Drive-by changes - stopped reading `type` completely for the multisig ISM configs -- this isn't needed whatsoever and caused issues bc the sealevel tooling would expect a number but infra would generate a string w/ the ISM type name - to support string chain_ids (the case on Cosmos), added some logic - removed `testnet3`, not needed anymore ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
2 months ago
"chainId": "osmosis-1",
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"contractAddressBytes": 32,
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"deployer": {
"name": "Mitosis",
"url": "https://mitosis.org"
},
"displayName": "Osmosis",
"domainId": 875,
"gasCurrencyCoinGeckoId": "osmosis",
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"gasPrice": {
"amount": "0.025",
"denom": "uosmo"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"grpcUrls": [
{
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"http": "https://osmosis-grpc.publicnode.com:443"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
],
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"index": {
"chunk": 10,
"from": 14389169
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"isTestnet": false,
"name": "osmosis",
"nativeToken": {
"decimals": 6,
"denom": "uosmo",
"name": "Osmosis",
"symbol": "OSMO"
},
"protocol": "cosmos",
"restUrls": [
{
"http": "https://osmosis-rest.publicnode.com"
}
],
"rpcUrls": [
{
"http": "https://osmosis-rpc.publicnode.com"
}
],
"slip44": 118,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "other",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"transactionOverrides": {
"gasPrice": "0.025"
}
},
"polygon": {
"blockExplorers": [
{
"apiUrl": "https://api.polygonscan.com/api",
"family": "etherscan",
"name": "PolygonScan",
"url": "https://polygonscan.com"
}
],
"blocks": {
"confirmations": 3,
"estimateBlockTime": 2,
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"reorgPeriod": "finalized"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 137,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Polygon",
"domainId": 137,
chore: update SVM ISMs (#4509) ### Description - Updates the enrolled sets on the default ISMs of eclipsemainnet and solanamainnet ### Drive-by changes - stopped reading `type` completely for the multisig ISM configs -- this isn't needed whatsoever and caused issues bc the sealevel tooling would expect a number but infra would generate a string w/ the ISM type name - to support string chain_ids (the case on Cosmos), added some logic - removed `testnet3`, not needed anymore ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
2 months ago
"gasCurrencyCoinGeckoId": "polygon-ecosystem-token",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"gnosisSafeTransactionServiceUrl": "https://safe-transaction-polygon.safe.global/",
"name": "polygon",
"nativeToken": {
"decimals": 18,
chore: update SVM ISMs (#4509) ### Description - Updates the enrolled sets on the default ISMs of eclipsemainnet and solanamainnet ### Drive-by changes - stopped reading `type` completely for the multisig ISM configs -- this isn't needed whatsoever and caused issues bc the sealevel tooling would expect a number but infra would generate a string w/ the ISM type name - to support string chain_ids (the case on Cosmos), added some logic - removed `testnet3`, not needed anymore ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
2 months ago
"name": "Polygon Ecosystem Token",
"symbol": "POL"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://polygon-bor.publicnode.com"
},
{
"http": "https://polygon-rpc.com"
},
{
"http": "https://rpc.ankr.com/polygon"
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "other",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"transactionOverrides": {
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"maxFeePerGas": 800000000000,
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"maxPriorityFeePerGas": 50000000000
}
},
"polygonzkevm": {
"blockExplorers": [
{
"apiUrl": "https://api-zkevm.polygonscan.com/api",
"family": "etherscan",
"name": "PolygonScan",
"url": "https://zkevm.polygonscan.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 10,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 1101,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Polygon zkEVM",
"displayNameShort": "zkEVM",
"domainId": 1101,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://safe-transaction-zkevm.safe.global/",
"name": "polygonzkevm",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://zkevm-rpc.com"
},
{
"http": "https://rpc.ankr.com/polygon_zkevm"
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "polygoncdk",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"transactionOverrides": {
"gasPrice": 1000000000
}
},
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"polynomial": {
"blockExplorers": [
{
"apiUrl": "https://polynomialscan.io/api",
"family": "routescan",
"name": "Polynomial Explorer",
"url": "https://polynomialscan.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
"reorgPeriod": 5
},
"chainId": 8008,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Polynomial",
"domainId": 8008,
"gasCurrencyCoinGeckoId": "ethereum",
"name": "polynomial",
"nativeToken": {
"decimals": 18,
"name": "Ethereum",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.polynomial.fi"
}
],
"technicalStack": "opstack"
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"proofofplay": {
"blockExplorers": [
{
"apiUrl": "https://explorer.apex.proofofplay.com/api/eth-rpc",
"family": "blockscout",
"name": "Proof of Play Apex Explorer",
"url": "https://explorer.apex.proofofplay.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 1,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 70700,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Proof of Play Apex",
"domainId": 70700,
"gasCurrencyCoinGeckoId": "ethereum",
"index": {
"from": 32018468
},
"name": "proofofplay",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.apex.proofofplay.com"
}
],
"technicalStack": "arbitrumnitro"
},
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"rari": {
"blockExplorers": [
{
"apiUrl": "https://mainnet.explorer.rarichain.org/api",
"family": "blockscout",
"name": "Rari Mainnet Explorer",
"url": "https://mainnet.explorer.rarichain.org"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 30,
"reorgPeriod": 0
},
"chainId": 1380012617,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "RARI Chain",
"domainId": 1380012617,
"gasCurrencyCoinGeckoId": "ethereum",
"index": {
"from": 541753
},
"name": "rari",
"nativeToken": {
"decimals": 18,
"name": "Ethereum",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://mainnet.rpc.rarichain.org/http"
}
],
"technicalStack": "arbitrumnitro"
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"real": {
"blockExplorers": [
{
"apiUrl": "https://explorer.re.al/api/eth-rpc",
"family": "blockscout",
"name": "re.al Explorer",
"url": "https://explorer.re.al"
}
],
"blocks": {
"confirmations": 1,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"estimateBlockTime": 30,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"reorgPeriod": 0
},
"chainId": 111188,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "re.al",
"domainId": 111188,
"gasCurrencyCoinGeckoId": "real-ether",
"index": {
"from": 363159
},
"name": "real",
"nativeToken": {
"decimals": 18,
"name": "Real Ether",
"symbol": "reETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://real.drpc.org"
}
],
"technicalStack": "arbitrumnitro"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"redstone": {
"blockExplorers": [
{
"apiUrl": "https://explorer.redstone.xyz/api",
"family": "blockscout",
"name": "Redstone Explorer",
"url": "https://explorer.redstone.xyz"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 690,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Redstone",
"domainId": 690,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://transaction-redstone.safe.optimism.io",
"name": "redstone",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.redstonechain.com"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "opstack"
},
"rootstock": {
"blockExplorers": [
{
"apiUrl": "https://rootstock.blockscout.com/api",
"family": "blockscout",
"name": "Blockscout",
"url": "https://rootstock.blockscout.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 30,
"reorgPeriod": 4
},
"chainId": 30,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Rootstock",
"domainId": 30,
"gasCurrencyCoinGeckoId": "rootstock",
"name": "rootstock",
"nativeToken": {
"decimals": 18,
"name": "Rootstock Smart Bitcoin",
"symbol": "RBTC"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.mainnet.rootstock.io/kXhXHf6TnnfW1POvr4UT0YUvujmuju-M"
},
{
"http": "https://public-node.rsk.co"
},
{
"http": "https://mycrypto.rsk.co"
}
],
"technicalStack": "other",
"transactionOverrides": {
"gasPrice": 70000000
}
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"sanko": {
"blockExplorers": [
{
"apiUrl": "https://explorer.sanko.xyz/api/eth-rpc",
"family": "blockscout",
"name": "Sanko Explorer",
"url": "https://explorer.sanko.xyz"
}
],
"blocks": {
"confirmations": 1,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"estimateBlockTime": 15,
"reorgPeriod": 1
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 1996,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Sanko",
"domainId": 1996,
"gasCurrencyCoinGeckoId": "dream-machine-token",
"index": {
"from": 937117
},
"name": "sanko",
"nativeToken": {
"decimals": 18,
"name": "Dream Machine Token",
"symbol": "DMT"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://mainnet.sanko.xyz"
}
],
"technicalStack": "arbitrumnitro"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"scroll": {
"blockExplorers": [
{
"apiUrl": "https://api.scrollscan.com/api",
"family": "etherscan",
"name": "Scroll Explorer",
"url": "https://scrollscan.com/"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 3,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 17
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 534352,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Scroll",
"domainId": 534352,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://safe-transaction-scroll.safe.global",
"name": "scroll",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://scroll.blockpi.network/v1/rpc/public"
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "other",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"transactionOverrides": {
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"gasPrice": 200000000
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
},
"sei": {
"blockExplorers": [
{
"apiUrl": "https://seitrace.com/pacific-1/api",
"family": "etherscan",
"name": "Seitrace",
"url": "https://seitrace.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 1,
"reorgPeriod": 1
},
"chainId": 1329,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Sei",
"domainId": 1329,
"gasCurrencyCoinGeckoId": "sei-network",
"gnosisSafeTransactionServiceUrl": "https://transaction.sei-safe.protofire.io",
"name": "sei",
"nativeToken": {
"decimals": 18,
"name": "Sei",
"symbol": "SEI"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://evm-rpc.sei-apis.com"
}
],
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"technicalStack": "other",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"transactionOverrides": {
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"gasPrice": 101000000000
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"shibarium": {
"blockExplorers": [
{
"apiUrl": "https://shibariumscan.io/api",
"family": "blockscout",
"name": "Shibarium Explorer",
"url": "https://shibariumscan.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 5,
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"reorgPeriod": "finalized"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 109,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Shibarium",
"domainId": 109,
"gasCurrencyCoinGeckoId": "bone-shibaswap",
"name": "shibarium",
"nativeToken": {
"decimals": 18,
"name": "Bone ShibaSwap",
"symbol": "BONE"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://www.shibrpc.com"
},
{
"http": "https://rpc.shibrpc.com"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"snaxchain": {
"blockExplorers": [
{
"apiUrl": "https://explorer.snaxchain.io/api",
"family": "blockscout",
"name": "Snaxchain Mainnet Explorer",
"url": "https://explorer.snaxchain.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
"reorgPeriod": 5
},
"chainId": 2192,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "SnaxChain",
"domainId": 2192,
"gasCurrencyCoinGeckoId": "ethereum",
"name": "snaxchain",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://mainnet.snaxchain.io"
}
],
"technicalStack": "opstack"
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"solanamainnet": {
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"blockExplorers": [
{
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"apiUrl": "https://solscan.io",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"family": "other",
"name": "Solana Explorer",
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"url": "https://solscan.io"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 0.4,
"reorgPeriod": 0
},
"chainId": 1399811149,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Solana",
"domainId": 1399811149,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"gasCurrencyCoinGeckoId": "solana",
"name": "solanamainnet",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"nativeToken": {
"decimals": 9,
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"name": "Solana",
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"symbol": "SOL"
},
"protocol": "sealevel",
"rpcUrls": [
{
"http": "https://api.mainnet-beta.solana.com"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
},
"stride": {
"bech32Prefix": "stride",
"blockExplorers": [
{
"apiUrl": "https://www.mintscan.io/stride",
"family": "other",
"name": "Mintscan",
"url": "https://www.mintscan.io/stride"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 5,
"reorgPeriod": 1
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"canonicalAsset": "ustrd",
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"chainId": "stride-1",
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"contractAddressBytes": 32,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"deployer": {
"name": "Stride Labs",
"url": "https://www.stride.zone"
},
"displayName": "Stride",
"domainId": 745,
"gasCurrencyCoinGeckoId": "stride",
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"gasPrice": {
"amount": "0.025",
"denom": "ustrd"
},
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"grpcUrls": [
{
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"http": "https://stride-grpc.publicnode.com:443"
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
}
],
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"index": {
"chunk": 5,
"from": 9152000
},
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"name": "stride",
"nativeToken": {
"decimals": 6,
"denom": "ustrd",
"name": "Stride",
"symbol": "STRD"
},
"protocol": "cosmos",
"restUrls": [
{
"http": "https://stride-api.polkachu.com"
}
],
"rpcUrls": [
{
"http": "https://stride-rpc.polkachu.com"
}
],
"slip44": 118,
"transactionOverrides": {
"gasPrice": "0.0025"
}
},
"superposition": {
"blockExplorers": [
{
"apiUrl": "https://explorer.superposition.so/api",
"family": "blockscout",
"name": "Superposition Explorer",
"url": "https://explorer.superposition.so/"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 60,
"reorgPeriod": 0
},
"chainId": 55244,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Superposition",
"domainId": 55244,
"gasCurrencyCoinGeckoId": "ethereum",
"index": {
"from": 1201
},
"name": "superposition",
"nativeToken": {
"decimals": 18,
"name": "Ethereum",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.superposition.so"
}
],
"technicalStack": "arbitrumnitro"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"taiko": {
"blockExplorers": [
{
"apiUrl": "https://api.taikoscan.io/api",
"family": "etherscan",
"name": "Taikoscan",
"url": "https://taikoscan.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 12,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 167000,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Taiko",
"domainId": 167000,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://transaction.safe.taiko.xyz",
"name": "taiko",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.mainnet.taiko.xyz"
}
],
"technicalStack": "other"
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"tangle": {
"blockExplorers": [
{
"apiUrl": "https://explorer.tangle.tools/api",
"family": "blockscout",
"name": "Tangle EVM Explorer",
"url": "https://explorer.tangle.tools"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 6,
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"reorgPeriod": "finalized"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 5845,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Tangle",
"domainId": 5845,
"gasCurrencyCoinGeckoId": "tangle-network",
"isTestnet": false,
"name": "tangle",
"nativeToken": {
"decimals": 18,
"name": "Tangle Network Token",
"symbol": "TNT"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.tangle.tools"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "polkadotsubstrate"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"viction": {
"blockExplorers": [
{
"apiUrl": "https://www.vicscan.xyz/api",
"family": "other",
"name": "Vicscan",
"url": "https://www.vicscan.xyz"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 3
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 88,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Viction",
"domainId": 88,
"gasCurrencyCoinGeckoId": "tomochain",
"name": "viction",
"nativeToken": {
"decimals": 18,
"name": "Viction",
"symbol": "VIC"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.tomochain.com"
},
{
"http": "https://viction.blockpi.network/v1/rpc/public"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"worldchain": {
"blockExplorers": [
{
"apiUrl": "https://worldchain-mainnet-explorer.alchemy.com/api",
"family": "blockscout",
"name": "World Chain explorer",
"url": "https://worldchain-mainnet-explorer.alchemy.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 480,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "World Chain",
"domainId": 480,
"gasCurrencyCoinGeckoId": "ethereum",
"name": "worldchain",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"http": "https://worldchain-mainnet.g.alchemy.com/public"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "opstack"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"xai": {
"blockExplorers": [
{
"apiUrl": "https://explorer.xai-chain.net/api",
"family": "blockscout",
"name": "Xai Explorer",
"url": "https://explorer.xai-chain.net"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 1,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 660279,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Xai",
"domainId": 660279,
"gasCurrencyCoinGeckoId": "xai-blockchain",
"index": {
"from": 24395308
},
"name": "xai",
"nativeToken": {
"decimals": 18,
"name": "XAI Token",
"symbol": "XAI"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://xai-chain.net/rpc"
}
],
"technicalStack": "arbitrumnitro"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"xlayer": {
"blockExplorers": [
{
"apiUrl": "https://www.oklink.com/api",
"family": "other",
"name": "X Layer Explorer",
"url": "https://www.oklink.com/xlayer"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 10,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 196,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "XLayer",
"displayNameShort": "XLayer",
"domainId": 196,
"gasCurrencyCoinGeckoId": "okb",
"gnosisSafeTransactionServiceUrl": "https://app.safe.global/welcome?chain=xlayer",
"name": "xlayer",
"nativeToken": {
"decimals": 18,
"name": "OKB",
"symbol": "OKB"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://xlayerrpc.okx.com"
},
{
"http": "https://rpc.xlayer.tech"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "polygoncdk"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"zeronetwork": {
"blockExplorers": [
{
"apiUrl": "https://zero-network-api.calderaexplorer.xyz/api",
"family": "etherscan",
"name": "Zero Network Explorer",
"url": "https://zerion-explorer.vercel.app"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 1,
"reorgPeriod": 0
},
"chainId": 543210,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Zero Network",
"domainId": 543210,
"gasCurrencyCoinGeckoId": "ethereum",
"name": "zeronetwork",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://zero-network.calderachain.xyz"
}
],
"technicalStack": "zksync"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"zetachain": {
"blockExplorers": [
{
"apiUrl": "https://explorer.zetachain.com",
"family": "other",
"name": "ZetaScan",
"url": "https://explorer.zetachain.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 6,
"reorgPeriod": 0
},
"chainId": 7000,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "ZetaChain",
"domainId": 7000,
"gasCurrencyCoinGeckoId": "zetachain",
"gnosisSafeTransactionServiceUrl": "https://transaction.safe.zetachain.com",
"name": "zetachain",
"nativeToken": {
"decimals": 18,
"name": "ZetaChain",
"symbol": "ZETA"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://zetachain-evm.blockpi.network/v1/rpc/public"
},
{
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
"http": "https://zetachain-mainnet.g.allthatnode.com/archive/evm"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "other"
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"zircuit": {
"blockExplorers": [
{
"apiUrl": "https://explorer.zircuit.com/api/contractVerifyHardhat",
"family": "etherscan",
"name": "Zircuit Eplorer",
"url": "https://explorer.zircuit.com"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
chore: add `mainnet` suffix to solana and eclipse (#4410) ### Description Because we're doing a new core deployment that includes protocol fees ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
3 months ago
},
"chainId": 48900,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Zircuit",
"domainId": 48900,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://transaction.safe.zircuit.com",
"name": "zircuit",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://zircuit1-mainnet.p2pify.com"
},
{
"http": "https://zircuit1-mainnet.liquify.com"
},
{
"http": "https://zircuit-mainnet.drpc.org"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "opstack"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
feat: update eclipse ISM (#4802) ### Description - Uses the fresh validator set from #4785, happy to wait for that to get merged in first - Mostly wanted to update the Staked validator on Stride. The rest were just to keep in sync with the recent changes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
4 weeks ago
"zksync": {
"blockExplorers": [
{
"apiUrl": "https://block-explorer-api.mainnet.zksync.io/api",
"family": "etherscan",
"name": "zkSync Explorer",
"url": "https://explorer.zksync.io"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 1,
"reorgPeriod": 0
},
"chainId": 324,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "zkSync",
"domainId": 324,
"gasCurrencyCoinGeckoId": "ethereum",
"name": "zksync",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://mainnet.era.zksync.io"
}
],
"technicalStack": "zksync"
},
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
"zoramainnet": {
"blockExplorers": [
{
"apiUrl": "https://explorer.zora.energy/api",
"family": "blockscout",
"name": "Zora Explorer",
"url": "https://explorer.zora.energy"
}
],
"blocks": {
"confirmations": 1,
"estimateBlockTime": 2,
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
"reorgPeriod": 5
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
},
"chainId": 7777777,
"deployer": {
"name": "Abacus Works",
"url": "https://www.hyperlane.xyz"
},
"displayName": "Zora",
"domainId": 7777777,
"gasCurrencyCoinGeckoId": "ethereum",
"gnosisSafeTransactionServiceUrl": "https://transaction-zora.safe.optimism.io",
"name": "zoramainnet",
"nativeToken": {
"decimals": 18,
"name": "Ether",
"symbol": "ETH"
},
"protocol": "ethereum",
"rpcUrls": [
{
"http": "https://rpc.zora.energy"
}
chore: update Eclipse validator sets to include Stride, minor cleanup (#4747) ### Description - deletes all the mainnet2 artifacts that we don't need - moves the sealevel helper scripts into more explicit directories, and ensures thresholds are appropriate - updates the eclipse ISM ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
1 month ago
],
"technicalStack": "opstack"
feat: deploy solana, eclipsemainnet (#4238) ### Description <!-- What's included in this PR? --> ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests --> --------- Co-authored-by: pbio <10051819+paulbalaji@users.noreply.github.com>
4 months ago
}
}