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.
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
Support the Arbitrum BoLD Challenge Protocol in Nitro #2362
Support the Arbitrum BoLD Challenge Protocol in Nitro #2362
Changes from 10 commits
5bba5e0
9d720a8
2467ac0
22ccdb7
2a44c92
b8c6502
100ad6e
abbcd20
5935794
2cb59b9
a7f2fbe
053cb36
6c4c401
7b77f7f
4e7b4a5
cbc3f7e
983a1e8
2a313c1
6835a7b
099d03c
bfba244
5ccbbb4
af8cc34
ba2e3b1
a171c95
0375950
b9c6c10
c3d8ec8
4e599d4
751f1d9
9a9012d
192e047
6a33e3e
33e2ca8
6470551
e57b0b0
737b99e
9ae02fc
28ba3e6
0b217ac
573880a
9363a29
e721188
0b59ee3
494d2a6
43d3da8
9aa0a82
99a6252
a2d9e45
b2f8e53
06f49df
6c2781e
6704f92
2c58a9e
c2b0f82
ad8b825
4426b46
e5e4ea1
6abb7cb
928a8f8
d66cc0e
d7efbab
57a0d95
b3f29c0
9565823
528f868
69bc7bd
886a21d
e9cc824
58e093f
f89cbd8
6a8b741
06663c2
c3f737e
7ed6155
d770502
8f8459d
513bee2
30f125b
25d0437
8fb0788
9ab81eb
59fc8a5
5774b3d
8e3e19a
0437e7b
4bfe480
9973230
746978c
a6a2312
a6a29e1
a63950c
20a9857
e0154ec
65819f0
5589f2b
6656d0e
3b9ad4d
2506150
7012c91
5f2e60d
658a5ce
7ce2089
8265691
a525bb1
0a078a7
051095f
c56a509
d3e62a4
6011b74
633f175
57af6a4
533fceb
e3b8d70
c6faf78
2d479d1
e1d40d3
4914c34
abdc7a1
efdeb8d
8446078
3b2cfdb
b28b78c
220d133
3c86220
2205adb
d97ae8e
748a9f6
f3bf2ac
e734a4d
88d143b
8e12821
c102262
c80e048
7975a06
5334e63
b6cb5a1
027a13b
c305135
b23ab2c
66ebcfc
7e77151
b3dd61d
344eb20
7ededde
77ff553
6497de1
f7588dc
0a2f031
10ffac0
dba3e46
a5f3cf7
5caa3a2
2b1de35
ccdc7d8
60daa96
8606740
8e39be5
04a8d83
4649a54
b38a1fa
976a18f
4c316e5
11afd69
c3f806e
6e20fc6
e0fd4df
463f167
259a4eb
30af4ff
e712059
d3266db
ae1d18a
7056809
2f0bc89
0abf704
683d190
d763207
bf1838e
d0bf3f4
7c1140f
361a747
e9373e7
4a323c3
0aa337a
0f2fd1c
7537061
b053a14
1e0461f
6cc1d2f
331c12e
f36ed0d
19bc1ef
4aba248
72ba88d
eed7b12
e0a4a0f
b4f9dad
c2ac13a
0aa0cf8
2821084
7b92647
dac6070
1f259a9
f1de4c5
11b270e
9e07266
8aff5ee
cdee55d
e9ecd45
bd7bd35
b6ee9d2
89b4cb5
6608888
5cec6a7
0e6e2a8
1ad24f2
fd85fcd
e5b5354
4977148
e2a41e7
c63db41
b9e263f
6a0754a
abee6b8
cdf48cf
c874ed5
6cd3aec
023ce1e
7b43136
855462b
17f0bbb
14796b3
1d0c06f
027e2bd
6365875
bd2adae
ec0a917
828ebf4
25a0f89
1f436a6
dc36a3f
d706059
46d742e
8518e3d
1e635e4
d372f30
a64cb81
1a47581
76a8a0f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Does this work for L3s? Is CreatedAtBlock the parent chain block number or the L1 block number?
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.
It is set by the rollup contract as
block.number
when the assertion is created on the parent chain. I presume this will refer to the parent chain block number for L3sThere 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.
No, unfortunately
block.number
on arb1 returns the L1 block number not the L2 block number. For the old rollup we had a separate lookup table for this accessible via getNodeCreationBlockForLogLookup. Do we have the same in bold?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.
Looks like we'll have to change a few places inside of the bold/ folder as well to fix this behavior. Added to tasks here https://linear.app/offchain-labs/issue/NIT-2971/bold-l3-support-is-broken-as-assertioncreatedatblock-points-to-the-l1s. It seems L3 support won't work until we fix it
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.
Sounds good, since this only blocks L3 support I don't think it needs to block merging