Bitcoin Forum
May 25, 2019, 02:45:34 PM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Poll
Question: .
.
.

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 ... 527 »
  Print  
Author Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN  (Read 731696 times)
s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1064
Merit: 1010


View Profile
February 14, 2016, 11:13:27 PM
 #381

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
1558795534
Hero Member
*
Offline Offline

Posts: 1558795534

View Profile Personal Message (Offline)

Ignore
1558795534
Reply with quote  #2

1558795534
Report to moderator
PLAY OVER 3000 GAMES
LIGHTNING FAST WITHDRAWALS
PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1558795534
Hero Member
*
Offline Offline

Posts: 1558795534

View Profile Personal Message (Offline)

Ignore
1558795534
Reply with quote  #2

1558795534
Report to moderator
1558795534
Hero Member
*
Offline Offline

Posts: 1558795534

View Profile Personal Message (Offline)

Ignore
1558795534
Reply with quote  #2

1558795534
Report to moderator
jk9694
Full Member
***
Offline Offline

Activity: 275
Merit: 122


View Profile
February 14, 2016, 11:36:45 PM
 #382

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

ocminer
Legendary
*
Offline Offline

Activity: 2366
Merit: 1233



View Profile WWW
February 15, 2016, 12:10:06 AM
 #383

Everything looks good again.

suprnova pools - reliable mining pools - #suprnova on freenet
https://www.suprnova.cc - FOLLOW us @ Twitter ! twitter.com/SuprnovaPools
s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1064
Merit: 1010


View Profile
February 15, 2016, 12:19:57 AM
Last edit: February 15, 2016, 01:13:37 AM by s3v3nh4cks
 #384

Thanks OC!!

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

Thanks!!
jk9694
Full Member
***
Offline Offline

Activity: 275
Merit: 122


View Profile
February 15, 2016, 02:03:22 AM
 #385

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
Copper Member
Legendary
*
Offline Offline

Activity: 1162
Merit: 1025



View Profile
February 15, 2016, 02:31:45 AM
 #386

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
Legendary
*
Offline Offline

Activity: 1134
Merit: 1000


jakiman is back!


View Profile
February 15, 2016, 03:18:32 AM
Last edit: February 15, 2016, 03:33:09 AM by jakiman
 #387

Seems my controller wallet was on a different fork to my masternodes?  Huh
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.

s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1064
Merit: 1010


View Profile
February 15, 2016, 03:29:06 AM
 #388

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
Copper Member
Legendary
*
Offline Offline

Activity: 1162
Merit: 1025



View Profile
February 15, 2016, 04:15:36 AM
 #389

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
Legendary
*
Offline Offline

Activity: 1134
Merit: 1000


jakiman is back!


View Profile
February 15, 2016, 04:27:09 AM
 #390

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.

s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1064
Merit: 1010


View Profile
February 15, 2016, 04:35:25 AM
 #391

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
Copper Member
Legendary
*
Offline Offline

Activity: 1162
Merit: 1025



View Profile
February 15, 2016, 04:46:15 AM
 #392

Cool, no big deal man, glad you guys got it sorted fast.
jakiman
Legendary
*
Offline Offline

Activity: 1134
Merit: 1000


jakiman is back!


View Profile
February 15, 2016, 04:51:52 AM
 #393

Is the block explorer up to date?

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

s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1064
Merit: 1010


View Profile
February 15, 2016, 04:58:53 AM
 #394

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
Legendary
*
Offline Offline

Activity: 1134
Merit: 1000


jakiman is back!


View Profile
February 15, 2016, 05:22:57 AM
 #395

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)


s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1064
Merit: 1010


View Profile
February 15, 2016, 05:25:31 AM
 #396

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
Legendary
*
Offline Offline

Activity: 1022
Merit: 1001


Syscoin- Changing the way people do business.


View Profile WWW
February 15, 2016, 05:35:04 AM
 #397

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?  Undecided

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

Syscoin: Business on the Blockchain. - Buy and sell goods and services, send encrypted messages and more all secured by the blockchain.
Syscoin Website | Syscoin Whitepaper | Syscoin Team Price Peg
bathrobehero
Legendary
*
Offline Offline

Activity: 1694
Merit: 1027


ICO? Not even once.


View Profile
February 15, 2016, 03:00:20 PM
 #398

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?

RIP Bittrex
RIP Poloniex
incognitoworker
Hero Member
*****
Offline Offline

Activity: 736
Merit: 500


View Profile
February 15, 2016, 03:18:29 PM
 #399

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

Quotient- Closed loop economy enviroment experiment
https://bitcointalk.org/index.php?topic=1195335.0
tylerderden
Copper Member
Legendary
*
Offline Offline

Activity: 1162
Merit: 1025



View Profile
February 15, 2016, 03:53:39 PM
 #400

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
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 ... 527 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!