Updatemasternode - Revision history

Kassius84 at 17:18, 29 December 2022

2022-12-29T17:18:39Z

Stonygan at 07:47, 23 December 2022

2022-12-23T07:47:52Z

Stonygan at 07:55, 8 December 2022

2022-12-08T07:55:22Z

Jochen2000: Added getmininginfo image to get Masternode-ID

2022-12-06T08:26:59Z

Added getmininginfo image to get Masternode-ID

Jochen2000 at 07:53, 6 December 2022

2022-12-06T07:53:18Z

Jochen2000 at 07:50, 6 December 2022

2022-12-06T07:50:13Z

Jochen2000 at 07:48, 6 December 2022

2022-12-06T07:48:28Z

Stonygan at 14:18, 2 December 2022

2022-12-02T14:18:18Z

Stonygan at 13:37, 2 December 2022

2022-12-02T13:37:27Z

Stonygan at 13:36, 2 December 2022

2022-12-02T13:36:28Z

← Older revision		Revision as of 17:18, 29 December 2022
Line 1:		Line 1:
−	'''Updatemasternode'''	+	== '''Updatemasternode''' ==
−
	With V3 of the DeFiChain-Node from December 2022 many new features included.		With V3 of the DeFiChain-Node from December 2022 many new features included.

@@ Line 59: / Line 59: @@
 <u>Mainnet:</u>
-updatemasternode Rewardaddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''1008''' blocks
+updatemasternode Rewardaddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''2016''' blocks
 updatemasternode Operatoraddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''2016''' blocks
 updatemasternode Owneraddress: Switch in State ''TRANSFERRING'', ''PRE-ENABLED'' after 2016 blocks, ''ENABLED'' after 1008 blocks = '''3024''' blocks (~24h)

@@ Line 25: / Line 25: @@
 Change multiple addresses:<syntaxhighlight lang="bash">
 updatemasternode "EnteryourMasternodeID" {"operatorAddress":"EnterNewOperatoraddress","rewardAddress":"EnterNewRewardaddress"}
 </syntaxhighlight>
 Be aware, when you redirect your Rewards to a Exchange like Bittrex or Kucoin or another Smart Contract (e.g. CAKE), make sure beforehand that the service supports this redirection. Masternoderewards are created directly from the blockchain and are initially in "immature" status for 99 blocks and cannot be used. Exchanges often use smart contracts to assign incoming transactions to your Exchange Wallet via a batch command; this is not possible in this case.

@@ Line 8: / Line 8: @@
 You need your MasternodeID to use this Command. The MasternodeID is your TransactionID from the creation of your Masternode. You can find the ID in the Desktop Wallet when you click the Tab Masternodes, select your Masternode and check the last line named ''Hash''.
-[[File:MasternodeID.png|center]]
+[[File:MasternodeID.png|center]]When you have access to the operator wallet you can find the MasternodeID using the command ''getmininginfo'':
 <u>The commands for the desktop wallet:</u>

@@ Line 22: / Line 22: @@
 </syntaxhighlight>
 Change multiple addresses:<syntaxhighlight lang="bash">
-updatemasternode "EnteryourMasternodeID" {"operatorAddress":"EnterNewOperarotaddress","rewardAddress":"EnterNewRewardaddress"}
+updatemasternode "EnteryourMasternodeID" {"operatorAddress":"EnterNewOperatoraddress","rewardAddress":"EnterNewRewardaddress"}
 </syntaxhighlight>
 Be aware, when you redirect your Rewards to a Exchange like Bittrex or Kucoin or another Smart Contract (e.g. CAKE), make sure beforehand that the service supports this redirection. Masternoderewards are created directly from the blockchain and are initially in "immature" status for 99 blocks and cannot be used. Exchanges often use smart contracts to assign incoming transactions to your Exchange Wallet via a batch command; this is not possible in this case.

@@ Line 4: / Line 4: @@
 The updatemasternode command can be used to change an existing Masternode. The Owneraddress (the address with 20K DFI Colateral), Operatoraddress and the Rewardaddress can be changed.
-You may change only one address or multiple addresses at the same time. The time in TRANSFERRING state is only applied once no matter how many addresses are changed. Therefore it helps to reduce non-generating time for a masternode by changing all addresses in one step.
+You may change one address or multiple addresses at the same time. The time in TRANSFERRING state is only applied once no matter how many addresses are changed. Therefore it helps to reduce non-generating time for a masternode by changing all addresses in one step.
 Please note that only those addresses are to be specified in the command that need to be changed. Those addresses that should be kept are not to be mentioned.
@@ Line 14: / Line 14: @@
 Change Owneraddress:<syntaxhighlight lang="bash">
 updatemasternode "EnteryourMasternodeID" {"ownerAddress":"EnterNewOwneraddress"}
-</syntaxhighlight>Change the Operatoraddress:<syntaxhighlight lang="bash">
+</syntaxhighlight>
 updatemasternode "EnteryourMasternodeID" {"operatorAddress":"EnterNewOperatoraddress"}
-</syntaxhighlight>Change or set a Rewardaddress:<syntaxhighlight lang="bash">
+</syntaxhighlight>
 updatemasternode "EnteryourMasternodeID" {"rewardAddress":"EnterNewRewardaddress"}
-</syntaxhighlight>Be aware, when you redirect your Rewards to a Exchange like Bittrex or Kucoin or another Smart Contract (e.g. CAKE), make sure beforehand that the service supports this redirection. Masternoderewards are created directly from the blockchain and are initially in "immature" status for 99 blocks and cannot be used. Exchanges often use smart contracts to assign incoming transactions to your Exchange Wallet via a batch command; this is not possible in this case.
+</syntaxhighlight>
 Redirecting to your LightWallet can also be problematic, if your rewards go there directly to your main address, you can't make a transaction there for 99 blocks. If you run a Vault, this can be a problem under certain circumstances, if you have to react quickly. Optimally, you set up a new DFI address on the LightWallet that you use only for your masternoderewards.

@@ Line 3: / Line 3: @@
 With V3 of the DeFiChain-Node from December 2022 many new features included.
-The updatemasternode command can be used to change an existing Masternode. The Owneraddress (the address with 20K DFI Colateral), Operatoraddress and the Rewardaddress can be changed. Please note that only one value can be changed per command. If you want to create a new Owneraddress and a new Operatoraddress, the ''updatemasternode'' command must be used twice.
+The updatemasternode command can be used to change an existing Masternode. The Owneraddress (the address with 20K DFI Colateral), Operatoraddress and the Rewardaddress can be changed.
 You need your MasternodeID to use this Command. The MasternodeID is your TransactionID from the creation of your Masternode. You can find the ID in the Desktop Wallet when you click the Tab Masternodes, select your Masternode and check the last line named ''Hash''.
@@ Line 12: / Line 14: @@
 Change Owneraddress:<syntaxhighlight lang="bash">
 updatemasternode "EnteryourMasternodeID" {"ownerAddress":"EnterNewOwneraddress"}
-</syntaxhighlight>Changing the Operatoraddress:<syntaxhighlight lang="bash">
+</syntaxhighlight>Change the Operatoraddress:<syntaxhighlight lang="bash">
 updatemasternode "EnteryourMasternodeID" {"operatorAddress":"EnterNewOperatoraddress"}
 </syntaxhighlight>Change or set a Rewardaddress:<syntaxhighlight lang="bash">
@@ Line 18: / Line 20: @@
 </syntaxhighlight>Be aware, when you redirect your Rewards to a Exchange like Bittrex or Kucoin or another Smart Contract (e.g. CAKE), make sure beforehand that the service supports this redirection. Masternoderewards are created directly from the blockchain and are initially in "immature" status for 99 blocks and cannot be used. Exchanges often use smart contracts to assign incoming transactions to your Exchange Wallet via a batch command; this is not possible in this case.
-Redirecting to your LightWallet can also be problematic, if your rewards go there directly to your main address, you can't make a transaction there for 99 blocks. If you run a Vault, this can be a problem under certain circumstances, if you have to react quickly. Optimally, you set up a new DFI address on the LighWallet that you use only for your masternoderewards.
+Redirecting to your LightWallet can also be problematic, if your rewards go there directly to your main address, you can't make a transaction there for 99 blocks. If you run a Vault, this can be a problem under certain circumstances, if you have to react quickly. Optimally, you set up a new DFI address on the LightWallet that you use only for your masternoderewards.
@@ Line 28: / Line 30: @@
 updatemasternode Rewardaddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''60''' blocks
