-
Notifications
You must be signed in to change notification settings - Fork 122
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
Conversation
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 |
Very glad to see this feature back. Awesome job guys. |
8b5bfa9
to
67e8359
Compare
@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.
|
3d4d217
to
0d47fac
Compare
0d47fac
to
e2eb658
Compare
|
Yes, |
Will this be included in Fort Canning Great World? |
This PR also changes on the GW fork the stake modifier calculation to use the MN owner address instead of the operator address.