Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
N
nebula
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
exchain
nebula
Commits
57a0209f
Commit
57a0209f
authored
Oct 25, 2023
by
pcw109550
Committed by
Tei Im
Nov 01, 2023
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
specs: Add span batch hardfork rule
parent
8b1df75b
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
0 deletions
+15
-0
span-batches.md
specs/span-batches.md
+15
-0
No files found.
specs/span-batches.md
View file @
57a0209f
...
@@ -9,6 +9,7 @@
...
@@ -9,6 +9,7 @@
-
[
Introduction
](
#introduction
)
-
[
Introduction
](
#introduction
)
-
[
Span batch format
](
#span-batch-format
)
-
[
Span batch format
](
#span-batch-format
)
-
[
Span batch Hard Fork Rule
](
#span-batch-hard-fork-rule
)
-
[
Optimization Strategies
](
#optimization-strategies
)
-
[
Optimization Strategies
](
#optimization-strategies
)
-
[
Truncating information and storing only necessary data
](
#truncating-information-and-storing-only-necessary-data
)
-
[
Truncating information and storing only necessary data
](
#truncating-information-and-storing-only-necessary-data
)
-
[
`tx_data_headers` removal from initial specs
](
#tx_data_headers-removal-from-initial-specs
)
-
[
`tx_data_headers` removal from initial specs
](
#tx_data_headers-removal-from-initial-specs
)
...
@@ -153,6 +154,20 @@ decoding. For example, lets say bad batcher wrote span batch which `block_count
...
@@ -153,6 +154,20 @@ decoding. For example, lets say bad batcher wrote span batch which `block_count
the explicit limit, not trying to consume data until EOF is reached. We can also safely preallocate memory for decoding
the explicit limit, not trying to consume data until EOF is reached. We can also safely preallocate memory for decoding
because we know the upper limit of memory usage.
because we know the upper limit of memory usage.
## Span batch Hard Fork Rule
Span batch hard fork is activated based on timestamp.
Activation Rule:
`x != null && x >= upgradeTime && y != null && y >= upgradeTime`
Let
`inclusion_block`
be the L1 block when the span batch was first fully derived.
`x == span_start.timestamp`
, which is the timestamp of first L2 block timestamp derived from span batch.
`y == inclusion_block.timestamp`
, which is the timestamp of L1 block when span batch was first fully derived.
We need this additional check because span batch hard fork is a derivation update, and
`x`
becomes dependent of the hard fork(we must run span batch decoding to find
`x`
).
## Optimization Strategies
## Optimization Strategies
### Truncating information and storing only necessary data
### Truncating information and storing only necessary data
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment