Add hard fork to include more claim data #375
No reviewers
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
hard fork
help wanted
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
soft fork
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
work in progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbrycrd#375
Loading…
Reference in a new issue
No description provided.
Delete branch "hash_bit_seq"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It's future hard fork request to ensure:
=&#:$@%?;\/"<>*\n\t\r\b\0
in claim nameAdjust consensus parameter
nClaimInfoInMerkleForkHeight
to allow it in production as well asnMaxRemovalWorkaroundHeight
to purge out implementation detail bug which allow addition of claim without delay, see comments for more details.The original list of that must be included in the fork:
It was decided that item 2 could be done by enforcing it at the mempool level only. The name enforcement does not need to become part of consensus. Hence, it technically doesn't need a fork.
It appears that item 1 is not in this changeset? Actually, it looks like we simply need to set the nMaxRemovalWorkaroundHeight. (We also need to set the other effective heights for this fork.)
The maximum metadata size should probably be doubled. No more than that.
Pull request closed