Skip to content

Commit

Permalink
Update LINK token faucet and bridge info (#1765)
Browse files Browse the repository at this point in the history
* 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 <98668332+khadni@users.noreply.github.com>
  • Loading branch information
dwightjl and khadni authored Feb 28, 2024
1 parent a4c7098 commit b72e599
Show file tree
Hide file tree
Showing 7 changed files with 51 additions and 128 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,6 @@ Chainlink Automation is available on the following networks. All networks operat
- Testnet (Automation v1.2)
- [Arbitrum](#arbitrum)
- Mainnet
- Goerli testnet
- Sepolia testnet
- [Optimism](#optimism)
- Mainnet
Expand Down
9 changes: 5 additions & 4 deletions src/content/data-feeds/l2-sequencer-feeds.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,14 +19,15 @@ You can find proxy addresses for the L2 sequencer feeds at the following address

- Arbitrum:
- Arbitrum mainnet: [0xFdB631F5EE196F0ed6FAa767959853A9F217697D](https://arbiscan.io/address/0xFdB631F5EE196F0ed6FAa767959853A9F217697D)
- Arbitrum Goerli testnet: [0x4da69F028a5790fCCAfe81a75C0D24f46ceCDd69](https://goerli-rollup-explorer.arbitrum.io/address/0x4da69F028a5790fCCAfe81a75C0D24f46ceCDd69)
- Optimism:
- Optimism mainnet: [0x371EAD81c9102C9BF4874A9075FFFf170F2Ee389](https://optimistic.etherscan.io/address/0x371EAD81c9102C9BF4874A9075FFFf170F2Ee389)
- Optimism Goerli testnet: [0x4C4814aa04433e0FB31310379a4D6946D5e1D353](https://goerli-optimism.etherscan.io/address/0x4C4814aa04433e0FB31310379a4D6946D5e1D353)
- BASE:
- BASE mainnet: [0xBCF85224fc0756B9Fa45aA7892530B47e10b6433](https://basescan.org/address/0xBCF85224fc0756B9Fa45aA7892530B47e10b6433)
- Metis:
- Andromeda mainnet: [0x58218ea7422255EBE94e56b504035a784b7AA204](https://andromeda-explorer.metis.io/address/0x58218ea7422255EBE94e56b504035a784b7AA204)
- Scroll:
- Scroll mainnet: [0x95BcCbBBaCBB7ed224AC2EE38531f2467DF41Ea4](https://scrollscan.com/address/0x95BcCbBBaCBB7ed224AC2EE38531f2467DF41Ea4)

### Arbitrum

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

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.

## Optimism, BASE, and Metis
## Optimism, BASE, Metis, and Scroll

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

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

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

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

### Handling outages on Optimism, BASE, and Metis
### Handling outages on Optimism, BASE, Metis, and Scroll

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.

Expand Down
Loading

0 comments on commit b72e599

Please sign in to comment.