[ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN

[4x13]

OK guys, I need everyone to turn on their wallet solo-mining just incase

Please everyone add gen=1 to your darknet.conf file. it will help keeping the hash decentralized so this doesn't happen again.


The issue was caused by too much hash being on one pool, and that pool went down. so the blockchain stalled. Stakebox and Myself have put some hash at several of the pools for the next few days to keep it going.

Sorry for the issues..

KEEP MINING!! Please

[1713970090]

1713970090

[1713970090]

1713970090

[1713970090]

1713970090

[jk9694]

Coin-Server is back up again.  We are watching the backend to make sure the wallet doesn't get banned again.

[ocminer]

Everything looks good again.

[4x13]

Thanks OC!!

Everyone needs to do a masternode start-all as your masternodes expired while the chain stalled..

Thanks!!

[jk9694]

Coin-Server is still down, the network ban is still in place.  We will be offline with the pool and the explorer and the public nodes for the next 24 hours.

Sorry for the inconvenience...

[tylerderden]

Yep lost connection to the network and a couple thousand coins in the process on that deal. I'll point one of my cards to a pool if it keeps that from happening again.

[jakiman]

Seems my controller wallet was on a different fork to my masternodes?  
I'm only using the nodes list in the OP in my darknet.conf file. Hmm.

My masternodes matches the block number of the block explorer.
But the controller wallet had a much higher block #. (about 100 more)
Tried rescan but still same. So I'm trying to sync up from scratch now.

Update: Still same. Hmm. I seem to sync from only node 173.245.148.70 in the OP list in the beginning.

[4x13]

Yep lost connection to the network and a couple thousand coins in the process on that deal. I'll point one of my cards to a pool if it keeps that from happening again.

couple thousand coins how?

[tylerderden]

Yep lost connection to the network and a couple thousand coins in the process on that deal. I'll point one of my cards to a pool if it keeps that from happening again.

couple thousand coins how?

I'm not sure, they were payments from my masternode. I noticed I had 0 connections to the network so I restarted my wallet and masternode, about 25% stayed the rest are gone, no longer in the transaction list or anything. Fork maybe? Not sure what happened exactly.

Am I the only one that shows the obfuscation stuff disabled on this latest wallet?

[jakiman]

I'm not sure, they were payments from my masternode. I noticed I had 0 connections to the network so I restarted my wallet and masternode, about 25% stayed the rest are gone, no longer in the transaction list or anything. Fork maybe? Not sure what happened exactly.

Am I the only one that shows the obfuscation stuff disabled on this latest wallet?

I had the same issue. I had a few masternode payments that came in and some even confirmed but now they all disappeared.

[4x13]

There were some blocks, after the blockchain started moving again, that were orphaned until everyone restarted their master node and the network caught back up. everything seems to be moving along fine now

[tylerderden]

Cool, no big deal man, glad you guys got it sorted fast.

[jakiman]

Is the block explorer up to date?

http://darknetexplorer.coin-server.com/

[4x13]

the issue stemmed from the Pool/blockexplorer was banned for some reason (We are researching the specific reason) but essentially had a misbehaving masternode at the same IP as the pool/blockexplorer. So the network banned his IP, so his wallet connected with a few other iP's that were also banned and created their own little temp network where the blocks were all 250 DNET because their little network did not have any masternodes on it to trigger the 20%/80% split that the reward does on the correct network. but those of use who were mining that pool, got orphans because when the pool handed out the 250 DNET blocks only to the miner, then Network enforced the Reward rules and Orphaned those blocks.

Until We figure out why his IP was banned other than a misbehaving Master node, it is important that people follow the rules of 1 public IP per masternode or the network will ban your IP and any wallet that is also attached to that banned IP which is what ended up happening.

So no, the Block Explorer is not up to date at the moment, it should be back online tomorrow sometime. Sorry Guys..

[jakiman]

Ah. Thanks for the explanation.

I got my controller & master nodes all in sync and all having same block numbers now. (20888 at time of writing)

[4x13]

yeah, I consider it growing pains until the network can grow to a more stable size. Thanks for sticking with us. The network is real fragile in the beginning

[danosphere]

Try the darknet-qt in src/qt.
Add the nodes from op. My win wallet didn't need the addnodes, the linux one didn't connect without.

Thank trying to do this but need to build from source to get that darknet-qt to show up in src/qt... tried building from source and got this error/output stream:

Code:

Making all in src
make[1]: Entering directory `/root/Darknet/src'
make[2]: Entering directory `/root/Darknet/src'
  CXX      libbitcoinconsensus_la-allocators.lo
  CXX      primitives/libbitcoinconsensus_la-transaction.lo
  CXX      crypto/libbitcoinconsensus_la-hmac_sha512.lo
  CXX      crypto/libbitcoinconsensus_la-sha1.lo
  CXX      crypto/libbitcoinconsensus_la-sha256.lo
  CXX      crypto/libbitcoinconsensus_la-sha512.lo
  CXX      crypto/libbitcoinconsensus_la-ripemd160.lo
  CXX      libbitcoinconsensus_la-eccryptoverify.lo
  CXX      libbitcoinconsensus_la-ecwrapper.lo
  CXX      libbitcoinconsensus_la-hash.lo
  CXX      libbitcoinconsensus_la-pubkey.lo
  CXX      script/libbitcoinconsensus_la-script.lo
  CXX      script/libbitcoinconsensus_la-interpreter.lo
  CXX      script/libbitcoinconsensus_la-bitcoinconsensus.lo
  CXX      libbitcoinconsensus_la-uint256.lo
  CXX      libbitcoinconsensus_la-utilstrencodings.lo
  CXXLD    libbitcoinconsensus.la
  CXX      darknetd-darknetd.o
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[2]: *** [darknetd-darknetd.o] Error 4
make[2]: Leaving directory `/root/Darknet/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/Darknet/src'
make: *** [all-recursive] Error 1

Any ideas?  

How much RAM do you have available? I usually see "g++: internal compiler error: Killed (program cc1plus)" compiling on Raspberry Pi with too many cores and I run out of RAM.

I think it might be this, let me try upping the ram and giving it another go

[bathrobehero]

the issue stemmed from the Pool/blockexplorer was banned for some reason (We are researching the specific reason) but essentially had a misbehaving masternode at the same IP as the pool/blockexplorer. So the network banned his IP, so his wallet connected with a few other iP's that were also banned and created their own little temp network where the blocks were all 250 DNET because their little network did not have any masternodes on it to trigger the 20%/80% split that the reward does on the correct network. but those of use who were mining that pool, got orphans because when the pool handed out the 250 DNET blocks only to the miner, then Network enforced the Reward rules and Orphaned those blocks.

Until We figure out why his IP was banned other than a misbehaving Master node, it is important that people follow the rules of 1 public IP per masternode or the network will ban your IP and any wallet that is also attached to that banned IP which is what ended up happening.

So no, the Block Explorer is not up to date at the moment, it should be back online tomorrow sometime. Sorry Guys..

Theoritical question: if I know the IP address of a masternode that is not mine and start my own masternode with his address as my masternodeaddr, does it mean I can ban both him and myself?

[incognitoworker]

the issue stemmed from the Pool/blockexplorer was banned for some reason (We are researching the specific reason) but essentially had a misbehaving masternode at the same IP as the pool/blockexplorer. So the network banned his IP, so his wallet connected with a few other iP's that were also banned and created their own little temp network where the blocks were all 250 DNET because their little network did not have any masternodes on it to trigger the 20%/80% split that the reward does on the correct network. but those of use who were mining that pool, got orphans because when the pool handed out the 250 DNET blocks only to the miner, then Network enforced the Reward rules and Orphaned those blocks.

Until We figure out why his IP was banned other than a misbehaving Master node, it is important that people follow the rules of 1 public IP per masternode or the network will ban your IP and any wallet that is also attached to that banned IP which is what ended up happening.

So no, the Block Explorer is not up to date at the moment, it should be back online tomorrow sometime. Sorry Guys..

Theoritical question: if I know the IP address of a masternode that is not mine and start my own masternode with his address as my masternodeaddr, does it mean I can ban both him and myself?

I would say no, you would also need the masternode privkey to get it banned i think.
Masternodeadr is where to look for ip, while masternodeprivkey is the actual wallet?

IW

[tylerderden]

the issue stemmed from the Pool/blockexplorer was banned for some reason (We are researching the specific reason) but essentially had a misbehaving masternode at the same IP as the pool/blockexplorer. So the network banned his IP, so his wallet connected with a few other iP's that were also banned and created their own little temp network where the blocks were all 250 DNET because their little network did not have any masternodes on it to trigger the 20%/80% split that the reward does on the correct network. but those of use who were mining that pool, got orphans because when the pool handed out the 250 DNET blocks only to the miner, then Network enforced the Reward rules and Orphaned those blocks.

Until We figure out why his IP was banned other than a misbehaving Master node, it is important that people follow the rules of 1 public IP per masternode or the network will ban your IP and any wallet that is also attached to that banned IP which is what ended up happening.

So no, the Block Explorer is not up to date at the moment, it should be back online tomorrow sometime. Sorry Guys..

Theoritical question: if I know the IP address of a masternode that is not mine and start my own masternode with his address as my masternodeaddr, does it mean I can ban both him and myself?

Don't ban me bro lol