Author

Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 330. (Read 782375 times)

full member
Activity: 236
Merit: 100
Same here. Installed new wallet from scratch. Won't download the chain.
same here on the mac version


no problems here on mac
(Mixing and Staking)

you cleared out your Library DNet folder before the new version ?
(Download everything from scratch)
legendary
Activity: 1778
Merit: 1003
NodeMasters
Same here. Installed new wallet from scratch. Won't download the chain.
same here on the mac version
sr. member
Activity: 471
Merit: 250
Same here. Installed new wallet from scratch. Won't download the chain.
full member
Activity: 168
Merit: 100
New wallet is stuck...  :/ wont update sigh...
hero member
Activity: 727
Merit: 501
I have already updated my controller wallet and my MN's to v2.1.2.2, but when I try to restart the masternodes I receive the correct message of:

Quote
{
    "alias" : "BMN3",
    "result" : "successful"
}

And when I go to my MN and type

Quote
./darknet-cli masternode status

I receive this message

Quote
{
    "vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
    "service" : "[::]:0",
    "status" : "Not capable masternode: Hot node, waiting for remote activation."
}

Any thoughts???

EDIT: And when I ask for masternode list-conf in my MN's controller wallet all of them appear as ENABLED. Huh


I restarted my wallet/controller with the new version first. Maybe 30 minutes later, restarted the some masternodes with the new version.

The stayed in the same state. (Not capable masternode: Hot node, waiting for remote activation.) for about an hour so I ran start-alias ... from the controller and then the state changed.

Information from the wallet/controller is based on information is has last received from the masternode... and I think that after it doesn't hear from the masternode after a certain amount of time, then the masternode changes to the Missing state.
Did like you said and the result is the same, only change is that now my MN's has a value on "vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )", diferent to 00000....
I have activated obfuscation, can be related with it, devs? darknet.conf and masternodes.conf are ok in the controller wallet, only coin-server.com as node and correct Privkeys and associated collateral, and the same in the MN's, each ip has its asociated privkeys. But they don't change from the waiting remote activation state, nor with start-alias [MN alias] neither with masternode start-all.

I have also stop and start a mn as jakiman said and it didn't worked. After work I will try to resync again from scratch and start them again to see if that solved the problem. Any idea, suggestion is welcome. Anyone with similar problems or I am the original guy? Sad

Solved, I have resync from scratch (but after solving the problem I think it was no necessary) and I have done two things. The least important I think is to add "addnode=coin-server.com" to the darknet.conf file, that has no nodes since the blockchain problems in version v2.0.x. And more important, I have started the wallet, wait for sync, stopped the wallet, WAIT FOR A MINUTE, and started it again. I thinks that when I have stopped the wallet in the first attempts I tried to restart it again too fast, and the stopping action make something that allow the MN to be activated. I will inform again as soon as I have the first payments.
Thanks, Jakiman, your indication gives me a clue that my problem could be there.

On the other hand I have obfuscation completed at 93%, what happens when it reach 100%?

I have the impression I'm stacking blocks faster since I have obfuscation activated.

And as we approachh firsr block reward decrease in POS phase price seems to go up. Smiley
legendary
Activity: 1148
Merit: 1001

my test masternodes with version 2.1.2.2 are now up and running without any issues for 24 hrs.
will upgrade the rest today

What's date for having everyone's on new version?

i guess we don't know yet
hero member
Activity: 728
Merit: 500

my test masternodes with version 2.1.2.2 are now up and running without any issues for 24 hrs.
will upgrade the rest today

What's date for having everyone's on new version?
legendary
Activity: 1148
Merit: 1001

my test masternodes with version 2.1.2.2 are now up and running without any issues for 24 hrs.
will upgrade the rest today
hero member
Activity: 727
Merit: 501
I have already updated my controller wallet and my MN's to v2.1.2.2, but when I try to restart the masternodes I receive the correct message of:

Quote
{
    "alias" : "BMN3",
    "result" : "successful"
}

And when I go to my MN and type

Quote
./darknet-cli masternode status

I receive this message

Quote
{
    "vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
    "service" : "[::]:0",
    "status" : "Not capable masternode: Hot node, waiting for remote activation."
}

Any thoughts???

EDIT: And when I ask for masternode list-conf in my MN's controller wallet all of them appear as ENABLED. Huh


I restarted my wallet/controller with the new version first. Maybe 30 minutes later, restarted the some masternodes with the new version.

The stayed in the same state. (Not capable masternode: Hot node, waiting for remote activation.) for about an hour so I ran start-alias ... from the controller and then the state changed.

Information from the wallet/controller is based on information is has last received from the masternode... and I think that after it doesn't hear from the masternode after a certain amount of time, then the masternode changes to the Missing state.
Did like you said and the result is the same, only change is that now my MN's has a value on "vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )", diferent to 00000....
I have activated obfuscation, can be related with it, devs? darknet.conf and masternodes.conf are ok in the controller wallet, only coin-server.com as node and correct Privkeys and associated collaterals, and the same in the MN's, each ip has its asociated privkeys. But they don't change from the waiting remote activation state, nor with start-alias [MN alias] neither with masternode start-all.

I have also stop and start a mn as jakiman said and it didn't worked. After work I will try to resync again from scratch and start them again to see if that solved the problem. Any idea, suggestion is welcome. Anyone with similar problems or I am the original guy? Sad
legendary
Activity: 1638
Merit: 1011
jakiman is back!
Thanks for taking the time to help.  Smiley

http://pastebin.com/rGJesuiJ

Hmm. I personally don't see any problems in that log file.

In Settings-Options-Network, do you have Map port using UPnP & allow incoming connections checked? (SOCKS5 can be left unchecked)
full member
Activity: 274
Merit: 122
I have removed all the data in the darknet folder and even deleted all firewall rules and started fresh but still cannot get the wallet to download the blockchain in Win64.  Connections appear for a split second and then dissapear again in the peers window.

Anyone worked out a solution yet?

There isnt anything wrong with the wallet.  Please post the contents of your log file to pastebin and link it here.

Thanks

Thanks for taking the time to help.  Smiley

http://pastebin.com/rGJesuiJ

You may need to paste it again after letting the wallet run a bit.  I didnt see where you had addnode=coin-server.com.  Actually I dont see it trying to connect at all.  Keep it open for a bit and then paste the log again.
sr. member
Activity: 448
Merit: 250
I have removed all the data in the darknet folder and even deleted all firewall rules and started fresh but still cannot get the wallet to download the blockchain in Win64.  Connections appear for a split second and then dissapear again in the peers window.

Anyone worked out a solution yet?

There isnt anything wrong with the wallet.  Please post the contents of your log file to pastebin and link it here.

Thanks

Thanks for taking the time to help.  Smiley

http://pastebin.com/rGJesuiJ
full member
Activity: 274
Merit: 122
I have removed all the data in the darknet folder and even deleted all firewall rules and started fresh but still cannot get the wallet to download the blockchain in Win64.  Connections appear for a split second and then dissapear again in the peers window.

Anyone worked out a solution yet?

There isnt anything wrong with the wallet.  Please post the contents of your log file to pastebin and link it here.

Thanks
sr. member
Activity: 448
Merit: 250
I have removed all the data in the darknet folder and even deleted all firewall rules and started fresh but still cannot get the wallet to download the blockchain in Win64.  Connections appear for a split second and then dissapear again in the peers window.

Anyone worked out a solution yet?
legendary
Activity: 1078
Merit: 1011
Need more people to turn on Obfuscation, minimum of 500 DNET for 2 rounds Please....

Maybe a bit more explanation if non-default setting are needed and if restarting is needed.

I would like to... I guess it is not so simple....

Looking at the help in the cli...

darknet-cli help obfuscation
obfuscation
darknetaddress, reset, or auto (AutoDenominate) is a real and will be rounded to the next 0.1


The help for darknetd says talks about "automated obfuscation",

 -enableobfuscation=          Enable use of automated obfuscation for funds stored in this wallet (0-1, default: 0)

So I would guess that one could manually enable obfuscate some  coins from the CLI without any change or restart... but no...

$ darknet-cli obfuscation Dabc123abc123abc123zzzzzzzzzz 500
error: {"code":-1,"message":"value is type str, expected real"}


Am I doing something wrong?


if you are trying to run the Obfuscation purely from the daemon file, you need to add certain entries into your darknet.conf file. for example;

enableobfuscation=1
obfuscationrounds=2
anonymizedarknetamount=500

you will need to restart the daemon for these settings to take effect. (Also after changing them)

tx that's what i was looking for
works - the usual Idl - waiting in queue - too recent  so far

Edit:
so i can stake and mix at the same time ?

yes, I am doing the same thing
full member
Activity: 236
Merit: 100
Need more people to turn on Obfuscation, minimum of 500 DNET for 2 rounds Please....

Maybe a bit more explanation if non-default setting are needed and if restarting is needed.

I would like to... I guess it is not so simple....

Looking at the help in the cli...

darknet-cli help obfuscation
obfuscation
darknetaddress, reset, or auto (AutoDenominate) is a real and will be rounded to the next 0.1


The help for darknetd says talks about "automated obfuscation",

 -enableobfuscation=          Enable use of automated obfuscation for funds stored in this wallet (0-1, default: 0)

So I would guess that one could manually enable obfuscate some  coins from the CLI without any change or restart... but no...

$ darknet-cli obfuscation Dabc123abc123abc123zzzzzzzzzz 500
error: {"code":-1,"message":"value is type str, expected real"}


Am I doing something wrong?


if you are trying to run the Obfuscation purely from the daemon file, you need to add certain entries into your darknet.conf file. for example;

enableobfuscation=1
obfuscationrounds=2
anonymizedarknetamount=500

you will need to restart the daemon for these settings to take effect. (Also after changing them)

tx that's what i was looking for
works - the usual Idl - waiting in queue - too recent  so far

Edit:
so i can stake and mix at the same time ?
legendary
Activity: 1078
Merit: 1011
I had to recreate these budgets which were already approved, but were mistakenly deleted from the nodes. Please revote.

original Post bitcointalk.org/index.php?topic=1262920.msg15244032#msg15244032

I just created a proposal to cover the cost of github private repos so the Dev's can all have their own personal private repo to work from. the cost is not that significant, but it should be covered by the project.

Please vote yes,

Thanks

"mnbudget vote-many c391f4930d61ac49609d1dc62e0f5e180a6b32fcebc1cd8d72846800b3cd9509 yes" to vote in favor

"mnbudget vote-many c391f4930d61ac49609d1dc62e0f5e180a6b32fcebc1cd8d72846800b3cd9509 no" to vote against

"mnbudget getinfo github-repo-fees” to check the status

**********

Original Post bitcointalk.org/index.php?topic=1262920.msg15703921#msg15703921

Proposal to setup Public-Awareness Program through Jakiman;

"mnbudget vote-many 884085394e31a5e6e1a87ffb554ee9aa843c93be6f81674b281045d3adce3602 yes" to vote in favor

"mnbudget vote-many 884085394e31a5e6e1a87ffb554ee9aa843c93be6f81674b281045d3adce3602 no" to vote against

"mnbudget getinfo public-awareness” to check the status
legendary
Activity: 1078
Merit: 1011
@nyteo please pm or email me that info and delete your post. You can't post that info here.
legendary
Activity: 1078
Merit: 1011
Need more people to turn on Obfuscation, minimum of 500 DNET for 2 rounds Please....

Maybe a bit more explanation if non-default setting are needed and if restarting is needed.

I would like to... I guess it is not so simple....

Looking at the help in the cli...

darknet-cli help obfuscation
obfuscation
darknetaddress, reset, or auto (AutoDenominate) is a real and will be rounded to the next 0.1


The help for darknetd says talks about "automated obfuscation",

 -enableobfuscation=          Enable use of automated obfuscation for funds stored in this wallet (0-1, default: 0)

So I would guess that one could manually enable obfuscate some  coins from the CLI without any change or restart... but no...

$ darknet-cli obfuscation Dabc123abc123abc123zzzzzzzzzz 500
error: {"code":-1,"message":"value is type str, expected real"}


Am I doing something wrong?


if you are trying to run the Obfuscation purely from the daemon file, you need to add certain entries into your darknet.conf file. for example;

enableobfuscation=1
obfuscationrounds=2
anonymizedarknetamount=500

you will need to restart the daemon for these settings to take effect. (Also after changing them)
Jump to: