Skip to content
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

Proposer finalization rewards #811

Closed

Conversation

Nizametdinov
Copy link
Member

@Nizametdinov Nizametdinov commented Mar 20, 2019

This pull request implements proposer finalization rewards. See the details in #418.

@thothd thothd requested a review from Gnappuraz March 20, 2019 13:05
@Nizametdinov Nizametdinov force-pushed the proposer-finalization-rewards branch from 4234aa7 to 12e6701 Compare March 20, 2019 13:06
@Nizametdinov Nizametdinov force-pushed the proposer-finalization-rewards branch 2 times, most recently from afdd628 to 03fc85b Compare March 27, 2019 20:34
@Nizametdinov Nizametdinov force-pushed the proposer-finalization-rewards branch 2 times, most recently from e63cdd4 to 74f0e3b Compare April 2, 2019 14:24
@Nizametdinov Nizametdinov force-pushed the proposer-finalization-rewards branch from 4d9830d to a4ea67d Compare April 8, 2019 10:03
@Nizametdinov Nizametdinov marked this pull request as ready for review April 8, 2019 10:06
@Nizametdinov Nizametdinov force-pushed the proposer-finalization-rewards branch from 5555806 to 4a18cb4 Compare April 8, 2019 10:24
@Nizametdinov Nizametdinov requested a review from a team April 8, 2019 11:34
src/consensus/tx_verify.cpp Outdated Show resolved Hide resolved
src/proposer/finalization_reward_logic.cpp Outdated Show resolved Hide resolved
src/test/tx_verify_tests.cpp Show resolved Hide resolved
test/functional/feature_finalization_rewards.py Outdated Show resolved Hide resolved
src/consensus/tx_verify.cpp Outdated Show resolved Hide resolved
src/injector.h Show resolved Hide resolved
src/injector.h Show resolved Hide resolved
@Nizametdinov Nizametdinov force-pushed the proposer-finalization-rewards branch 3 times, most recently from 9e3eb22 to 2f74883 Compare April 10, 2019 08:49
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
Remove unused import in feature_ltor

Signed-off-by: Azat Nizametdinov <azat@thirdhash.com>
@Nizametdinov Nizametdinov force-pushed the proposer-finalization-rewards branch from b22997c to 022ac5c Compare April 11, 2019 08:38
@thothd thothd added this to the 0.2 milestone Apr 11, 2019
cmihai added a commit that referenced this pull request Apr 15, 2019
This commit cherry-picks the GetAmount changes from #811 and fixes the filtertransactions RPC output for coinbase transactions, setting the "fee" field to zero and "amount" to the reward received by the miner. Previously, as a side-effect of the algorithm, it was the other way around.

Signed-off-by: Mihai Ciumeica <mihai@thirdhash.com>
@scravy
Copy link
Member

scravy commented May 6, 2019

I guess this needs rebase.

Maybe it would make sense, since this has already accumulated quite a lot of comments, is quite out of date, etc, and needs heavy rebasing/merging as 0.17 was merged in between – maybe it would make sense to create a fresh pull request and start with a clean slate?

@Nizametdinov
Copy link
Member Author

@scravy I'm going to open a new PR also because my old fork is now detached from the upstream. I'm closing this one and will open a new one soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants