Attention Dash Masternode Owners: Please register with the Deterministic Masternode List now

Status
Not open for further replies.
Hi Everyone,

We've been struggling to start our masternode with the DIP003 protocol. With the last step as mentioned on this page we're getting the below error:
Code: 
bad-protx-key-not-same (code 16) (code -1)

We're using the same address (newly generated) for both the owner and voting address, tried different ones as-well. We've tried swapping out different variables (keys), with no luck as we keep hitting that same error.

We're out of clues and at this point any advice would be greatly appreciated.
 
Curacao said:
Hi Everyone,

We've been struggling to start our masternode with the DIP003 protocol. With the last step as mentioned on this page we're getting the below error:
Code: 
bad-protx-key-not-same (code 16) (code -1)

We're using the same address (newly generated) for both the owner and voting address, tried different ones as-well. We've tried swapping out different variables (keys), with no luck as we keep hitting that same error.

We're out of clues and at this point any advice would be greatly appreciated.
Click to expand...

Currently spork 15 isn’t activated so that voting address must be same with owner address. You can update different voting address after spork 15 activated.
 
As clearly mentioned in our post, we've tried using the same keys, we've tried all possible combination and keep hitting that same error.
 
Curacao said:
As clearly mentioned in our post, we've tried using the same keys, we've tried all possible combination and keep hitting that same error.
Click to expand...
you mentioned "with the last step" you hit that errorcode... which step is that exactly ?

Prepare a ProRegTx transaction ?
Sign the ProRegTx transaction ?
Submit the signed message ?




 
Last edited:
qwizzie said:
you mentioned "with the last step" you hit that errorcode... which step is that exactly ?

Prepare a ProRegTx transaction ?
Sign the ProRegTx transaction ?
Submit the signed message ?
Click to expand...
When executing the last command:
Code: 
protx register_submit ***
 
Curacao said:
When executing the last command:
Code: 
protx register_submit ***
Click to expand...

that command consists of two parts :

  • tx: The serialized transaction previously returned in the tx output field from the protx register_prepare command
  • sig: The message signed with the collateral key from the signmessage command
Make sure tx is copied within its specific brackets --> ""

example of wrong usage :

"tx":
"030001000191def1f8bb265861f92e9984ac25c5142ebeda44901334e304c447dad5adf6070000000000feffffff0121dff505000000001976a9149e2deda2452b57e999685cb7dabdd6f4c3937f0788ac00000000d1010000000000c7fd27022913dd8505ae701e0fd56625c3fa9d2ff47802225faae562389e492c0100000000000000000000000000ffff8c523b334e1fad8e6259e14db7d05431ef4333d94b70df1391c601d2c43f022eeceaaf09532d84350feb49d7e72c183e56737c816076d0e803d4f86036bd4151160f5732ab4a461bd127ad8e6259e14db7d05431ef4333d94b70df1391c600001976a914adf50b01774202a184a2c7150593442b89c212e788acf8d42b331ae7a29076b464e61fdbcfc0b13f611d3d7f88bbe066e6ebabdfab7700", "collateralAddress": "yPd75LrstM268Sr4hD7RfQe5SHtn9UMSEG",

example of right usage :

030001000191def1f8bb265861f92e9984ac25c5142ebeda44901334e304c447dad5adf6070000000000feffffff0121dff505000000001976a9149e2deda2452b57e999685cb7dabdd6f4c3937f0788ac00000000d1010000000000c7fd27022913dd8505ae701e0fd56625c3fa9d2ff47802225faae562389e492c0100000000000000000000000000ffff8c523b334e1fad8e6259e14db7d05431ef4333d94b70df1391c601d2c43f022eeceaaf09532d84350feb49d7e72c183e56737c816076d0e803d4f86036bd4151160f5732ab4a461bd127ad8e6259e14db7d05431ef4333d94b70df1391c600001976a914adf50b01774202a184a2c7150593442b89c212e788acf8d42b331ae7a29076b464e61fdbcfc0b13f611d3d7f88bbe066e6ebabdfab7700

Make sure the sig is fully copied as well and that there is a space between tx and sig.

If this does not help i suggest you re-do the protx register_prepare command from start, making sure both ownerKeyAddr and votingKeyAddr are the same (as you did the first time) and make sure you use the BLS public key with the operatorPubkey. Also check if you need to use feeSourceAddress (which needs to have some small funds) to get this transaction through.
 
Last edited:
Hi Qwizzie,

We didn't use brackets (""), and we're pretty sure everything was copied correctly. Prepared everything in notepad window so just copy pasted into the dash debug window. Yeah we're out of clues as well.
 
Curacao said:
Hi Qwizzie,

We didn't use brackets (""), and we're pretty sure everything was copied correctly. Prepared everything in notepad window so just copy pasted into the dash debug window. Yeah we're out of clues as well.
Click to expand...

Strange to see "bad-protx-key-not-same (code 16) (code -1)" in the "Submit the signed message" step (the final step). Hopefully a dev team member can provide a better explanation for these two error codes.
(i'm out of clues myself at this point)
 
Curacao said:
Hi Qwizzie,

We didn't use brackets (""), and we're pretty sure everything was copied correctly. Prepared everything in notepad window so just copy pasted into the dash debug window. Yeah we're out of clues as well.
Click to expand...

Are you registering your masternode with v0.13.2 ? If yes, have you put the BLS priv key in the dash.conf ? (both on local and on your server) and restarted the server ?

Dash Community,

We are pleased to announce the release of Dash Core v0.13.2 to mainnet. This release contains several optimizations to Dash Core v0.13 to provide an easier user experience for masternode owners as well as fix a few bugs the team found during the initial rollout. This upgrade is non-mandatory, but is recommended for all users.

Below are a few highlights of this release.

Mandatory “masternodeblsprivkey” field when configuring and running a masternode
This field was not mandatory in previous versions that had to function with and without DIP3 (Deterministic Masternode List) activated. Now that DIP3 has activated, this field will be required to ensure that masternode owners enter their operator key. This field will check that the format of the key entered is valid, and return an error if the key format is incorrect.
Click to expand...
 
Hi qwizzie,

That might just be it, we'll try that. In the wiki it isn't clearly mentioned that the bls private key should also be added to the client's dash.conf file. We'll follow up.
 
Hi everyone,

We've managed to get the MN up again. Indeed we needed to put the BLS Priv key in both the MN as client config. That was our mistake. This wasn't clearly mentioned in the wiki page. Thank you all for your assistance!
 
Hi, I just updated masternode following the guide, and "dash-cli masternode list" is showing my mn, but the owner address and voting address have changed to something else which is not in my registration tx message, how is that possible?
 
I just followed the guide, no DMT, done from a PC client 0.13.2 without any problem in the process. Is it possible for some to intercept my tx and change the owneraddress to something else?

In my understanding of cryptocurrency, a signed message is not possible to change dramatically even with transaction malleability, I guess it is a listing problem?
 
Last edited:
masternube said:
When exactly will Spork 15 be activated?

I think I found the answer here:
https://blog.dash.org/spork-15-activation-april-2-2ee937afb64d

"Therefore we now plan to activate spork 15 on April 2, the day after the next super block payout."
Click to expand...

Yep, in 2 days. Spork 16 will follow soon after that. And in 10 days (more or less) we will have our annual blockreward reduction (-7.1%) also.
Link : https://stats.masternode.me/network-report/226667

So a few important events coming up in a short time period.
 
Last edited:
3uxHeO3.jpg

Spork 15 is active ? Or is it a cruel first fools day joke ? o_O
 
Status
Not open for further replies.
Back
Top