Search results

If you re-register with an owner key in this local dash-qt wallet, you'll also be able to monitor your MN in the Masternodes tab (Settings>Options>Wallet>Show Masternodes Tab).

If they are in BANNED state, you should be able to create a new registration. You can force ban with protx revoke protxhash operatorblsprivkey I think the reason you can't re-register is because you re-used the same blsprivkey in the dash.conf. The update_registrar can also solve your...

BLS keys are not stored in the wallet. The importprivkey is for real Dash addresses only. https://docs.dash.org/en/stable/docs/user/masternodes/setup.html#generate-a-bls-key-pair

you're missing the FeeSourceAddress at the end, with both of those commands. There are FIVE things in the command: protx update_registrar proTxHash operatorKeyAddr votingKeyAddr payoutAddress feeSourceAddress So if yfvG1iTVVwRnpY3xBCJxczPJWtcQ1nx2H7 is one of your wallet's addresses with money...

First of all, it is always easiest to work with TWO separate things: 1) A remote VPS ssh terminal for the masternode mode only dashd 2) A separate dash-qt wallet, either on a different VPS or synced locally. I know you're just on testnet, but that is how most real-world users will interact and...

You can fix this with protx -testnet update_registrar 14ccde67298cdd799ccc8e053d5b5e853daa076f785a154df4bbae3cc9fa342c 96549902797b501abfd6268e961f17224cd3524fc0683214bbea818a9d84393bfc39d346ae7ce4f47c05b732e558cd62 "" "" to change the operator public key to the one on your Mac

That is because "45ce4e508d3cefd656d160cff9df64d85c97ffce1f6cc5d0335ea0aff7c5a9f5-1" is the collateral hash, not the proTx registration hash. If you type masternodelist json 45ce4e508d3cefd656d160cff9df64d85c97ffce1f6cc5d0335ea0aff7c5a9f5-1 it will show the proTxHash for it.

Try using masternodelist to check the details of the current MN that is conflicting with one of the addresses being duplicated.

What version of DMT did you use? Since we rolled back the v19.0 hard fork (and new BLS scheme), DMT 0.9.33 & 0.9.34 might not work correctly, as they were adjusted to work with v19.0, not v19.1. I think you should use DMT version 0.9.32 if you're generating BLS keypairs or registering/updating...

I still have version 4.1.5.0 installed from F-Droid in 2021, which is still the latest version in the F-Droid repository, and it looks exactly like Bertrand's picture above. Is the OP is trying to open Dash Electrum from a shortcut within another app?

If you can't get in touch with him, you should probably consider a different service provider. You could try https://dashmasternode.io which is run by @splawik21 who is very well known and trusted in this community since the beginning. Every day your masternode is down is costing you money...

You cant do an update_service without the privkey which moocowmoo has. But for update_registrar, you could try protx update_registrar yourprotxhash "" "" "" feesourceaddress (or leave it blank and it uses the payout address if it exists in the wallet you're issuing the command from). see...

One thing you could try is a protx update_registrar and keep all the information the same (use "" to keep the currently registered info) In the off chance he fully updated the MN itself and it is synced on v19.1.0 it might reactivate it. I've never tried it that way, and the docs don't say to do...

Hmm, I think dashninja does not list PoSe Banned masternodes. Your wallet shows it as POSE_BANNED though, right?

It depends how you set it up with him initially. If he was the one who generated the BLS key in the first place, and gave you the BLS owner public key to you so you could register the masternode, then that means only he can issue update_service, because only he has the private key.

My interpretation was that masternode.me is detecting those two things about the masternode: 1 that it is "NOT REGISTERED" and 2 that it is on "v0.19.01.00." That data leads me to believe the masternode.me site cannot parse the recent versioning scheme change correctly, as that looks very...

protx update_service is the command to un-ban. You would use update_registrar if you wanted to change masternode hosting providers, which as @qwizzie suggests you might want to consider. List of hosting services

The OP is not operating a shared node, which means moocowmoo does not hold his collateral. As long as moowcowmoo updated the MN itself to v19.1.0 and fully synced it, all this person would need to do is issue a protx update_service to un-ban his node. The fact that it says "POSE BANNED" in his...

That most likely means your masternode on the wrong chain. You'll have to do the invalidateblock / reconsider block trick, or more likely a full --reindex. Do a ./dash-cli -getinfo and check which block you're on. It should match the one shown in the Information tab in your wallet that...

As @splawik21 said, it is not worth PoSe ban to save on server cost by using a cheaper low-resource one. Instead of 2GB RAMtry something larger like 6GB, and 3+ CPU cores. Also, your VPS provider might sometimes have down-time, in which case the Dash network will not be able to see it. So use...