-
Notifications
You must be signed in to change notification settings - Fork 370
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
gzeoneth
wants to merge
3
commits into
master
Choose a base branch
from
gzeoneth-patch-1
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
anegg0
approved these changes
Feb 24, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
arbitrum-docs/build-decentralized-apps/arbitrum-vs-ethereum/04-solidity-support.mdx
Outdated
Show resolved
Hide resolved
…-solidity-support.mdx
pete-vielhaber
approved these changes
Feb 25, 2025
TucksonDev
reviewed
Feb 26, 2025
@@ -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). | |
There was a problem hiding this comment.
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.