-updatemasternode operatoraddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''60''' blocks
+updatemasternode Operatoraddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''60''' blocks
-updatemaster Owneraddress: Switch in State ''TRANSFERING'', ''PRE-ENABLED'' after 60 blocks, ''ENABLED'' after 10 blocks = '''70''' blocks
+updatemasternode Owneraddress: Switch in State ''TRANSFERRING'', ''PRE-ENABLED'' after 60 blocks, ''ENABLED'' after 10 blocks = '''70''' blocks
 <u>Mainnet:</u>
@@ Line 36: / Line 38: @@
 updatemasternode Rewardaddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''1008''' blocks
-updatemasternode operatoraddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''2016''' blocks
+updatemasternode Operatoraddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''2016''' blocks
-updatemaster Owneraddress: Switch in State ''TRANSFERING'', ''PRE-ENABLED'' after 2016 blocks, ''ENABLED'' after 1008 blocks = '''3024''' blocks (~24h)
+updatemasternode Owneraddress: Switch in State ''TRANSFERRING'', ''PRE-ENABLED'' after 2016 blocks, ''ENABLED'' after 1008 blocks = '''3024''' blocks (~24h)

@@ Line 28: / Line 28: @@
 updatemasternode Rewardaddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''60''' blocks
-Target Multipliers do net reset.
+''Target Multipliers do net reset.''
 updatemasternode operatoraddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''60''' blocks
-Target Multipliers do net reset.
+''Target Multipliers do net reset.''
 updatemaster Owneraddress: Switch in State ''TRANSFERING'', ''PRE-ENABLED'' after 60 blocks, ''ENABLED'' after 10 blocks = '''70''' blocks
-All Target Multipliers reset to 1.
+'''''All Target Multipliers reset to 1.'''''
 <u>Mainnet:</u>
@@ Line 42: / Line 42: @@
 updatemasternode Rewardaddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''1008''' blocks
-Target Multipliers do net reset.
+''Target Multipliers do net reset.''
 updatemasternode operatoraddress: Switch in State ''TRANSFERRING'', ''ENABLED'' after '''2016''' blocks
-Target Multipliers do net reset.
+''Target Multipliers do net reset.''
 updatemaster Owneraddress: Switch in State ''TRANSFERING'', ''PRE-ENABLED'' after 2016 blocks, ''ENABLED'' after 1008 blocks = '''3024''' blocks (~24h)
-All Target Multipliers reset to 1.
+'''''All Target Multipliers reset to 1.'''''