repair bad hash computation in miner #283
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#283
Loading…
Reference in a new issue
No description provided.
Delete branch "bad_hash_in_miner"
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?
fixed ancestors not all in claim trie on packageFees condition
Break or return does not make any difference. After the loop we end up with function return. I don't think we should throw away all txs after a low fee one.
As I understand it, this is a miner's feature. We're reading in transactions in order of highest fee density to lowest fee density. You can configure the minimum fee per byte, and if we go below that we're done. Miners want the privilege of being able to ignore transactions below a certain fee; it's to their advantage to hash less data. This will become more important as the mined block payment reduces over time.
Ah, i see get it by ancestor_score it will be from high to low, so after that all other txs are with lowest fee - then ok, we can keep return as well.