-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
wallet, simplewallet: Drop support for mine-to-use RPC system #8724
wallet, simplewallet: Drop support for mine-to-use RPC system #8724
Conversation
New wallet connecting old rpc mine-to-use node error msg: (i guess the refresh thread line could be dropped, and im not sure about the See . Block received: 0 being on the same line)
👍 |
@plowsof Thanks for testing. That error message was a typo, I meant to put the link to the relevant GH issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had a go at it. Pretty clear of course because mostly deleting stuff.
@@ -4517,7 +4517,6 @@ class t_daemon | |||
|
|||
const auto arg_wallet_file = wallet_args::arg_wallet_file(); | |||
const auto arg_from_json = wallet_args::arg_generate_from_json(); | |||
const auto arg_rpc_client_secret_key = wallet_args::arg_rpc_client_secret_key(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am a bit confused: If I checked correctly you let a lot of RPC payment related stuff stand in the wallet RPC server, but out all possible things to delete you only delete things related to this key.
If that's really the case, what's the idea here?
@rbrunner7 Thanks for reviewing! I updated the PR with some of your comments. What did you mean by "you let a lot of RPC payment related stuff stand in the wallet RPC server"? Would you please be able to point me to that? |
Well, I did a simple search for "rpc_pay" in the file |
IIUC, those RPC endpoints are unrelated to the mine-to-use system. AFAIK, those are RPC commands for retrieving general purpose payment information. |
(Slaps forehead) Of course, you are right, that's purely coincidence that the string "rpc_pay" results there. But then I am still a bit confused: How can it be that the RPC server has (almost) no RPC Pay related code in it? Does that mean that it doesn't implement that? Or is it enough for it to work that merely |
Haha... there's certain words that don't seem like words to me anymore: transaction, payment, mine, access, daemon, etc. They all kinda blur together.
Yes, I believe so. I really think the only wallet that supported mine-to-use was simplewallet, and not by default either. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Let's shed a last tear for all the good code that mooo implemented for this feature, and enjoy the simplified wallet code :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed. Thank you for working on this.
34f0726
to
ed16f53
Compare
Squashed and rebased against master |
ed16f53
to
b7820e4
Compare
Rebased against master again to resolve conflicts with #8076 |
I had a look at the rebase changes as far as they merge code in from my own #8076 (probably the largest single source of conflicts), and compiled the rebased code for a quick check whether pool handling still works. I could not find any problems, this gets an "ok" from me. |
Using post-PR wallet with pre-PR node will generate error message specific to this PR and not generic "command failed" mesages.
b7820e4
to
d2a591d
Compare
Rebased against master again to fix merge conflicts with #8698 |
To verify rebase:
|
The main thing to test here is new wallet UX with old RPC mine-to-use node. Using post-PR wallet with pre-PR node should generate error message specific to this PR and not generic "command failed" mesages.