Skip to content

Commit b72e599

Browse files
dwightjlkhadni
andauthored
Update LINK token faucet and bridge info (#1765)
* Update LINK token faucet and bridge info * Correct Polygon zkEVM testnet faucet * Base Sepolia LINK * Update decommissioned/deprecated testnets * Edits and add Base Sepolia faucet link * Update VRF supported networks * Update L2 sequencers * Update Automation supported testnets * Remove Base Goerli testnet from Data Feeds lists * Change Base title case * Update Base network status URL * Update zksync status page URL --------- Co-authored-by: Karim <[email protected]>
1 parent a4c7098 commit b72e599

File tree

7 files changed

+51
-128
lines changed

7 files changed

+51
-128
lines changed

src/content/chainlink-automation/overview/supported-networks.mdx

-1
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,6 @@ Chainlink Automation is available on the following networks. All networks operat
3737
- Testnet (Automation v1.2)
3838
- [Arbitrum](#arbitrum)
3939
- Mainnet
40-
- Goerli testnet
4140
- Sepolia testnet
4241
- [Optimism](#optimism)
4342
- Mainnet

src/content/data-feeds/l2-sequencer-feeds.mdx

+5-4
Original file line numberDiff line numberDiff line change
@@ -19,14 +19,15 @@ You can find proxy addresses for the L2 sequencer feeds at the following address
1919

2020
- Arbitrum:
2121
- Arbitrum mainnet: [0xFdB631F5EE196F0ed6FAa767959853A9F217697D](https://arbiscan.io/address/0xFdB631F5EE196F0ed6FAa767959853A9F217697D)
22-
- Arbitrum Goerli testnet: [0x4da69F028a5790fCCAfe81a75C0D24f46ceCDd69](https://goerli-rollup-explorer.arbitrum.io/address/0x4da69F028a5790fCCAfe81a75C0D24f46ceCDd69)
2322
- Optimism:
2423
- Optimism mainnet: [0x371EAD81c9102C9BF4874A9075FFFf170F2Ee389](https://optimistic.etherscan.io/address/0x371EAD81c9102C9BF4874A9075FFFf170F2Ee389)
2524
- Optimism Goerli testnet: [0x4C4814aa04433e0FB31310379a4D6946D5e1D353](https://goerli-optimism.etherscan.io/address/0x4C4814aa04433e0FB31310379a4D6946D5e1D353)
2625
- BASE:
2726
- BASE mainnet: [0xBCF85224fc0756B9Fa45aA7892530B47e10b6433](https://basescan.org/address/0xBCF85224fc0756B9Fa45aA7892530B47e10b6433)
2827
- Metis:
2928
- Andromeda mainnet: [0x58218ea7422255EBE94e56b504035a784b7AA204](https://andromeda-explorer.metis.io/address/0x58218ea7422255EBE94e56b504035a784b7AA204)
29+
- Scroll:
30+
- Scroll mainnet: [0x95BcCbBBaCBB7ed224AC2EE38531f2467DF41Ea4](https://scrollscan.com/address/0x95BcCbBBaCBB7ed224AC2EE38531f2467DF41Ea4)
3031

3132
### Arbitrum
3233

@@ -43,9 +44,9 @@ The diagram below shows how these feeds update and how a consumer retrieves the
4344

4445
If the Arbitrum network becomes unavailable, the `ArbitrumValidator` contract continues to send messages to the L2 network through the delayed inbox on L1. This message stays there until the sequencer is back up again. When the sequencer comes back online after downtime, it processes all transactions from the delayed inbox before it accepts new transactions. The message that signals when the sequencer is down will be processed before any new messages with transactions that require the sequencer to be operational.
4546

46-
## Optimism, BASE, and Metis
47+
## Optimism, BASE, Metis, and Scroll
4748

48-
On Optimism, BASE, and Metis, the sequencer's status is relayed from L1 to L2 where the consumer can retrieve it.
49+
On Optimism, BASE, Metis, and Scroll, the sequencer's status is relayed from L1 to L2 where the consumer can retrieve it.
4950

5051
<ClickToZoom src="/images/data-feed/l2-diagram-optimism-metis.webp" />
5152

@@ -69,7 +70,7 @@ On Optimism, BASE, and Metis, the sequencer's status is relayed from L1 to L2 wh
6970

7071
1. Consumers can then read from the `AggregatorProxy` contract, which fetches the latest round data from the `OptimismSequencerUptimeFeed` contract.
7172

72-
### Handling outages on Optimism, BASE, and Metis
73+
### Handling outages on Optimism, BASE, Metis, and Scroll
7374

7475
If the sequencer is down, messages cannot be transmitted from L1 to L2 and **no L2 transactions are executed**. Instead, messages are enqueued in the `CanonicalTransactionChain` on L1 and only processed in the order they arrived later when the sequencer comes back up. As long as the message from the validator on L1 is already enqueued in the `CTC`, the flag on the sequencer uptime feed on L2 will be guaranteed to be flipped prior to any subsequent transactions. The transaction that flips the flag on the uptime feed will be executed before transactions that were enqueued after it. This is further explained in the diagrams below.
7576

0 commit comments

Comments
 (0)