PSA: You need control of your Payment key in order to get paid on Platform

[xkcd]

Dear eMNOs,

This is a public service announcement to let you know that you need control of your masternode payment key in order to get paid on Platform. This means in case you are currently running a evonode where the payout address is the exchange deposit address, you will be locked out of Platform rewards. Please refer to this guide https://www.dash.org/forum/index.php?threads/how-to-create-the-perfect-masternode.52717/ on how to optimally setup your masternode. In case you need to change your payment key, you may do so using the protx update_registrar invocation on your Dash QT and punching in a new address from your wallet, this will not impact your position in the payment queue. Precise details on how to claim and withdraw your evo rewards will be available prior to the activation of the withdrawals feature on platform.

Please note, this applies only to eMNOs, regular MNs are not impacted, however, strongly encouraged to follow best practices all the same.

Cheers,

XkAI.

 

[qwizzie]

Are you talking about not being able to withdrawal credits for dash or are you talking about not receiving / accumulating any credits on Platform, when you don't have control over your Evonode payout address ? And what if the Evonode payout is an address on a hardware wallet ? Its under user direct control, so no problem ?

 

[xkcd]

Are you talking about not being able to withdrawal credits for dash or are you talking about not receiving / accumulating any credits on Platform, when you don't have control over your Evonode payout address ? And what if the Evonode payout is an address on a hardware wallet ? Its under user direct control, so no problem ?

The credits will still accumulate even if you don't have control of the address, but you would not be able to withdraw them to Dash when the time comes to do so. In the case you have the payment address on HW wallet, you would still need to produce the private key to remove the credits from platform. The exact mechanism of how to do this is unknown to me because withdrawals are not working on testnet. I would strongly advise people sort this out ahead of time to avoid potential issues/edge cases where things don't work because they messed up their keys.

 

[qwizzie]

@xkcd : In the case of having more then 1 Evonode could you use 1 identity across multiple Evonodes, build up credits through that specific identity and rely on at least 1 active Evonode to withdrawal those credits to dash ?

That way even if an Evonode gets disbanded (maybe due to withdrawals taking longer then expected), it will not affect the accumulated Platform credits so far (particularly the accumulated credits of the disbanded Evonode).

Another way i guess would be to use multiple identities (a different identity for each Evonode) and if an Evonode gets disbanded, switch identity on at least one active Evonode to get to the credits balance of that disbanded Evonode and initiate a withdrawal. It would be kinda like switching wallets inside a Dash Core wallet.

 

[xkcd]

@xkcd : In the case of having more then 1 Evonode could you use 1 identity across multiple Evonodes, build up credits through that specific identity and rely on at least 1 active Evonode to withdrawal those credits to dash ?

That way even if an Evonode gets disbanded (maybe due to withdrawals taking longer then expected), it will not affect the accumulated Platform credits so far (particularly the accumulated credits of the disbanded Evonode).

Another way i guess would be to use multiple identities (a different identity for each Evonode) and if an Evonode gets disbanded, switch identity on at least one active Evonode to get to the credits balance of that disbanded Evonode and initiate a withdrawal. It would be kinda like switching wallets inside a Dash Core wallet.

These are the mysteries that we don't have good answers to at the moment because we cannot test these scenarios on testnet. What I would do in this case is set BOTH eMNs to the SAME payout address and then when you can do a withdraw for both using the one address. What the actual mechanics are to post a withdrawal to Platform, I have no idea. I don't know if you need to also create an Identity or if the system automatically does this on your behalf from the payment address or nodeKey. That said, I would imagine there would be no loss of rewards in the case you ran a eMN for a partial Epoch and took it down and then used an 'expired' payment key to try and withdraw the rewards, I am sure such a scenario would be catered for.

 

[thephez]

Masternode identities are created automatically by the system based on info from the Core deterministic masternode list. The payout on the platform side always goes to the same address as on the core side. My understanding is that currently the credit withdraw state transition would have to be signed by the private key. Then platform would create the actual asset unlock transaction releasing the locked Dash on the Core chain. But it's unknown when hardware wallet support for signing the state transition might be available, so using an address from Core for payouts is probably the prudent approach.

 

[qwizzie]

Masternode identities are created automatically by the system based on info from the Core deterministic masternode list. The payout on the platform side always goes to the same address as on the core side. My understanding is that currently the credit withdraw state transition would have to be signed by the private key. Then platform would create the actual asset unlock transaction releasing the locked Dash on the Core chain. But it's unknown when hardware wallet support for signing the state transition might be available, so using an address from Core for payouts is probably the prudent approach.

When can we expect feature Withdrawals to be available for public testing on Testnet ? Bertrand256 need to test this feature on Testnet in order to make the necessary changes (if technically possible) for Dash Masternode Tool (DMT).

cc : @Bertrand256

With both the DIP describing the Credits system (including withdrawals) not yet released to the public and withdrawals itself not open for public testing on Testnet, third party developers like Bertrand256 (DMT) & 32teeth & rango (Dash Central) that DCG expect to provide support for Platform or that have shown an interest to support Platform / Evonodes, are getting hamstringed right now.

Why do i get the feeling both the release of the DIP and any public testing of Withdrawals on Testnet will only get available after Withdrawals gets enabled on Mainnet ? (so well after activation of Platform on Mainnet)

My understanding is that currently the credit withdraw state transition would have to be signed by the private key. Then platform would create the actual asset unlock transaction releasing the locked Dash on the Core chain. But it's unknown when hardware wallet support for signing the state transition might be available, so using an address from Core for payouts is probably the prudent approach

I assume it does not matter if the Core address for payouts is from a Dash Core HD wallet or from a Dash Core non-HD wallet (with the old backups system) ? Both type of Core wallet addresses (for Windows / Mac desktop users !!) should work, right ?

 

[thephez]

When can we expect feature Withdrawals to be available for public testing on Testnet ? Bertrand256 need to test this feature on Testnet in order to make the necessary changes (if technically possible) for Dash Masternode Tool (DMT).

Why do i get the feeling both the release of the DIP and any public testing of Withdrawals on Testnet will only get available after Withdrawals gets enabled on Mainnet ? (so well after activation of Platform on Mainnet)

I am not sure of specific timing, but I recall Sam mentioned withdrawals on a recent YouTube update. He indicated he wanted to review that code/process thoroughly and that it would be happening after the accelerated release. I cannot imagine a scenario where such a critical feature is not tested on both devnets and testnet prior to going to mainnet. If the DIPs are not ready to be published prior to withdrawals being enabled, we should be able to either make draft versions available or put out an "integration guide" with specific details necessary those developers would need to know.

I assume it does not matter if the Core address for payouts is from a Dash Core HD wallet or from a Dash Core non-HD wallet (with the old backups system) ? Both type of Core wallet addresses (for Windows / Mac desktop users !!) should work, right ?

Correct, it does not matter. There is nothing that distinguishes an address from an HD wallet vs one from a non-HD wallet.