protx update_service. protx-dup issue

Rul

New Member
May 8, 2022
35
2
8
22
Hello!
I am trying to recover my masternode with protx update_service help. But when use it in debug console it says "protx-dup (code 18) (code -26)". How can I fix this?
 

qwizzie

Grizzled Member
Aug 6, 2014
2,019
1,201
1,183
Yes, I followed these instructions. Maybe problem is in dashd version? I have zeus and 18.0.1 version. Is it updating automatically or do I need to do something?
At the very least i would recommend that you update to v18.1
Ask xkcd for help if you have a problem updating to v18.1 from within Zeus : https://www.dash.org/forum/threads/dash-masternode-zeus-replacement-for-dashman.51618/

With regards to getting your masternode unbanned : have you actually verified that you used the original proTxHash ? I would doublecheck every field that you used there, before getting that error message. Also make sure you have funds available for the protx update_service transaction fee in your feeSourceAddress.
 
Last edited:

Rul

New Member
May 8, 2022
35
2
8
22
At the very least i would recommend that you update to v18.1
Ask xkcd for help if you have a problem updating to v18.1 from within Zeus : https://www.dash.org/forum/threads/dash-masternode-zeus-replacement-for-dashman.51618/

With regards to getting your masternode unbanned : have you actually verified that you used the original proTxHash ? I would doublecheck every field that you used there, before getting that error message. Also make sure you have funds available for the protx update_service transaction fee in your feeSourceAddress.
I have version18.1. I will doublecheck everything! Thank you for the answer!
 
  • Like
Reactions: xkcd

Rul

New Member
May 8, 2022
35
2
8
22
What can be the problem if I do protx update service, write feeSourceAdress and output says that there is no funds on it, but there are funds?
 

splawik21

Yeah, it's me....
Dash Core Group
Foundation Member
Dash Support Group
Apr 8, 2014
1,966
1,327
1,283
The workaround is to not put the Dash address for "feesourceaddress" but you need to put a little balance into the "payoutaddress" instead.
edit: I mixed it up with registering of the MN where I experienced similar issue on v18.1 with one of the clients.
 
Last edited:
  • Like
Reactions: Rul

xkcd

Active Member
Masternode Owner/Operator
Feb 19, 2017
464
435
133
australia
mnowatch.org
Dash Address
XpoZXRfr2iFxWhfRSAK3j1jww9xd4tJVez
Probably you are not skipping over the payment address, here's how you should construct the command.
Code:
protx update_service proTxHash ipAndPort operatorKey "" feeSourceAddress
Please note, the fee source address must have at least 1000 Duffs in it and be in the same wallet you are running the protx command from and the wallet must be unlocked when you run the command.
 
  • Like
Reactions: AgnewPickens

Rul

New Member
May 8, 2022
35
2
8
22
Probably you are not skipping over the payment address, here's how you should construct the command.
Code:
protx update_service proTxHash ipAndPort operatorKey "" feeSourceAddress
Please note, the fee source address must have at least 1000 Duffs in it and be in the same wallet you are running the protx command from and the wallet must be unlocked when you run the command.
Thank you for the help!
 
  • Like
Reactions: xkcd