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

Restore updatemasternode and combine setforcedrewardaddress / removeforcedaddress #934

Merged
merged 15 commits into from
May 19, 2022

Conversation

Bushstar
Copy link
Member

This PR also changes on the GW fork the stake modifier calculation to use the MN owner address instead of the operator address.

@Stonygan
Copy link

Maybe you can check, why its only allowed to use a Legacy or address from the LightWallet(BECH32?) for a rewardaddress? Normal addresses from the APP or CAKE are not allowed? @Bushstar

@Bushstar Bushstar changed the title Restore updatemasternode, setforcedrewardaddress and removeforcedaddress Restore updatemasternode and combine setforcedrewardaddress / removeforcedaddress Nov 26, 2021
@mjollnir14
Copy link

Very glad to see this feature back. Awesome job guys.

src/masternodes/mn_checks.cpp Outdated Show resolved Hide resolved
@prasannavl prasannavl added this to the 3.x - Great World milestone Dec 7, 2021
@Bushstar
Copy link
Member Author

Bushstar commented Dec 9, 2021

@Stonygan I expect that the initial idea was to simplify ownership. P2PKH and P2WPKH are the Legacy and Bech32 address types, these are simple addresses derived from a private key. The other address type you mention is P2SH-P2WPKH which wraps P2WPKH in P2SH, to accept this we have to accept all P2SH addresses and we do not know how those addresses were created, they could be multi-sig or a different type of script entirely. Better to keep things simple than let people get into trouble.

If you have access to the DeFi CLI console you can generate a legacy or bech32 address with the following commands.

getnewaddress "" "legacy"
getnewaddress "" "bech32"

@chanakasameera
Copy link
Contributor

MasternodeInfo.banTx Attribute becomes undefined by this PR, is it acceptable ?
Related jellyfish test : packages/jellyfish-api-core/tests/category/masternode/createMasternode.test.ts

@bvbfan
Copy link
Contributor

bvbfan commented Mar 4, 2022

Yes, banTx isn't used anywhere, now it's waste of space.

src/masternodes/rpc_masternodes.cpp Outdated Show resolved Hide resolved
src/masternodes/rpc_masternodes.cpp Outdated Show resolved Hide resolved
src/masternodes/rpc_masternodes.cpp Outdated Show resolved Hide resolved
@bvbfan bvbfan requested review from bvbfan and removed request for monstrobishi May 9, 2022 07:59
@prasannavl prasannavl merged commit 0364a90 into v3 May 19, 2022
@prasannavl prasannavl deleted the restore-fc-calls branch May 19, 2022 07:37
@mjollnir14
Copy link

Will this be included in Fort Canning Great World?

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

Successfully merging this pull request may close these issues.

7 participants