Author

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

full member
Activity: 165
Merit: 100
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.
sr. member
Activity: 686
Merit: 251
full member
Activity: 165
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?
legendary
Activity: 1078
Merit: 1011
I have connections, some of them to 2.1.2.1 wallets and some of them to 2.1.2.2 wallets. Is this correct?

And when you have time, devs, could you give a little explanation of what obfuscation is and how it works for dummies?
Thanks

Yes, it's okay to connect to both versions.

As for obfuscation, I think it was explained before but I'm still trying to find it. Here's one I found though.
https://bitcointalksearch.org/topic/m.16041350

Obfuscation is a service that uses the masternodes to mix your Dnet with others who also enable Obfuscation to obscure the origins of the original coins. 2 - 4 rounds provides decent mixing, while 8 rounds gets you to the point that someone would have to be pretty damned determined to trace out the entire string of transactions from all the pieces of all the monetized segments of the coins you have chosen to mix. Don't get me wrong, it is still traceable if you are determined, but very difficult presently.

When you enable this function, you can go into your coin control, and see how the lot of DNET has been broken up into certain sized segments, these will be traded many times with others also running Obfuscation, making it very difficult to trace as all the inputs/outputs will be the same monetary size.
legendary
Activity: 1078
Merit: 1011
Ok, Everyone, Sorry for the Delay.. Smiley I would Like to Keep Pushing forward getting DarkNet added to CoinPayments, and Our Giveaway. As we need to make a slight change to the rules involving posting information here on BCT as they say it violates their rules of conduct. So Please continue Tweeting the information as originally requested, and PM me the tx information or you can email it to me 's3v3nh4cks @ gmail'

So to recap the rules;

- each vote placed for DarkNet (DNET) to get added to Coinpayments.net is equal to 1 vote, vote as many times as you like and as often as you like. This giveaway ends when DarkNet is added to CoinPayments.

- PM or email me your BCT username and TX ID (DO NOT POST IT HERE)


PRIZE is a Stakebox with the DarkNet wallet preinstalled and 10K DNET ready to run a Masternode (or) Stake. (Dnet will be sent by me once you provide me your DNET address after the end of the Giveaway and the TX ID will be posted for all to verify)

To kick things off, I Will match any vote that is Placed between now and the end of 9/11 (Without registering for the giveaway of course). I will tally up the votes based on the dates of the TX ID's and submit my matching votes on 9/12

Thanks to everyone who have brought us this far, lets see this to completion. I estimate we need around 815 total votes.

https://www.coinpayments.net/vote

s3v3n
legendary
Activity: 1638
Merit: 1011
jakiman is back!
I have connections, some of them to 2.1.2.1 wallets and some of them to 2.1.2.2 wallets. Is this correct?

And when you have time, devs, could you give a little explanation of what obfuscation is and how it works for dummies?
Thanks

Yes, it's okay to connect to both versions.

As for obfuscation, I think it was explained before but I'm still trying to find it. Here's one I found though.
https://bitcointalksearch.org/topic/m.16041350
legendary
Activity: 1638
Merit: 1011
jakiman is back!
If everything checks out, try stopping the masternode's wallet, then restart it again.
I had the same issue and that resolved it. Seems it wasn't just updating its status.
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

Have you double checked that the genkey and IP addresses match in the masternode.conf and both are fully sync'd?

Of course, masternode.conf file has not been changed in my controller wallet and the same for darknet.conf in my MN's. And ./darknet-cli getinfo gives me the same block in controller wallet and MN's, same as http://178.254.23.111/~pub/DN/DN_Info.html.

hero member
Activity: 525
Merit: 500
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

Have you double checked that the genkey and IP addresses match in the masternode.conf and both are fully sync'd?
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
hero member
Activity: 727
Merit: 501
I have connections, some of them to 2.1.2.1 wallets and some of them to 2.1.2.2 wallets. Is this correct?

And when you have time, devs, could you give a little explanation of what obfuscation is and how it works for dummies?

Thanks
hero member
Activity: 525
Merit: 500
I am not getting any connections on the v2.1.2.2 wallet.  I need to re-sync the blockchain after an error, I added connect=coin-server.com to the darknet.conf but am still not getting any connections, any ideas?


Same here. When I use files from the previous wallet, I get connections quickly, but the chain doesn't sync.
hero member
Activity: 727
Merit: 501
Need more people to turn on Obfuscation, minimum of 500 DNET for 2 rounds Please....
Started here as you asked. Some questions:

I need to do anything more than change ofuscation amount and rounds and push the button?

Why the button doesn't look like a button? Tongue

Where is the option to stop the anoying sound that happens everytime a transaction happens? I REALLY need it...  Undecided
sr. member
Activity: 448
Merit: 250
I am not getting any connections on the v2.1.2.2 wallet.  I need to re-sync the blockchain after an error, I added connect=coin-server.com to the darknet.conf but am still not getting any connections, any ideas?
hero member
Activity: 525
Merit: 500
Need more people to turn on Obfuscation, minimum of 500 DNET for 2 rounds Please....


I'll do it as soon as my new wallet gets some connections. 30 min and still 0 active connections.
full member
Activity: 236
Merit: 100
Need more people to turn on Obfuscation, minimum of 500 DNET for 2 rounds Please....

how to /Mac ?
i am set for 2 rounds - 500
but when i press 'start mix' nothing happens
legendary
Activity: 1078
Merit: 1011
Need more people to turn on Obfuscation, minimum of 500 DNET for 2 rounds Please....
hero member
Activity: 525
Merit: 500
legendary
Activity: 1638
Merit: 1011
jakiman is back!
DEV UPDATE

Mandatory v2.1.2.2 wallet update has been released today by Stakebox that has fixed some core bugs and include many frontend improvements.

https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.1.2.2

Change Log
- Incorrect math for the max budget, the block rewards, and the seesaw mechanism were corrected.
- Issue with masternode payment enforcement has been addressed.
- Unconfirmed staking and masternode rewards will no longer be shown in coin control.
- Masternode rewards will be marked as such in the transactions tab, and will no longer show as confirmed prematurely.
- Staking and masternode rewards will also show in the immature row on the main overview page of the wallet.
- Transactions sent using Obfuscation were showing as Darksent in the transactions page before, they will show as Obfuscated now.
- 2 new RPC calls created. setstakesplitthreshold & getstakesplitthreshold. This will allow people to experiment with stake split sizes.
- Few other minor changes to the Qt

As with any wallet upgrades, please backup first then test with 1 or few of your wallets and masternodes first before upgrading all wallets.

For those who missed it. I've also tweeted it. Should follow me if you want up to date DNET news. Cool
https://twitter.com/jakimanboy/status/773736110518337540
Jump to: