Implement a hard fork for extended/infinite claim expiration times #112
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#112
Loading…
Reference in a new issue
No description provided.
Delete branch "claim-expiration"
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?
Nice.
I think we first need to get a version of this that is not mainnet altering so that downstream LBRY devs can finally test expiration better using regtest and maybe testnet (they haven't been able to because of the long expiration time that was fixed and generating that many blocks take too long).
I made some alterations on this branch: https://github.com/lbryio/lbrycrd/commits/claim-expiration
This branch changes mainnet chainparams so that there should be no forking change in expiration on the mainnet
3539af2a2b
I made it so that it claim expiration is not disabled by default, and utilized a #define statement, I made the if statement a bit easier to understand by using nCurrentHeight on CClaimTrie
c3646afb63
I was succesfully able to resync to the main-net with these changes. Let me know what you think.
@kaykurokawa Thanks for looking at this!
Explicitly disabling on mainnet is a fine idea so long as we're not looking to hard fork. The testnet/regtest params were already independent, so they could be tested at any reasonable heights. I agree picking an arbitrary mainnet fork height needs discussion, so for now, disabling is a fair option to move ahead with any testing required.
Closing this and continuing here: https://github.com/lbryio/lbrycrd/pull/115
Pull request closed