Merge branch 'master' into node-running-overview

OffchainLabs · Oct 15, 2024 · eb45bd2 · eb45bd2
2 parents 6b8372b + 927d5f7
commit eb45bd2
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 0 deletions.
diff --git a/arbitrum-docs/launch-orbit-chain/infra-options-orbit-chains.md b/arbitrum-docs/launch-orbit-chain/infra-options-orbit-chains.md
@@ -64,6 +64,7 @@ Indexers provide a convenient way to retrieve historic or application-specific d
 - [The Graph](https://thegraph.com/)
 - [Goldsky](https://goldsky.com/)
 - [Ormi](https://www.ormilabs.xyz/)
+- [Traceye](https://traceye.io/)
 
 ## Oracles
 

diff --git a/arbitrum-docs/run-arbitrum-node/sequencer/02-read-sequencer-feed.md b/arbitrum-docs/run-arbitrum-node/sequencer/02-read-sequencer-feed.md
@@ -88,3 +88,9 @@ Using the feed relay, you can also retrieve the `L2 block number` of a message:
 
 - On <a data-quicklook-from="arbitrum-one">Arbitrum One</a>, this can be done by adding the Arbitrum One genesis block number (22207817) to the sequence number of the feed message.
 - Note that in the case of <a data-quicklook-from="arbitrum-nova">Arbitrum Nova</a>, the Nitro genesis number is `0`, so it doesn't need to be included when adding to the feed message's sequence number.
+
+:::info
+
+Note that the `messagess[0].message.message.header.blockNumber` is `L1 block number` instead of `L2 block number`
+
+:::