-
Notifications
You must be signed in to change notification settings - Fork 320
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
Stop forcing the last reserved byte to 0 for compact shares #779
Labels
bug
Something isn't working
consensus breaking
modifies block validity rules in a way that will break consensus unless all nodes update their rules
Comments
rootulp
added
the
discussion
inherently unactionable issue for the sole purpose of discussion
label
Sep 23, 2022
I'm confused by this as well.
perhaps we should rethink this now that we are adding the length delimiter to compact shares (formerly contiguous shares) |
Based on synchronous discussion, it seems like the last transaction share shouldn't force the reserve byte to zero. |
rootulp
added
bug
Something isn't working
and removed
discussion
inherently unactionable issue for the sole purpose of discussion
labels
Sep 29, 2022
evan-forbes
added
the
consensus breaking
modifies block validity rules in a way that will break consensus unless all nodes update their rules
label
Sep 29, 2022
evan-forbes
changed the title
Why is reserved byte of last compact share forced to zero?
Stop forcing the last reserved byte to 0 for compact shares
Sep 29, 2022
rootulp
added a commit
to rootulp/celestia-app
that referenced
this issue
Sep 29, 2022
rootulp
added a commit
to rootulp/celestia-app
that referenced
this issue
Sep 29, 2022
This was referenced Sep 29, 2022
rootulp
added a commit
to rootulp/celestia-app
that referenced
this issue
Sep 29, 2022
rootulp
added a commit
that referenced
this issue
Sep 30, 2022
Repository owner
moved this from TODO
to Done
in Celestia Node
Sep 30, 2022
rach-id
pushed a commit
to rach-id/celestia-app
that referenced
this issue
Nov 16, 2022
cmwaters
pushed a commit
to celestiaorg/go-square
that referenced
this issue
Dec 14, 2023
0xchainlover
pushed a commit
to celestia-org/celestia-app
that referenced
this issue
Aug 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
consensus breaking
modifies block validity rules in a way that will break consensus unless all nodes update their rules
Question
Why is reserved byte of last compact share forced to zero? This behavior seems undesirable if the last compact share contains a new transaction.
Context
Link
celestia-app/pkg/shares/split_compact_shares.go
Lines 141 to 145 in 907da5f
The text was updated successfully, but these errors were encountered: