Launched mastenodes more than 26 hours ago, in the active list is. Payments not.
If every day is generated 1440 blocks, and masternodes currently 567, then every 9-10 hours, payment must occur.
what's wrong? why so long no payments?
Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 476. (Read 782382 times)
March 21, 2016, 07:01:17 AM
March 21, 2016, 06:43:55 AM
enableobfuscate=0
that will disable it
that will disable it
It works, thanks!
Indeed. In general this function will work OK.
However, IMHO Obfuscation Mixing should remain an optional choice for the user. Some users won't want this feature enabled automatically.
Perhaps this should be put to a MN vote, following 'testing' this in the current release ?
March 21, 2016, 06:38:09 AM
enableobfuscate=0
that will disable it
that will disable it
It works, thanks!
March 21, 2016, 06:37:27 AM
Reporting a potential 'conflict of obfuscation' / Masternode activation issue when users set-up a new Masternode on a 0 balance wallet address, in regards to the v1.0.2.0 release setting: "Enabled Obfuscation by default, the new default is to keep 1000 DNET mixed with 8 rounds."
- If the user is intending to set-up 'One single Local Masternode', receiving the 10,000 Dnet set-up (requirement) from say purchasing coins via an exchange, then the incoming transaction is likely to be met with an Obfuscation transaction fee payment from the balance (before the Masternode is enabled), thus leaving say a 9999.99981844 Dnet balance remaining and causing the user to receive the following unexpected message; "Not capable masternode: Could not find suitable coins!"
Which can ofc be easily resolved by sending just 1 more Dnet to the same address and then making a new transaction of 10,000 Dnet to the same (your own) wallet address to allow for successful Masternode activation.
- If the user is intending to set-up 'One single Local Masternode', receiving the 10,000 Dnet set-up (requirement) from say purchasing coins via an exchange, then the incoming transaction is likely to be met with an Obfuscation transaction fee payment from the balance (before the Masternode is enabled), thus leaving say a 9999.99981844 Dnet balance remaining and causing the user to receive the following unexpected message; "Not capable masternode: Could not find suitable coins!"
Which can ofc be easily resolved by sending just 1 more Dnet to the same address and then making a new transaction of 10,000 Dnet to the same (your own) wallet address to allow for successful Masternode activation.
+1, this is what I meant earlier.
Currently the only workaround is to turn off obfuscation as soon as the wallet starts and hope that you're not late.
It should be disabled by default or at least there should be a switch in the .conf file.
enableobfuscate=0
that will disable it
Yes adding enableobfuscate=0 in the .conf should disable it.
However, in the 'tested' new MN instance, it did not. Hence, why I'm reporting the issue.
March 21, 2016, 06:28:55 AM
Reporting a potential 'conflict of obfuscation' / Masternode activation issue when users set-up a new Masternode on a 0 balance wallet address, in regards to the v1.0.2.0 release setting: "Enabled Obfuscation by default, the new default is to keep 1000 DNET mixed with 8 rounds."
- If the user is intending to set-up 'One single Local Masternode', receiving the 10,000 Dnet set-up (requirement) from say purchasing coins via an exchange, then the incoming transaction is likely to be met with an Obfuscation transaction fee payment from the balance (before the Masternode is enabled), thus leaving say a 9999.99981844 Dnet balance remaining and causing the user to receive the following unexpected message; "Not capable masternode: Could not find suitable coins!"
Which can ofc be easily resolved by sending just 1 more Dnet to the same address and then making a new transaction of 10,000 Dnet to the same (your own) wallet address to allow for successful Masternode activation.
- If the user is intending to set-up 'One single Local Masternode', receiving the 10,000 Dnet set-up (requirement) from say purchasing coins via an exchange, then the incoming transaction is likely to be met with an Obfuscation transaction fee payment from the balance (before the Masternode is enabled), thus leaving say a 9999.99981844 Dnet balance remaining and causing the user to receive the following unexpected message; "Not capable masternode: Could not find suitable coins!"
Which can ofc be easily resolved by sending just 1 more Dnet to the same address and then making a new transaction of 10,000 Dnet to the same (your own) wallet address to allow for successful Masternode activation.
+1, this is what I meant earlier.
Currently the only workaround is to turn off obfuscation as soon as the wallet starts and hope that you're not late.
It should be disabled by default or at least there should be a switch in the .conf file.
enableobfuscate=0
that will disable it
March 21, 2016, 06:26:43 AM
Reporting a potential 'conflict of obfuscation' / Masternode activation issue when users set-up a new Masternode on a 0 balance wallet address, in regards to the v1.0.2.0 release setting: "Enabled Obfuscation by default, the new default is to keep 1000 DNET mixed with 8 rounds."
- If the user is intending to set-up 'One single Local Masternode', receiving the 10,000 Dnet set-up (requirement) from say purchasing coins via an exchange, then the incoming transaction is likely to be met with an Obfuscation transaction fee payment from the balance (before the Masternode is enabled), thus leaving say a 9999.99981844 Dnet balance remaining and causing the user to receive the following unexpected message; "Not capable masternode: Could not find suitable coins!"
Which can ofc be easily resolved by sending just 1 more Dnet to the same address and then making a new transaction of 10,000 Dnet to the same (your own) wallet address to allow for successful Masternode activation.
- If the user is intending to set-up 'One single Local Masternode', receiving the 10,000 Dnet set-up (requirement) from say purchasing coins via an exchange, then the incoming transaction is likely to be met with an Obfuscation transaction fee payment from the balance (before the Masternode is enabled), thus leaving say a 9999.99981844 Dnet balance remaining and causing the user to receive the following unexpected message; "Not capable masternode: Could not find suitable coins!"
Which can ofc be easily resolved by sending just 1 more Dnet to the same address and then making a new transaction of 10,000 Dnet to the same (your own) wallet address to allow for successful Masternode activation.
+1, this is what I meant earlier.
Currently the only workaround is to turn off obfuscation as soon as the wallet starts and hope that you're not late.
It should be disabled by default or at least there should be a switch in the .conf file.
March 21, 2016, 04:45:49 AM
how long to wait for payment from Masternode ?
12 - 24 hours
March 21, 2016, 04:39:02 AM
how long to wait for payment from Masternode ?
March 21, 2016, 04:29:19 AM
Anyone here that can give a hand?
I am having issues with setting up my masternodes usings PJC's VPS.
The servers work fine, its just doing the setup of the wallet I am having issues with.
I have made config files for the nodes but when I do "Masternode outputs" it only shows 1 masternode and not all 4 I made.
Can anyone help me with this?
200 Dnet reward
I am having issues with setting up my masternodes usings PJC's VPS.
The servers work fine, its just doing the setup of the wallet I am having issues with.
I have made config files for the nodes but when I do "Masternode outputs" it only shows 1 masternode and not all 4 I made.
Can anyone help me with this?
200 Dnet reward
link to setup guide in my sig.
March 21, 2016, 04:18:34 AM
Anyone here that can give a hand?
I am having issues with setting up my masternodes usings PJC's VPS.
The servers work fine, its just doing the setup of the wallet I am having issues with.
I have made config files for the nodes but when I do "Masternode outputs" it only shows 1 masternode and not all 4 I made.
Can anyone help me with this?
200 Dnet reward
EDIT:
NVM.. Getting help tomorrow
Thanks though.
I am having issues with setting up my masternodes usings PJC's VPS.
The servers work fine, its just doing the setup of the wallet I am having issues with.
I have made config files for the nodes but when I do "Masternode outputs" it only shows 1 masternode and not all 4 I made.
Can anyone help me with this?
200 Dnet reward
EDIT:
NVM.. Getting help tomorrow
Thanks though.
March 20, 2016, 08:26:03 PM
is this worth mining still?
Yes it is. Best to mine & hold of course.
March 20, 2016, 08:03:33 PM
When if at all will there be an android wallet?
March 20, 2016, 07:57:53 PM
I'm referring to instances on 'One single Local Masternode' where the 10,000 Dnet balance is actually being received to the Masternode capable address.
If this error ccurs on the remote node after upgrading to 1.0.2.0
No. The issue would only potentially apply to the set-up of a new local Masternode on a 0 balance wallet address.
It is not a major issue. Just something that new folks setting up masternodes could be confused by.
The devs will understand what I'm referring to here.
Yes, we understand exactly what you are referring to. While we would prefer that Obfuscation be ran 100% of the time by all users wallets, this option can be disabled if needed.
March 20, 2016, 07:36:44 PM
I'm referring to instances on 'One single Local Masternode' where the 10,000 Dnet balance is actually being received to the Masternode capable address.
If this error ccurs on the remote node after upgrading to 1.0.2.0
No. The issue would only potentially apply to the set-up of a new local Masternode on a 0 balance wallet address.
It is not a major issue. Just something that new folks setting up masternodes could be confused by.
The devs will understand what I'm referring to here.
March 20, 2016, 07:29:37 PM
I'm referring to instances on 'One single Local Masternode' where the 10,000 Dnet balance is actually being received to the Masternode capable address.
If this error ccurs on the remote node after upgrading to 1.0.2.0
March 20, 2016, 07:27:06 PM
Reporting a potential 'conflict of obfuscation' / Masternode activation issue when users set-up a new Masternode on a 0 balance wallet address, in regards to the v1.0.2.0 release setting: "Enabled Obfuscation by default, the new default is to keep 1000 DNET mixed with 8 rounds.".
I solved this issue by deleting everything except the darknet.conf file in the .darknet folder of each remote node
I'm referring to instances on 'One single Local Masternode' where the 10,000 Dnet balance is actually being received to the Masternode capable address.
March 20, 2016, 07:21:18 PM
-if the user is intending to set-up 'One single Local Masternode', receiving the 10,000 Dnet set-up (requirement) from say purchasing coins via an exchange, then the incoming transaction is likely to be met with an Obfuscation transaction fee payment from the balance (before the Masternode is enabled), thus leaving say a 9999.99981844 Dnet balance remaining and causing the user to receive the following unexpected message; "Not capable masternode: Could not find suitable coins!"
I solved this issue by deleting everything except the darknet.conf file in the .darknet folder of each remote node March 20, 2016, 07:19:46 PM
is this worth mining still?
March 20, 2016, 07:04:51 PM
Reporting a potential 'conflict of obfuscation' / Masternode activation issue when users set-up a new Masternode on a 0 balance wallet address, in regards to the v1.0.2.0 release setting: "Enabled Obfuscation by default, the new default is to keep 1000 DNET mixed with 8 rounds."
- If the user is intending to set-up 'One single Local Masternode', receiving the 10,000 Dnet set-up (requirement) from say purchasing coins via an exchange, then the incoming transaction is likely to be met with an Obfuscation transaction fee payment from the balance (before the Masternode is enabled), thus leaving say a 9999.99981844 Dnet balance remaining and causing the user to receive the following unexpected message; "Not capable masternode: Could not find suitable coins!"
Which can ofc be easily resolved by sending just 1 more Dnet to the same address and then making a new transaction of 10,000 Dnet to the same (your own) wallet address to allow for successful Masternode activation.
- If the user is intending to set-up 'One single Local Masternode', receiving the 10,000 Dnet set-up (requirement) from say purchasing coins via an exchange, then the incoming transaction is likely to be met with an Obfuscation transaction fee payment from the balance (before the Masternode is enabled), thus leaving say a 9999.99981844 Dnet balance remaining and causing the user to receive the following unexpected message; "Not capable masternode: Could not find suitable coins!"
Which can ofc be easily resolved by sending just 1 more Dnet to the same address and then making a new transaction of 10,000 Dnet to the same (your own) wallet address to allow for successful Masternode activation.
March 20, 2016, 06:30:53 PM
Edit: Got 1 of 3 using 1.0.2.0 to start locally. No idea why it worked now after failing last 10 goes. Now 2 to go!
Edit2: Now got all 3 started with 1.0.2.0. All I did was follow the guide by BitcoinFX to upgrade. Then started via "start-alias" from controller wallet.
Edit2: Now got all 3 started with 1.0.2.0. All I did was follow the guide by BitcoinFX to upgrade. Then started via "start-alias" from controller wallet.
What do you mean by "start locally"?
I have tried many many many times and it can never start with 1.0.2.0 but starts with no issue for 1.0.1.0, using the same protocol to sync a chain and bring up the node.
I meant by running "masternode start" on each of the VPS.
But I did run "masternode start-alias
(I did both multiple times and kept getting the hot node error before. But trying again later on, it worked. Weird.)
Jump to: