Skip to content

Commit

Permalink
Update arbitrum-integration.md (#1387)
Browse files Browse the repository at this point in the history
* Update arbitrum-integration.md

change in fall back on method to ability
change in link to sequencer_inbox.go

* fix: use v2.2.2 release link

* Update developers/arbitrum-integration.md

---------

Co-authored-by: jcstein <[email protected]>
Co-authored-by: Josh Stein <[email protected]>
  • Loading branch information
3 people authored Jan 31, 2024
1 parent ea57962 commit 874ec9d
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions developers/arbitrum-integration.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,13 +51,13 @@ which relays commitments to Celestia’s data root to an onchain light client
on Ethereum. This allows L2 solutions that settle on Ethereum to benefit
from the scalability Celestia’s data availability layer can provide.

As part of this integration, Blobstream has been incorporated into the
As part of this integration, Blobstream is being called from the
Arbitrum `SequencerInbox.sol` contract.

In the `SequencerInbox.sol` contract, the `validateBatchData`
modifier has been designed to authenticate that the data root is
on Celestia when reading a batch of data. This is achieved by the
[following code by @Ferret-san](https://gist.github.com/Ferret-san/3d3fc1b5738ee8d77ad112c0eb8bbe5f):
[following code in `arbnode/sequencer_inbox.go`](https://github.com/celestiaorg/nitro-contracts/blob/celestia/blobstream/src/bridge/SequencerInbox.sol#L334-L360):

Note that the data above is the bytes serialized version of this struct in Go:

Expand Down Expand Up @@ -101,8 +101,8 @@ The [@celestiaorg/nitro](https://github.com/celestiaorg/nitro) integration
[uses the same fallback mechanism](https://github.com/celestiaorg/nitro/blob/f01968eb3d4e19329e9c92b050e98a8e5772f1f2/arbnode/batch_poster.go#L845-L857).

The fallback logic for Celestia DA is configurable, providing an alternative
to the previous default fallback mechanism. Additionally, a method has been
added to the Arbitrum node software. This method allows the sequencer to call
to the previous default fallback mechanism. Additionally, an ability has been
added to the Arbitrum node software which allows the sequencer to call
`VerifyAttestation` to check if a data root has been posted on Blobstream or
not, before it sends the sequencer message (data pointer) to the underlying
chain.
Expand Down

0 comments on commit 874ec9d

Please sign in to comment.