Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: block.number description for orbit #2102

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from
Draft

Conversation

gzeoneth
Copy link
Member

No description provided.

Copy link

vercel bot commented Feb 24, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
arbitrum-docs ✅ Ready (Inspect) Visit Preview Feb 26, 2025 2:53am

Copy link
Contributor

@anegg0 anegg0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@@ -21,6 +21,6 @@ Although Arbitrum supports Solidity code, there are differences in the effects o
| `block.coinbase` | Returns the designated internal address `0xA4b000000000000000000073657175656e636572` if the message was posted by a sequencer. If it's a delayed message, it returns the address of the delayed message's poster (Note: the handling of delayed message's `block.coinbase` will likely be changed in a future ArbOS version). |
| `block.difficulty` | Returns the constant 1. |
| `block.prevrandao` | Returns the constant 1. |
| `block.number` | Returns an "estimate" of the parent chain block number at which the sequencer received the transaction. For more information, see [Block numbers and time](/build-decentralized-apps/arbitrum-vs-ethereum/02-block-numbers-and-time.mdx). |
| `block.number` | Returns an "estimate" of the first ancestor non Arbitrum chain (i.e., for Arb1 and L3 on Arb1 -> L1, for L3 on Base -> Base) block number at which the sequencer received the transaction. For more information, see [Block numbers and time](/build-decentralized-apps/arbitrum-vs-ethereum/02-block-numbers-and-time.mdx). |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| `block.number` | Returns an "estimate" of the first ancestor non Arbitrum chain (i.e., for Arb1 and L3 on Arb1 -> L1, for L3 on Base -> Base) block number at which the sequencer received the transaction. For more information, see [Block numbers and time](/build-decentralized-apps/arbitrum-vs-ethereum/02-block-numbers-and-time.mdx). |
| `block.number` | Returns an "estimate" of the block number in the first non Arbitrum chain ancestor (i.e., for Arbitrum One and any L3s on top of Arbitrum One, the first non Arbitrum chain ancestor is Ethereum (L1); for L3s on top of Base, the first non Arbitrum chain ancestor is Base) at which the sequencer received the transaction. For more information, see [Block numbers and time](/build-decentralized-apps/arbitrum-vs-ethereum/02-block-numbers-and-time.mdx). |

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants