[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 6510.

P2PHash

full member

Activity: 140

Merit: 100

Updated to the new wallet and network! Now with Cryptsy price displayed
Address: drk.p2phash.com

P2Pool benefits:
* No registration required
* Distributed hashrate
* Immediate payouts after a block is found
* Higher payouts with transaction fees paid to miners
* No account hack possible

Fee: only 0.5%
Start mining within seconds! Just point your miner to p2phash.com:7903 and use the Darkcoin address from your wallet for username, the password doesn't matter.

coins101

legendary

Activity: 1456

Merit: 1000

Quote from: ?? on ??

Quote from: n00bnoxious on March 22, 2014, 11:24:42 AM

Quote from: Simcom on March 22, 2014, 11:23:30 AM

www.reddit.com/r/DRKCoin

Subscribe if you haven't already - we should try to move some of this conversation over there, it's way quieter than it should be.

Also I see DarkcoinTalk is a bit of a ghost town. I say we move any non dev-related talk over there. This thread is almost unreadable.

+1

Staying here has the advantage of being easily accessible to others. Moving might be too soon until there are many more supporters.

Perhaps we should split out specific topics, onto new bitcointalk threads, that are on the bounty list and other to do lists and then link from here for updates?

chaeplin

sr. member

Activity: 294

Merit: 250

Quote from: HammerHedd on March 22, 2014, 12:47:40 PM

Quote from: chaeplin on March 22, 2014, 12:26:43 PM

I have fired up a AWS server for testing.

Do you need help with anything? I can push a miner in your direction if you need to test some incoming hashes

Code:

ubuntu@ip-172-31-27-220:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="13.10, Saucy Salamander"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 13.10"
VERSION_ID="13.10"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

ubuntu@ip-172-31-27-220:~$ uname -a
Linux ip-172-31-27-220 3.11.0-15-generic #25-Ubuntu SMP Thu Jan 30 17:22:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@ip-172-31-27-220:~$ darkcoind getmininginfo
{
   "blocks" : 38111,
   "currentblocksize" : 0,
   "currentblocktx" : 0,
   "difficulty" : 276.64209745,
   "errors" : "",
   "generate" : false,
   "genproclimit" : -1,
   "hashespersec" : 0,
   "networkhashps" : 8319203351,
   "pooledtx" : 0,
   "testnet" : false
}

https://github.com/evan82/darkcoin/blob/master/doc/build-unix.md

   2 apt-get update
   3 apt-get install git
   4 apt-get install build-essential
   5 apt-get install libssl-dev
   6 apt-get install libboost-all-dev
   7 apt-get install libdb5.1-dev libdb5.1++-dev
   8 cd /usr/local/src/
   9 ls
   10 git clone https://github.com/evan82/darkcoin.git
   11 cd darkcoin/
   12 ks
   13 history
   14 cd src/
   15 ls
   16 vi makefile.unix
   17 make -f makefile.unix

Code:

ubuntu@ip-172-31-27-220:~$ darkcoind getmininginfo
{
"blocks" : 38113,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 251.76643606,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 8272425203,
"pooledtx" : 10,
"testnet" : false
}

this is my aws 64bit ubuntu 13.10. Yes no problem.

@HammerHedd , please check your os bit again.

HammerHedd

full member

Activity: 168

Merit: 100

If you are mining on or running a P2Pool Node 107.170.124.93:7903 Please check your configuration!

Due to the DGW glitch, you are mining nothing but orphaned shares. Please switch to another node (http://darkcoin.mine.nu/) until the problem can be resolved.

Don't waste the hashes!

HammerHedd

full member

Activity: 168

Merit: 100

Quote from: chaeplin on March 22, 2014, 12:26:43 PM

I have fired up a AWS server for testing.

Do you need help with anything? I can push a miner in your direction if you need to test some incoming hashes

chaeplin

sr. member

Activity: 294

Merit: 250

Quote from: HammerHedd on March 22, 2014, 12:22:52 PM

Quote from: chaeplin on March 22, 2014, 12:17:45 PM

Quote from: HammerHedd on March 22, 2014, 12:05:58 PM

Quote from: eduffield on March 22, 2014, 12:02:35 PM

Quote from: chaeplin on March 22, 2014, 11:50:48 AM

Quote from: eduffield on March 22, 2014, 11:12:29 AM

Quote from: HammerHedd on March 22, 2014, 10:57:31 AM

I'm having a strange issue.. one machine (ubuntu) refuses to update it's wallet. I've deleted literally everything (the darkcoin/ directory and the .darkcoin/ directory) and rebuilt it. As before, it hung on s bunch of orphan blocks from about 6 days ago. So, I deleted and rebuilt everything again, then took everything in the .darkcoin/ directory from a currently working wallet (except wallet.dat) and copied it into the new directory so it would (theoretically) have a decent blockchain to start from and only be a block behind. It found one block, and then stopped communicating with the blockchain.

I can post the debug log if someone wants to help. It has completely screwed my Saturday Sad

I was hoping to have a nice smooth p2pool transition

I just pushed this branch, try it and let me know if that works:

https://github.com/evan82/darkcoin/tree/DGW-32bit-bug

I add printf and here the result.

Code:

2014-03-22 16:48:47 received block 0000000000a138da706d1e79ab9064034578404bd551482bae4840afa6673fad
2014-03-22 16:48:47 nBits: 469805813, GetNextWorkRequired: 469805811
2014-03-22 16:48:47 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 16:48:47 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 16:48:47 Misbehaving: 112.175.123.82:9999 (0 -> 100) DISCONNECTING
2014-03-22 16:48:47 disconnecting node 112.175.123.82

Yeah that's sad, it's definitely a bug with DGW. I can fix it, but it will require everyone update

What is the preferred solution in the short term?

How about try ubuntu 12.0.4 TLS ?
I have no prob.

lol... I switched back to the older computer and she's running fine... I'm going to go work outside and take a break from all this... The node is hashing again, that's what's important. I'll try the upgrade again later after the DGW bug gets sorted.

On the plus side, Evan is usually really fast at this sort of thing, so I'm sure it will be good to go in the very near future.

I have fired up a AWS server for testing.

HammerHedd

full member

Activity: 168

Merit: 100

Quote from: chaeplin on March 22, 2014, 12:17:45 PM

Quote from: HammerHedd on March 22, 2014, 12:05:58 PM

Quote from: eduffield on March 22, 2014, 12:02:35 PM

Quote from: chaeplin on March 22, 2014, 11:50:48 AM

Quote from: eduffield on March 22, 2014, 11:12:29 AM

Quote from: HammerHedd on March 22, 2014, 10:57:31 AM

I'm having a strange issue.. one machine (ubuntu) refuses to update it's wallet. I've deleted literally everything (the darkcoin/ directory and the .darkcoin/ directory) and rebuilt it. As before, it hung on s bunch of orphan blocks from about 6 days ago. So, I deleted and rebuilt everything again, then took everything in the .darkcoin/ directory from a currently working wallet (except wallet.dat) and copied it into the new directory so it would (theoretically) have a decent blockchain to start from and only be a block behind. It found one block, and then stopped communicating with the blockchain.

I can post the debug log if someone wants to help. It has completely screwed my Saturday Sad

I was hoping to have a nice smooth p2pool transition

I just pushed this branch, try it and let me know if that works:

https://github.com/evan82/darkcoin/tree/DGW-32bit-bug

I add printf and here the result.

Code:

2014-03-22 16:48:47 received block 0000000000a138da706d1e79ab9064034578404bd551482bae4840afa6673fad
2014-03-22 16:48:47 nBits: 469805813, GetNextWorkRequired: 469805811
2014-03-22 16:48:47 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 16:48:47 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 16:48:47 Misbehaving: 112.175.123.82:9999 (0 -> 100) DISCONNECTING
2014-03-22 16:48:47 disconnecting node 112.175.123.82

Yeah that's sad, it's definitely a bug with DGW. I can fix it, but it will require everyone update

What is the preferred solution in the short term?

How about try ubuntu 12.0.4 TLS ?
I have no prob.

lol... I switched back to the older computer and she's running fine... I'm going to go work outside and take a break from all this... The node is hashing again, that's what's important. I'll try the upgrade again later after the DGW bug gets sorted.

On the plus side, Evan is usually really fast at this sort of thing, so I'm sure it will be good to go in the very near future.

chaeplin

sr. member

Activity: 294

Merit: 250

Code:

2014-03-22 17:18:08 received block 0000000000a138da706d1e79ab9064034578404bd551482bae4840afa6673fad
2014-03-22 17:18:08 nBits: 469805813, GetNextWorkRequired: 469805811
2014-03-22 17:18:08 n1: 383.341940, n2: 383.359459
2014-03-22 17:18:08 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 17:18:08 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 17:18:08 Misbehaving: 112.175.123.82:9999 (0 -> 100) DISCONNECTING

more log.

chaeplin

sr. member

Activity: 294

Merit: 250

Quote from: HammerHedd on March 22, 2014, 12:05:58 PM

Quote from: eduffield on March 22, 2014, 12:02:35 PM

Quote from: chaeplin on March 22, 2014, 11:50:48 AM

Quote from: eduffield on March 22, 2014, 11:12:29 AM

Quote from: HammerHedd on March 22, 2014, 10:57:31 AM

I'm having a strange issue.. one machine (ubuntu) refuses to update it's wallet. I've deleted literally everything (the darkcoin/ directory and the .darkcoin/ directory) and rebuilt it. As before, it hung on s bunch of orphan blocks from about 6 days ago. So, I deleted and rebuilt everything again, then took everything in the .darkcoin/ directory from a currently working wallet (except wallet.dat) and copied it into the new directory so it would (theoretically) have a decent blockchain to start from and only be a block behind. It found one block, and then stopped communicating with the blockchain.

I can post the debug log if someone wants to help. It has completely screwed my Saturday Sad

I was hoping to have a nice smooth p2pool transition

I just pushed this branch, try it and let me know if that works:

https://github.com/evan82/darkcoin/tree/DGW-32bit-bug

I add printf and here the result.

Code:

2014-03-22 16:48:47 received block 0000000000a138da706d1e79ab9064034578404bd551482bae4840afa6673fad
2014-03-22 16:48:47 nBits: 469805813, GetNextWorkRequired: 469805811
2014-03-22 16:48:47 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 16:48:47 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 16:48:47 Misbehaving: 112.175.123.82:9999 (0 -> 100) DISCONNECTING
2014-03-22 16:48:47 disconnecting node 112.175.123.82

Yeah that's sad, it's definitely a bug with DGW. I can fix it, but it will require everyone update

What is the preferred solution in the short term?

How about try ubuntu 64bit 12.0.4 TLS ?
I have no prob.

HammerHedd

full member

Activity: 168

Merit: 100

Quote from: eduffield on March 22, 2014, 12:02:35 PM

Quote from: chaeplin on March 22, 2014, 11:50:48 AM

Quote from: eduffield on March 22, 2014, 11:12:29 AM

Quote from: HammerHedd on March 22, 2014, 10:57:31 AM

I'm having a strange issue.. one machine (ubuntu) refuses to update it's wallet. I've deleted literally everything (the darkcoin/ directory and the .darkcoin/ directory) and rebuilt it. As before, it hung on s bunch of orphan blocks from about 6 days ago. So, I deleted and rebuilt everything again, then took everything in the .darkcoin/ directory from a currently working wallet (except wallet.dat) and copied it into the new directory so it would (theoretically) have a decent blockchain to start from and only be a block behind. It found one block, and then stopped communicating with the blockchain.

I can post the debug log if someone wants to help. It has completely screwed my Saturday Sad

I was hoping to have a nice smooth p2pool transition

I just pushed this branch, try it and let me know if that works:

https://github.com/evan82/darkcoin/tree/DGW-32bit-bug

I add printf and here the result.

Code:

2014-03-22 16:48:47 received block 0000000000a138da706d1e79ab9064034578404bd551482bae4840afa6673fad
2014-03-22 16:48:47 nBits: 469805813, GetNextWorkRequired: 469805811
2014-03-22 16:48:47 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 16:48:47 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 16:48:47 Misbehaving: 112.175.123.82:9999 (0 -> 100) DISCONNECTING
2014-03-22 16:48:47 disconnecting node 112.175.123.82

Yeah that's sad, it's definitely a bug with DGW. I can fix it, but it will require everyone update

What is the preferred solution in the short term?

tifozi

hero member

Activity: 742

Merit: 501

Evan let us not rush it this time please. I posted a few pages back that DGW will need small updates/fixes. That is why I didn't want other coins to blindly start copying it.

eduffield

legendary

Activity: 1176

Merit: 1036

Dash Developer

Quote from: chaeplin on March 22, 2014, 11:50:48 AM

Quote from: eduffield on March 22, 2014, 11:12:29 AM

Quote from: HammerHedd on March 22, 2014, 10:57:31 AM

I'm having a strange issue.. one machine (ubuntu) refuses to update it's wallet. I've deleted literally everything (the darkcoin/ directory and the .darkcoin/ directory) and rebuilt it. As before, it hung on s bunch of orphan blocks from about 6 days ago. So, I deleted and rebuilt everything again, then took everything in the .darkcoin/ directory from a currently working wallet (except wallet.dat) and copied it into the new directory so it would (theoretically) have a decent blockchain to start from and only be a block behind. It found one block, and then stopped communicating with the blockchain.

I can post the debug log if someone wants to help. It has completely screwed my Saturday Sad

I was hoping to have a nice smooth p2pool transition

I just pushed this branch, try it and let me know if that works:

https://github.com/evan82/darkcoin/tree/DGW-32bit-bug

I add printf and here the result.

Code:

2014-03-22 16:48:47 received block 0000000000a138da706d1e79ab9064034578404bd551482bae4840afa6673fad
2014-03-22 16:48:47 nBits: 469805813, GetNextWorkRequired: 469805811
2014-03-22 16:48:47 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 16:48:47 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 16:48:47 Misbehaving: 112.175.123.82:9999 (0 -> 100) DISCONNECTING
2014-03-22 16:48:47 disconnecting node 112.175.123.82

Yeah that's sad, it's definitely a bug with DGW. I can fix it, but it will require everyone update. PS, try this branch: https://github.com/evan82/darkcoin/tree/DGW-32bit-bug

Just a warning though, if you're submitting blocks with that daemon they'll get rejected if that branch works

HammerHedd

full member

Activity: 168

Merit: 100

Quote from: chaeplin on March 22, 2014, 11:50:48 AM

Quote from: eduffield on March 22, 2014, 11:12:29 AM

Quote from: HammerHedd on March 22, 2014, 10:57:31 AM

I'm having a strange issue.. one machine (ubuntu) refuses to update it's wallet. I've deleted literally everything (the darkcoin/ directory and the .darkcoin/ directory) and rebuilt it. As before, it hung on s bunch of orphan blocks from about 6 days ago. So, I deleted and rebuilt everything again, then took everything in the .darkcoin/ directory from a currently working wallet (except wallet.dat) and copied it into the new directory so it would (theoretically) have a decent blockchain to start from and only be a block behind. It found one block, and then stopped communicating with the blockchain.

I can post the debug log if someone wants to help. It has completely screwed my Saturday Sad

I was hoping to have a nice smooth p2pool transition

I just pushed this branch, try it and let me know if that works:

https://github.com/evan82/darkcoin/tree/DGW-32bit-bug

I add printf and here the result.

Code:

2014-03-22 16:48:47 received block 0000000000a138da706d1e79ab9064034578404bd551482bae4840afa6673fad
2014-03-22 16:48:47 nBits: 469805813, GetNextWorkRequired: 469805811
2014-03-22 16:48:47 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 16:48:47 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 16:48:47 Misbehaving: 112.175.123.82:9999 (0 -> 100) DISCONNECTING
2014-03-22 16:48:47 disconnecting node 112.175.123.82

I see at least one other p2pool node is having the same problem - 5.6% efficiency

I wonder if I can roll the pool back...?

chaeplin

sr. member

Activity: 294

Merit: 250

Quote from: eduffield on March 22, 2014, 11:12:29 AM

Quote from: HammerHedd on March 22, 2014, 10:57:31 AM

I'm having a strange issue.. one machine (ubuntu) refuses to update it's wallet. I've deleted literally everything (the darkcoin/ directory and the .darkcoin/ directory) and rebuilt it. As before, it hung on s bunch of orphan blocks from about 6 days ago. So, I deleted and rebuilt everything again, then took everything in the .darkcoin/ directory from a currently working wallet (except wallet.dat) and copied it into the new directory so it would (theoretically) have a decent blockchain to start from and only be a block behind. It found one block, and then stopped communicating with the blockchain.

I can post the debug log if someone wants to help. It has completely screwed my Saturday Sad

I was hoping to have a nice smooth p2pool transition

I just pushed this branch, try it and let me know if that works:

https://github.com/evan82/darkcoin/tree/DGW-32bit-bug

I add printf and here the result.

Code:

2014-03-22 16:48:47 received block 0000000000a138da706d1e79ab9064034578404bd551482bae4840afa6673fad
2014-03-22 16:48:47 nBits: 469805813, GetNextWorkRequired: 469805811
2014-03-22 16:48:47 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 16:48:47 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 16:48:47 Misbehaving: 112.175.123.82:9999 (0 -> 100) DISCONNECTING
2014-03-22 16:48:47 disconnecting node 112.175.123.82

HammerHedd

full member

Activity: 168

Merit: 100

Quote from: chaeplin on March 22, 2014, 11:02:14 AM

Quote from: HammerHedd on March 22, 2014, 10:57:31 AM

I'm having a strange issue.. one machine (ubuntu) refuses to update it's wallet. I've deleted literally everything (the darkcoin/ directory and the .darkcoin/ directory) and rebuilt it. As before, it hung on s bunch of orphan blocks from about 6 days ago. So, I deleted and rebuilt everything again, then took everything in the .darkcoin/ directory from a currently working wallet (except wallet.dat) and copied it into the new directory so it would (theoretically) have a decent blockchain to start from and only be a block behind. It found one block, and then stopped communicating with the blockchain.

I can post the debug log if someone wants to help. It has completely screwed my Saturday Sad

I was hoping to have a nice smooth p2pool transition

show me the log.
ubuntu 32bit ? 64bit ?

32bit log.

Code:

2014-03-21 05:34:42 received block 0000000000a138da706d1e79ab9064034578404bd551482bae4840afa6673fad
2014-03-21 05:34:42 ERROR: AcceptBlock() : incorrect proof of work
2014-03-21 05:34:42 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-21 05:34:42 Misbehaving: 112.175.123.82:9999 (0 -> 100) DISCONNECTING

112.175.123.82 is 64bit, p2pool asia01.

64 bit ubuntu 13.10

Code:

2014-03-22 16:27:31 ProcessBlock: ACCEPTED
2014-03-22 16:27:31 received block 0000000000dfef8242fd4b9de9ad6edbd4a6cadcce14c5c68470f7fc05c3a5f8
2014-03-22 16:27:31 SetBestChain: new best=0000000000dfef8242fd4b9de9ad6edbd4a6cadcce14c5c68470f7fc05c3a5f8  height=34135  log2_work=53.845554  tx=140284  date=2014-03-15 19:17:58 progress=0.956234
2014-03-22 16:27:31 ProcessBlock: ACCEPTED
2014-03-22 16:27:31 received block 0000000000603d3a3ba622728747991e9752ecd59836e0667757c9d06143b7da
2014-03-22 16:27:31 SetBestChain: new best=0000000000603d3a3ba622728747991e9752ecd59836e0667757c9d06143b7da  height=34136  log2_work=53.845661  tx=140289  date=2014-03-15 19:23:05 progress=0.956257
2014-03-22 16:27:31 ProcessBlock: ACCEPTED
2014-03-22 16:27:31 received block 00000000004d129cf4fa6c885c1db87ef09d0e14d72fe76ef02d9e4c7cc55099
2014-03-22 16:27:31 SetBestChain: new best=00000000004d129cf4fa6c885c1db87ef09d0e14d72fe76ef02d9e4c7cc55099  height=34137  log2_work=53.845768  tx=140290  date=2014-03-15 19:23:48 progress=0.956261
2014-03-22 16:27:31 ProcessBlock: ACCEPTED
2014-03-22 16:27:31 received block 00000000007bb41ae78eff7bd8456b2526f542f8904439a20d4a291756d1e9d5
2014-03-22 16:27:31 SetBestChain: new best=00000000007bb41ae78eff7bd8456b2526f542f8904439a20d4a291756d1e9d5  height=34138  log2_work=53.845875  tx=140295  date=2014-03-15 19:26:08 progress=0.956272
2014-03-22 16:27:31 ProcessBlock: ACCEPTED
2014-03-22 16:27:31 received block 0000000000048df5a5abb1c3b8f58ab4f7415240f0ba253c51ba59a46fd98d10
2014-03-22 16:27:31 SetBestChain: new best=0000000000048df5a5abb1c3b8f58ab4f7415240f0ba253c51ba59a46fd98d10  height=34139  log2_work=53.845982  tx=140299  date=2014-03-15 19:28:04 progress=0.956282
2014-03-22 16:27:31 ProcessBlock: ACCEPTED
2014-03-22 16:27:31 received block 00000000007dda6b77dc0575cca14aecdc36cbdb07afe364d55e8def556304c2
2014-03-22 16:27:31 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 16:27:31 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 16:27:31 Misbehaving: 50.19.116.123:9999 (0 -> 100) DISCONNECTING
2014-03-22 16:27:31 disconnecting node 50.19.116.123:9999
2014-03-22 16:27:32 received block 0000000000d5e8652582bb526edb6a389366d8f818b30ea7acd9b5f08cbb41d1
2014-03-22 16:27:32 ProcessBlock: ORPHAN BLOCK, prev=000000000067e933f90bb757838c00fda8159d10a7485a1debc09cc2c522b4d8
2014-03-22 16:27:32 received block 00000000005f093fd0bf34bd7acc3d93bc3e0aa218985ee8c8d2bcbd9da834d4
2014-03-22 16:27:32 ProcessBlock: ORPHAN BLOCK, prev=0000000000d5e8652582bb526edb6a389366d8f818b30ea7acd9b5f08cbb41d1
2014-03-22 16:27:32 received block 0000000001441f1afc554412b0907e2367286aaa50e91169655647e4d18b67e7
2014-03-22 16:27:32 ProcessBlock: ORPHAN BLOCK, prev=00000000005f093fd0bf34bd7acc3d93bc3e0aa218985ee8c8d2bcbd9da834d4
2014-03-22 16:27:32 received block 0000000000058355b5902e435fccd8201e46a05ea325d44876a718e4b40cd93f
2014-03-22 16:27:32 ProcessBlock: ORPHAN BLOCK, prev=0000000001441f1afc554412b0907e2367286aaa50e91169655647e4d18b67e7
2014-03-22 16:27:32 received block 00000000009ea909a8d75a1a4ee69b799a26de225cff25db2a0a4f9034ba1446
2014-03-22 16:27:32 ProcessBlock: ORPHAN BLOCK, prev=0000000000058355b5902e435fccd8201e46a05ea325d44876a718e4b40cd93f
2014-03-22 16:27:32 received block 0000000000a9740c198a6c5875e796e5868cdbae0d6627809173b27ad5d53fea
2014-03-22 16:27:32 ProcessBlock: ORPHAN BLOCK, prev=00000000009ea909a8d75a1a4ee69b799a26de225cff25db2a0a4f9034ba1446
2014-03-22 16:27:32 received block 00000000016dc84f5ce90ca15cdeeb38d6bce4f584d155c7d5e830fae1c49fcf
2014-03-22 16:27:32 ProcessBlock: ORPHAN BLOCK, prev=0000000000a9740c198a6c5875e796e5868cdbae0d6627809173b27ad5d53fea
2014-03-22 16:27:32 received block 0000000000b85487da3625431772067524ca01dc73e9c391e6b0b66ac210417a
2014-03-22 16:27:32 ProcessBlock: ORPHAN BLOCK, prev=00000000016dc84f5ce90ca15cdeeb38d6bce4f584d155c7d5e830fae1c49fcf
2014-03-22 16:27:32 received block 0000000000adc1a3dc8896e5adf0fae1186c99406e9e2b8967dbb33cdeeb4559
2014-03-22 16:27:32 ProcessBlock: ORPHAN BLOCK, prev=0000000000b85487da3625431772067524ca01dc73e9c391e6b0b66ac210417a
2014-03-22 16:27:32 received block 0000000000b95c0cdfceec1aa9755b214cdf1b71288b7f730c695b668a6f2eb2

I can drop the whole thing in pastebin if that will help. I almost think it has to do with the recent change in block rewards (7% reduction) and I somehow am building a version that is conflicting with... something...

chaeplin

sr. member

Activity: 294

Merit: 250

Quote from: eduffield on March 22, 2014, 11:12:29 AM

Quote from: HammerHedd on March 22, 2014, 10:57:31 AM

I'm having a strange issue.. one machine (ubuntu) refuses to update it's wallet. I've deleted literally everything (the darkcoin/ directory and the .darkcoin/ directory) and rebuilt it. As before, it hung on s bunch of orphan blocks from about 6 days ago. So, I deleted and rebuilt everything again, then took everything in the .darkcoin/ directory from a currently working wallet (except wallet.dat) and copied it into the new directory so it would (theoretically) have a decent blockchain to start from and only be a block behind. It found one block, and then stopped communicating with the blockchain.

I can post the debug log if someone wants to help. It has completely screwed my Saturday Sad

I was hoping to have a nice smooth p2pool transition

I just pushed this branch, try it and let me know if that works:

https://github.com/evan82/darkcoin/tree/DGW-32bit-bug

patched, remove obj/, compiling, little slow.

n00bnoxious

sr. member

Activity: 280

Merit: 250

Bitnation Development Team Member

Quote from: Simcom on March 22, 2014, 11:23:30 AM

www.reddit.com/r/DRKCoin

Subscribe if you haven't already - we should try to move some of this conversation over there, it's way quieter than it should be.

Also I see DarkcoinTalk is a bit of a ghost town. I say we move any non dev-related talk over there. This thread is almost unreadable.

Simcom

sr. member

Activity: 336

Merit: 250

www.reddit.com/r/DRKCoin

Subscribe if you haven't already - we should try to move some of this conversation over there, it's way quieter than it should be.

chaeplin

sr. member

Activity: 294

Merit: 250

Quote from: eduffield on March 22, 2014, 11:12:29 AM

Quote from: HammerHedd on March 22, 2014, 10:57:31 AM

I'm having a strange issue.. one machine (ubuntu) refuses to update it's wallet. I've deleted literally everything (the darkcoin/ directory and the .darkcoin/ directory) and rebuilt it. As before, it hung on s bunch of orphan blocks from about 6 days ago. So, I deleted and rebuilt everything again, then took everything in the .darkcoin/ directory from a currently working wallet (except wallet.dat) and copied it into the new directory so it would (theoretically) have a decent blockchain to start from and only be a block behind. It found one block, and then stopped communicating with the blockchain.

I can post the debug log if someone wants to help. It has completely screwed my Saturday Sad

I was hoping to have a nice smooth p2pool transition

I just pushed this branch, try it and let me know if that works:

https://github.com/evan82/darkcoin/tree/DGW-32bit-bug

still..

Code:

2014-03-22 16:25:34 received block 0000000000a138da706d1e79ab9064034578404bd551482bae4840afa6673fad
2014-03-22 16:25:34 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 16:25:34 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 16:25:34 Misbehaving: 112.175.123.94:9999 (0 -> 100) DISCONNECTING
2014-03-22 16:25:34 disconnecting node 112.175.123.94


        // Check proof of work
        //if (nBits != GetNextWorkRequired(pindexPrev, this))

         double n1 = ConvertBitsToDouble(nBits);
         double n2 = ConvertBitsToDouble(GetNextWorkRequired(pindexPrev, this));
         if ((int)(n1*100) != (int)(n2*100))
            return state.DoS(100, error("AcceptBlock() : incorrect proof of work"));


user@monitoring:~> darkcoind --help
DarkCoin version v0.9.0.0-g07c9905-beta

n00bnoxious

sr. member

Activity: 280

Merit: 250

Bitnation Development Team Member

Quote from: godzirra on March 22, 2014, 11:11:23 AM

Quote from: n00bnoxious on March 22, 2014, 09:57:22 AM

Quote from: anonymousxx1503 on March 22, 2014, 09:42:27 AM

Quote from: Coin-Moron on March 22, 2014, 09:05:37 AM

The activity of the bot in cryptsy is declining.
I guess the whale had indeed mined enough for the long run.
Don't try for cheap trades fellas.
You might regret.

Well Cryptsy just did the opposite of what everyone (including the darkcoin devs) asked them to do for Darkcoin. They decreased minimum order size which will allow the bot to save money while lowering our price artifically! Good job Cryptsy!

https://twitter.com/cryptsy/status/447243624880021504

Yeah I spotted that - first they say they won't do anything to help then they go and do something to actively hurt the coin? Maybe the whale *is* Craptsy ;-)

That was my thought all week. When will another exchange take them out already! We need to get on btc-e.

I agree, but I do think we need all features out of beta first. If people adopt the coin before it's ready, there will be huge losses in one way or another...

Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 6510. (Read 9723858 times)