Repository navigation
Conversation
datum.coinbaser_reuse defaults to false. Job 1 and job 2 stay one pool output, and a missing coinbaser answer still publishes that one output. When the option is on and a multi-out list has been saved, the opening notify uses that list at the subsidy. The fee template uses the same list stretched to the fee total until the pool's own split arrives. A missing or short answer on the later job stretches that list too. No saved list leaves the one-output coinbase in place.
|
This is not a good config option. In most ordinary cases, the pool can't account for it (the funds already ended up in the wrong place). And unless the previous block was empty, it won't be the right sum anyway. If there's an actual use case for a pool (one that doesn't care about the sum?), it should be implemented as a pool config option, not a user config option. |
Author
|
the code scales coinbase (same %) to the new blocks payout when used along with 39/40 code |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
datum.coinbaser_reuse defaults to false.
New block Job 1 and job 2 stay one pool output, and a missing coinbaser answer still publishes that one output. as is now.
When the option is on and a multi-out list has been saved, the opening notify uses that list at the subsidy. The fee template uses the same list stretched to the fee total until the pool's own split arrives. A missing or short answer on the later job stretches that list too. No saved list leaves the one-output coinbase in place.
one caveat, the pool might need to do accounting for a double block on its own pool. riptide handles is as a bonus double payment for the previous 8 blocks, rather than a low work single payment with pool only payment. so they already have to do an accounting as well.