Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS

[Jamesco]

Hey guys,

I was wondering if anyone knows where I can find some higher quality Cap images? I am looking for the latest logo but can't seem to find a nice png/jpeg anywhere.

Edit: Specifically the 1c Digital Cap Logo.

[eBit]

Hi all!

I see we are having some trouble with Cryptsy. I am here to help.. If someone from their team needs assistance please PM me.

I personally did have a bit of issues when I got back.  First I started up my wallet after a few weeks of being idle, and I finished sycning but I didn't get the thumbs up. Seems I got stuck on a bad fork( .28 diff) . When I finally hit a few other peers I went through a big orphan catchup.

So I removed peers.dat and blkindex.dat and then re-download blocks from peers. All went well I got caught up to Friday ( 3 days ago) in about 3 hours. Then I when through a few massive re-orgs. I shut down the client and restarted it. I did get up to the right chain.  I am getting checkpoints and I am in sync with http://cap.cryptocoinexplorer.com/

So still going through some growing pains. I think a good feature to add(reminder for later) would be to sort peers.dat by last known good connection and begin recursively iterating backward through them.

I had the same problem. Came back to the wallet after a week and it was stuck on a certain block. I followed the same steps you did, and now after 12 hours of syncing I'm up to date on a chain about 5k blocks shorter than the one here: http://cap.cryptocoinexplorer.com/

Are you still synced up correctly?  Can you post the peers which are getting you there?


The difficulty is up almost 10x since last night on this chain, so someone's mining this.
"difficulty" : 2.31820584,

[presstab]

Hey guys,

I was wondering if anyone knows where I can find some higher quality Cap images? I am looking for the latest logo but can't seem to find a nice png/jpeg anywhere.

Edit: Specifically the 1c Digital Cap Logo.

All of the icons are stored here https://github.com/Tranz5/bottlecaps/tree/master/src/qt/res/icons

This seems the highest quality https://raw.githubusercontent.com/Tranz5/bottlecaps/master/src/qt/res/icons/BottleCaps-128.png

[David Latapie]

For those of you who, like me, have PHS and CAP and TEK and HBN, I suggest the following:
Vote for the highest ranking of them and this one only. Once it will be on the market, then we can get rid of cryptsy for this one (I still have PHS and CAP locked at Cryptsy).. Then focus all your votes on the next one.

That way, deliveries will happen faster.

[zeewolf]

I'm voting for HBN-CAP-TEK-PHS-OFF as often as i can (Each user can only vote for 5 coins per hour at the most).

I don't see how voting for only 1 coin could help it hit the market sooner (if you could vote 5x for one coin then yes, it would be a good idea).

Regarding CAP blockchain stuck - yeah - I was struggling with synchronization few days ago and finally succeeded, but today I'm stuck again. Some (many) peers are on fork (low diff) and somehow client favorizes them and once you connect to any of them you get stuck. Even if you set couple of static (on right chain) peers later it won't help. Client reorganizes blockchain all over again and won't move forward. It's serious problem guys. I don't want to redownload blockchain for the 5th time...

Edit: I resynced from scratch - http://mrfile.me/0z8fae8ysqks/BottleCaps_16062014_block_799195.7z.html - in case if someone have a problem - up to date blockchain and 4 fixed peers in .conf on correct chain.

[Jamesco]

Hey guys,

I was wondering if anyone knows where I can find some higher quality Cap images? I am looking for the latest logo but can't seem to find a nice png/jpeg anywhere.

Edit: Specifically the 1c Digital Cap Logo.

All of the icons are stored here https://github.com/Tranz5/bottlecaps/tree/master/src/qt/res/icons

This seems the highest quality https://raw.githubusercontent.com/Tranz5/bottlecaps/master/src/qt/res/icons/BottleCaps-128.png

Thanks for the link, unfortunately its still not quite the resolution I was looking for. Thanks for the help anyway

[breakbeater]

Hope cryptsy can get Bottlecaps online as this becoming annoying, i don't think it takes a week to get back a wallet online!

Well, i'm waiting for more than 40 days for my PHS withdrawal and i didn't get any response to my tickets. You are very optimistic if you think that CRAPTSY can resolve your issue in one week.

[Tranz]

Hi all!

I see we are having some trouble with Cryptsy. I am here to help.. If someone from their team needs assistance please PM me.

I personally did have a bit of issues when I got back.  First I started up my wallet after a few weeks of being idle, and I finished sycning but I didn't get the thumbs up. Seems I got stuck on a bad fork( .28 diff) . When I finally hit a few other peers I went through a big orphan catchup.

So I removed peers.dat and blkindex.dat and then re-download blocks from peers. All went well I got caught up to Friday ( 3 days ago) in about 3 hours. Then I when through a few massive re-orgs. I shut down the client and restarted it. I did get up to the right chain.  I am getting checkpoints and I am in sync with http://cap.cryptocoinexplorer.com/

So still going through some growing pains. I think a good feature to add(reminder for later) would be to sort peers.dat by last known good connection and begin recursively iterating backward through them.

I had the same problem. Came back to the wallet after a week and it was stuck on a certain block. I followed the same steps you did, and now after 12 hours of syncing I'm up to date on a chain about 5k blocks shorter than the one here: http://cap.cryptocoinexplorer.com/

Are you still synced up correctly?  Can you post the peers which are getting you there?


The difficulty is up almost 10x since last night on this chain, so someone's mining this.
"difficulty" : 2.31820584,

Yes I am still on the correct fork. did you also remove peers.dat?

Since older versions will not work with 2.0. I am going to issue an update to remove them..

So far I just have a few peers that appear stuck and are requesting the same blocks again and again.  But I have a strong 16 connections and on the right block.

[eBit]

Hi all!

I see we are having some trouble with Cryptsy. I am here to help.. If someone from their team needs assistance please PM me.

I personally did have a bit of issues when I got back.  First I started up my wallet after a few weeks of being idle, and I finished sycning but I didn't get the thumbs up. Seems I got stuck on a bad fork( .28 diff) . When I finally hit a few other peers I went through a big orphan catchup.

So I removed peers.dat and blkindex.dat and then re-download blocks from peers. All went well I got caught up to Friday ( 3 days ago) in about 3 hours. Then I when through a few massive re-orgs. I shut down the client and restarted it. I did get up to the right chain.  I am getting checkpoints and I am in sync with http://cap.cryptocoinexplorer.com/

So still going through some growing pains. I think a good feature to add(reminder for later) would be to sort peers.dat by last known good connection and begin recursively iterating backward through them.

I had the same problem. Came back to the wallet after a week and it was stuck on a certain block. I followed the same steps you did, and now after 12 hours of syncing I'm up to date on a chain about 5k blocks shorter than the one here: http://cap.cryptocoinexplorer.com/

Are you still synced up correctly?  Can you post the peers which are getting you there?


The difficulty is up almost 10x since last night on this chain, so someone's mining this.
"difficulty" : 2.31820584,

Yes I am still on the correct fork. did you also remove peers.dat?

Since older versions will not work with 2.0. I am going to issue an update to remove them..

So far I just have a few peers that appear stuck and are requesting the same blocks again and again.  But I have a strong 16 connections and on the right block.

I removed peers.dat multiple times.  I'm on v2.0.  Since I last opened the client there are 450 new blocks on this chain, but it seems stuck now.  Here's a snippet of my log file:



6/16/2014 22:49:39 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 22:49:39 ERROR: Reorganize() : ConnectBlock 000000000dc4e8984c03 failed
6/16/2014 22:49:39 InvalidChainFound: invalid block=000000000cd9c182c4fd  height=498988  trust=2002830707593  date=6/16/2014 17:11:56
6/16/2014 22:49:39 InvalidChainFound:  current best=00000000533bb533712f  height=493344  trust=2002511460146  date=6/16/2014 15:35:01
6/16/2014 22:49:39 ERROR: SetBestChain() : Reorganize failed
6/16/2014 22:49:39 ERROR: AcceptBlock() : AddToBlockIndex failed
6/16/2014 22:49:39 ERROR: ProcessBlock() : AcceptBlock FAILED
6/16/2014 22:49:39 received block 00000000104b394a2654
6/16/2014 22:49:39 Postponing 399 reconnects
6/16/2014 22:49:39 REORGANIZE
6/16/2014 22:49:39 REORGANIZE: Disconnect 1433 blocks; 000000000dd458745575..00000000533bb533712f
6/16/2014 22:49:39 REORGANIZE: Connect 6679 blocks; 000000000dd458745575..d9a6e62459d7a48767d7
6/16/2014 22:49:42 connection timeout
6/16/2014 22:49:42 trying connection 86.130.245.53:7685 lastseen=166.6hrs
6/16/2014 22:49:43 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 22:49:43 ERROR: Reorganize() : ConnectBlock 000000000dc4e8984c03 failed
6/16/2014 22:49:44 InvalidChainFound: invalid block=00000000104b394a2654  height=498989  trust=2002830707632  date=6/16/2014 17:13:02
6/16/2014 22:49:44 InvalidChainFound:  current best=00000000533bb533712f  height=493344  trust=2002511460146  date=6/16/2014 15:35:01
6/16/2014 22:49:44 ERROR: SetBestChain() : Reorganize failed
6/16/2014 22:49:44 ERROR: AcceptBlock() : AddToBlockIndex failed
6/16/2014 22:49:44 ERROR: ProcessBlock() : AcceptBlock FAILED
6/16/2014 22:49:44 received block 20c7f0046a066f45839f
6/16/2014 22:49:44 Postponing 400 reconnects
6/16/2014 22:49:44 REORGANIZE
6/16/2014 22:49:44 REORGANIZE: Disconnect 1433 blocks; 000000000dd458745575..00000000533bb533712f
6/16/2014 22:49:44 REORGANIZE: Connect 6679 blocks; 000000000dd458745575..d9a6e62459d7a48767d7
6/16/2014 22:49:47 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 22:49:47 ERROR: Reorganize() : ConnectBlock 000000000dc4e8984c03 failed
6/16/2014 22:49:48 connection timeout
6/16/2014 22:49:48 InvalidChainFound: invalid block=20c7f0046a066f45839f  height=498990  trust=2002847485104  date=6/16/2014 17:15:11
6/16/2014 22:49:48 InvalidChainFound:  current best=00000000533bb533712f  height=493344  trust=2002511460146  date=6/16/2014 15:35:01
6/16/2014 22:49:48 ERROR: SetBestChain() : Reorganize failed
6/16/2014 22:49:48 ERROR: AcceptBlock() : AddToBlockIndex failed
6/16/2014 22:49:48 ERROR: ProcessBlock() : AcceptBlock FAILED
6/16/2014 22:49:48 received block 0000000002b7458647aa
6/16/2014 22:49:48 Postponing 401 reconnects
6/16/2014 22:49:48 REORGANIZE
6/16/2014 22:49:48 REORGANIZE: Disconnect 1433 blocks; 000000000dd458745575..00000000533bb533712f
6/16/2014 22:49:48 REORGANIZE: Connect 6679 blocks; 000000000dd458745575..d9a6e62459d7a48767d7
6/16/2014 22:49:48 trying connection 31.49.171.27:7685 lastseen=34.4hrs
6/16/2014 22:49:51 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 22:49:51 ERROR: Reorganize() : ConnectBlock 000000000dc4e8984c03 failed
6/16/2014 22:49:52 InvalidChainFound: invalid block=0000000002b7458647aa  height=498991  trust=2002847485143  date=6/16/2014 17:16:49
6/16/2014 22:49:52 InvalidChainFound:  current best=00000000533bb533712f  height=493344  trust=2002511460146  date=6/16/2014 15:35:01
6/16/2014 22:49:52 ERROR: SetBestChain() : Reorganize failed
6/16/2014 22:49:52 ERROR: AcceptBlock() : AddToBlockIndex failed
6/16/2014 22:49:52 ERROR: ProcessBlock() : AcceptBlock FAILED

[eBit]

Clearing out peers.dat got me going again, but it nicely synced up to the short chain again. Now it's trying very hard to sync up with the 5500+ longer chain.  Last time it got a few of these blocks and then reverted to syncing to the shorter chain.  This is the log before it found the longer chain.  Oops, it looks like it gave up on the longer chain and is now happily on the shorter chain.  I added that log below the first one.


6/16/2014 23:07:57 SetBestChain: new best=000000003da7f48b2ad1  height=493824  trust=2003199650830  date=6/16/2014 23:02:16
6/16/2014 23:07:57 ProcessBlock: ACCEPTED
6/16/2014 23:07:57 received block 7c3c7f020970d202ee55
6/16/2014 23:07:57 SetBestChain: new best=7c3c7f020970d202ee55  height=493825  trust=2003216428302  date=6/16/2014 23:04:20
6/16/2014 23:07:58 SetBestChain: new best=0000000022f9de20187e  height=493826  trust=2003216428313  date=6/16/2014 23:05:33
6/16/2014 23:07:58 ProcessBlock: ACCEPTED
6/16/2014 23:07:58 Added 999 addresses from 38.126.94.60: 5 tried, 974 new
6/16/2014 23:07:58 Added 784 addresses from 38.126.94.60: 5 tried, 1608 new
6/16/2014 23:07:58 getblocks 493614 to 00000000000000000000 limit 500
6/16/2014 23:07:58 getblocks 493614 to 00000000000000000000 limit 500
6/16/2014 23:07:59 received block 000000000dbb005521cd
6/16/2014 23:07:59 ProcessBlock: ORPHAN BLOCK, prev=0000000016d7a17ac9e3
6/16/2014 23:07:59 received block 000000000742664d13c8
6/16/2014 23:07:59 ProcessBlock: ORPHAN BLOCK, prev=000000000dbb005521cd
6/16/2014 23:07:59 received getdata (265 invsz)
6/16/2014 23:07:59 Added 521 addresses from 87.106.246.28: 5 tried, 2091 new
6/16/2014 23:07:59 Added 509 addresses from 87.106.246.28: 5 tried, 2496 new
6/16/2014 23:07:59 Added 267 addresses from 87.106.246.28: 5 tried, 2684 new
6/16/2014 23:07:59 ProcessSyncCheckpoint: pending for sync-checkpoint 000000000aab4cb51320db3bff8c3137cdc0b3f0593001a2a0f4c2554bc4d8a7
6/16/2014 23:07:59 socket send error 10054
6/16/2014 23:07:59 disconnecting node 87.106.246.28:7685
6/16/2014 23:07:59 getblocks 493614 to 00000000000000000000 limit 500
6/16/2014 23:08:00 Flushing wallet.dat
6/16/2014 23:08:00 Flushed wallet.dat 30ms
6/16/2014 23:08:01 received block 000000002d939e30106f
6/16/2014 23:08:01 SetBestChain: new best=000000002d939e30106f  height=493827  trust=2003216428324  date=6/16/2014 23:05:49
6/16/2014 23:08:01 ProcessBlock: ACCEPTED


6/16/2014 23:15:49 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 23:15:49 ERROR: Reorganize() : ConnectBlock 0000000020b13db8cca5 failed
6/16/2014 23:15:50 InvalidChainFound: invalid block=0000000000d29ab3a70c  height=499349  trust=2003166466916  date=6/16/2014 23:12:50
6/16/2014 23:15:50 InvalidChainFound:  current best=0000000055839cec8532  height=493836  trust=2003216428423  date=6/16/2014 23:13:47
6/16/2014 23:15:50 ERROR: SetBestChain() : Reorganize failed
6/16/2014 23:15:50 ERROR: AcceptPendingSyncCheckpoint: SetBestChain failed for sync checkpoint 0000000000d29ab3a70c9668f2359da70e5dc0f0a960c9afc72916a2e67bdc0d
6/16/2014 23:15:50 ProcessBlock: ACCEPTED
6/16/2014 23:15:50 REORGANIZE
6/16/2014 23:15:50 REORGANIZE: Disconnect 1925 blocks; 000000000dd458745575..0000000055839cec8532
6/16/2014 23:15:50 REORGANIZE: Connect 7439 blocks; 000000000dd458745575..000000001770e7b46e2f
6/16/2014 23:15:53 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 23:15:53 ERROR: Reorganize() : ConnectBlock 0000000020b13db8cca5 failed
6/16/2014 23:15:53 connection timeout
6/16/2014 23:15:54 trying connection 75.111.222.12:7685 lastseen=7.7hrs
6/16/2014 23:15:54 InvalidChainFound: invalid block=000000001770e7b46e2f  height=499350  trust=2003166466956  date=6/16/2014 23:14:56
6/16/2014 23:15:54 InvalidChainFound:  current best=0000000055839cec8532  height=493836  trust=2003216428423  date=6/16/2014 23:13:47
6/16/2014 23:15:54 ERROR: SetBestChain() : Reorganize failed
6/16/2014 23:15:54 ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint 000000001770e7b46e2f901732d4ea8b251a5cf46b6c81621475f5fcb25f5437
6/16/2014 23:15:54 REORGANIZE
6/16/2014 23:15:54 REORGANIZE: Disconnect 1925 blocks; 000000000dd458745575..0000000055839cec8532
6/16/2014 23:15:54 REORGANIZE: Connect 7439 blocks; 000000000dd458745575..000000001770e7b46e2f
6/16/2014 23:15:57 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 23:15:57 ERROR: Reorganize() : ConnectBlock 0000000020b13db8cca5 failed
6/16/2014 23:15:58 InvalidChainFound: invalid block=000000001770e7b46e2f  height=499350  trust=2003166466956  date=6/16/2014 23:14:56
6/16/2014 23:15:58 InvalidChainFound:  current best=0000000055839cec8532  height=493836  trust=2003216428423  date=6/16/2014 23:13:47
6/16/2014 23:15:58 ERROR: SetBestChain() : Reorganize failed
6/16/2014 23:15:58 ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint 000000001770e7b46e2f901732d4ea8b251a5cf46b6c81621475f5fcb25f5437
6/16/2014 23:15:58 Flushed 5504 addresses to peers.dat  10ms
6/16/2014 23:15:58 RandAddSeed() 82348 bytes
6/16/2014 23:15:58 Added time data, samples 13, offset -5 (+0 minutes)
6/16/2014 23:15:58 nTimeOffset = -5  (+0 minutes)
6/16/2014 23:15:58 Moving 173.192.30.91:7685 to tried
6/16/2014 23:15:58 receive version message: version 70001, blocks=493836, us=108.36.3.37:3214, them=173.192.30.91:7685, peer=173.192.30.91:7685
6/16/2014 23:15:58 received block 000000002dcf88032246
6/16/2014 23:15:59 connection timeout
6/16/2014 23:15:59 trying connection 71.229.213.22:7685 lastseen=128.3hrs
6/16/2014 23:15:59 SetBestChain: new best=000000002dcf88032246  height=493837  trust=2003216428434  date=6/16/2014 23:14:46
6/16/2014 23:15:59 REORGANIZE
6/16/2014 23:15:59 REORGANIZE: Disconnect 1926 blocks; 000000000dd458745575..000000002dcf88032246
6/16/2014 23:15:59 REORGANIZE: Connect 7438 blocks; 000000000dd458745575..0000000000d29ab3a70c
6/16/2014 23:16:03 ERROR: Connect() : WriteBlockIndex for pindex failed
6/16/2014 23:16:03 ERROR: Reorganize() : ConnectBlock 0000000020b13db8cca5 failed
6/16/2014 23:16:04 InvalidChainFound: invalid block=0000000000d29ab3a70c  height=499349  trust=2003166466916  date=6/16/2014 23:12:50
6/16/2014 23:16:04 InvalidChainFound:  current best=000000002dcf88032246  height=493837  trust=2003216428434  date=6/16/2014 23:14:46
6/16/2014 23:16:04 ERROR: SetBestChain() : Reorganize failed
6/16/2014 23:16:04 ERROR: AcceptPendingSyncCheckpoint: SetBestChain failed for sync checkpoint 0000000000d29ab3a70c9668f2359da70e5dc0f0a960c9afc72916a2e67bdc0d
6/16/2014 23:16:04 ProcessBlock: ACCEPTED

[Tranz]

Clearing out peers.dat got me going again, but it nicely synced up to the short chain again. Now it's trying very hard to sync up with the 5500+ longer chain.  Last time it got a few of these blocks and then reverted to syncing to the shorter chain.  This is the log before it found the longer chain.  Oops, it looks like it gave up on the longer chain and is now happily on the shorter chain.  I added that log below the first one.


6/16/2014 23:07:57 SetBestChain: new best=000000003da7f48b2ad1  height=493824  trust=2003199650830  date=6/16/2014 23:02:16
6/16/2014 23:07:57 ProcessBlock: ACCEPTED
6/16/2014 23:07:57 received block 7c3c7f020970d202ee55
6/16/2014 23:07:57 SetBestChain: new best=7c3c7f020970d202ee55  height=493825  trust=2003216428302  date=6/16/2014 23:04:20
6/16/2014 23:07:58 SetBestChain: new best=0000000022f9de20187e  height=493826  trust=2003216428313  date=6/16/2014 23:05:33
6/16/2014 23:07:58 ProcessBlock: ACCEPTED
6/16/2014 23:07:58 Added 999 addresses from 38.126.94.60: 5 tried, 974 new
6/16/2014 23:07:58 Added 784 addresses from 38.126.94.60: 5 tried, 1608 new
6/16/2014 23:07:58 getblocks 493614 to 00000000000000000000 limit 500
6/16/2014 23:07:58 getblocks 493614 to 00000000000000000000 limit 500
6/16/2014 23:07:59 received block 000000000dbb005521cd
6/16/2014 23:07:59 ProcessBlock: ORPHAN BLOCK, prev=0000000016d7a17ac9e3
6/16/2014 23:07:59 received block 000000000742664d13c8
6/16/2014 23:07:59 ProcessBlock: ORPHAN BLOCK, prev=000000000dbb005521cd
6/16/2014 23:07:59 received getdata (265 invsz)
6/16/2014 23:07:59 Added 521 addresses from 87.106.246.28: 5 tried, 2091 new
6/16/2014 23:07:59 Added 509 addresses from 87.106.246.28: 5 tried, 2496 new
6/16/2014 23:07:59 Added 267 addresses from 87.106.246.28: 5 tried, 2684 new
6/16/2014 23:07:59 ProcessSyncCheckpoint: pending for sync-checkpoint 000000000aab4cb51320db3bff8c3137cdc0b3f0593001a2a0f4c2554bc4d8a7
6/16/2014 23:07:59 socket send error 10054
6/16/2014 23:07:59 disconnecting node 87.106.246.28:7685
6/16/2014 23:07:59 getblocks 493614 to 00000000000000000000 limit 500
6/16/2014 23:08:00 Flushing wallet.dat
6/16/2014 23:08:00 Flushed wallet.dat 30ms
6/16/2014 23:08:01 received block 000000002d939e30106f
6/16/2014 23:08:01 SetBestChain: new best=000000002d939e30106f  height=493827  trust=2003216428324  date=6/16/2014 23:05:49
6/16/2014 23:08:01 ProcessBlock: ACCEPTED


6/16/2014 23:15:49 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 23:15:49 ERROR: Reorganize() : ConnectBlock 0000000020b13db8cca5 failed
6/16/2014 23:15:50 InvalidChainFound: invalid block=0000000000d29ab3a70c  height=499349  trust=2003166466916  date=6/16/2014 23:12:50
6/16/2014 23:15:50 InvalidChainFound:  current best=0000000055839cec8532  height=493836  trust=2003216428423  date=6/16/2014 23:13:47
6/16/2014 23:15:50 ERROR: SetBestChain() : Reorganize failed
6/16/2014 23:15:50 ERROR: AcceptPendingSyncCheckpoint: SetBestChain failed for sync checkpoint 0000000000d29ab3a70c9668f2359da70e5dc0f0a960c9afc72916a2e67bdc0d
6/16/2014 23:15:50 ProcessBlock: ACCEPTED
6/16/2014 23:15:50 REORGANIZE
6/16/2014 23:15:50 REORGANIZE: Disconnect 1925 blocks; 000000000dd458745575..0000000055839cec8532
6/16/2014 23:15:50 REORGANIZE: Connect 7439 blocks; 000000000dd458745575..000000001770e7b46e2f
6/16/2014 23:15:53 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 23:15:53 ERROR: Reorganize() : ConnectBlock 0000000020b13db8cca5 failed
6/16/2014 23:15:53 connection timeout
6/16/2014 23:15:54 trying connection 75.111.222.12:7685 lastseen=7.7hrs
6/16/2014 23:15:54 InvalidChainFound: invalid block=000000001770e7b46e2f  height=499350  trust=2003166466956  date=6/16/2014 23:14:56
6/16/2014 23:15:54 InvalidChainFound:  current best=0000000055839cec8532  height=493836  trust=2003216428423  date=6/16/2014 23:13:47
6/16/2014 23:15:54 ERROR: SetBestChain() : Reorganize failed
6/16/2014 23:15:54 ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint 000000001770e7b46e2f901732d4ea8b251a5cf46b6c81621475f5fcb25f5437
6/16/2014 23:15:54 REORGANIZE
6/16/2014 23:15:54 REORGANIZE: Disconnect 1925 blocks; 000000000dd458745575..0000000055839cec8532
6/16/2014 23:15:54 REORGANIZE: Connect 7439 blocks; 000000000dd458745575..000000001770e7b46e2f
6/16/2014 23:15:57 ERROR: ConnectBlock() : UpdateTxIndex failed
6/16/2014 23:15:57 ERROR: Reorganize() : ConnectBlock 0000000020b13db8cca5 failed
6/16/2014 23:15:58 InvalidChainFound: invalid block=000000001770e7b46e2f  height=499350  trust=2003166466956  date=6/16/2014 23:14:56
6/16/2014 23:15:58 InvalidChainFound:  current best=0000000055839cec8532  height=493836  trust=2003216428423  date=6/16/2014 23:13:47
6/16/2014 23:15:58 ERROR: SetBestChain() : Reorganize failed
6/16/2014 23:15:58 ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint 000000001770e7b46e2f901732d4ea8b251a5cf46b6c81621475f5fcb25f5437
6/16/2014 23:15:58 Flushed 5504 addresses to peers.dat  10ms
6/16/2014 23:15:58 RandAddSeed() 82348 bytes
6/16/2014 23:15:58 Added time data, samples 13, offset -5 (+0 minutes)
6/16/2014 23:15:58 nTimeOffset = -5  (+0 minutes)
6/16/2014 23:15:58 Moving 173.192.30.91:7685 to tried
6/16/2014 23:15:58 receive version message: version 70001, blocks=493836, us=108.36.3.37:3214, them=173.192.30.91:7685, peer=173.192.30.91:7685
6/16/2014 23:15:58 received block 000000002dcf88032246
6/16/2014 23:15:59 connection timeout
6/16/2014 23:15:59 trying connection 71.229.213.22:7685 lastseen=128.3hrs
6/16/2014 23:15:59 SetBestChain: new best=000000002dcf88032246  height=493837  trust=2003216428434  date=6/16/2014 23:14:46
6/16/2014 23:15:59 REORGANIZE
6/16/2014 23:15:59 REORGANIZE: Disconnect 1926 blocks; 000000000dd458745575..000000002dcf88032246
6/16/2014 23:15:59 REORGANIZE: Connect 7438 blocks; 000000000dd458745575..0000000000d29ab3a70c
6/16/2014 23:16:03 ERROR: Connect() : WriteBlockIndex for pindex failed
6/16/2014 23:16:03 ERROR: Reorganize() : ConnectBlock 0000000020b13db8cca5 failed
6/16/2014 23:16:04 InvalidChainFound: invalid block=0000000000d29ab3a70c  height=499349  trust=2003166466916  date=6/16/2014 23:12:50
6/16/2014 23:16:04 InvalidChainFound:  current best=000000002dcf88032246  height=493837  trust=2003216428434  date=6/16/2014 23:14:46
6/16/2014 23:16:04 ERROR: SetBestChain() : Reorganize failed
6/16/2014 23:16:04 ERROR: AcceptPendingSyncCheckpoint: SetBestChain failed for sync checkpoint 0000000000d29ab3a70c9668f2359da70e5dc0f0a960c9afc72916a2e67bdc0d
6/16/2014 23:16:04 ProcessBlock: ACCEPTED

Ok I will have an update tonight or tommorw that should take care of this.

[crackfoo]

Thanks tranz. Hopefully this will make Cryptsy happy too and get it back online.

[StakeHunter]

Vote for HoboNickels on allcoin.com https://www.allcoin.com/vote

BTC address 19DqWMHHHYxux28yrn7UpAx5zJBZpuFTJw

Woohoo! Allcoin accepted my ticket I asked them to add CAP, HBN, TEK, PHS and XMR and they did Good folks at allcoins.com
https://www.allcoin.com/vote/#HBN

I suspect there are quite a few of us with similar interests here but maybe different priorities.
I'd suggest people concentrate on voting the current leader of this batch to a completed listing rather than spread the votes.
Then all getting behind the next front runner

You can vote for five different coins every hour on allcoins.  If you want to see CAP get to the top first then you are going to have to put up some BTC probably.

I agree - the only way any of those coins is going to get listed is through BTC donation, and right now its only ~2 BTC to put one of them on top. Sooooo...

[Tranz]

Guys I have updated to version 2.0.0.1. It is here.

https://github.com/Tranz5/bottlecaps/releases/download/2.0/BottleCaps-qt_2.0.0.1.zip

This should help with sync issues. And at this point older versions are forked off.

If you are stuck, you may have to do a full chain download once more.  If you are ok on 2.0 no need to change.

[eBit]

Guys I have updated to version 2.0.0.1. It is here.

https://github.com/Tranz5/bottlecaps/releases/download/2.0/BottleCaps-qt_2.0.0.1.zip

This should help with sync issues. And at this point older versions are forked off.

If you are stuck, you may have to do a full chain download once more.  If you are ok on 2.0 no need to change.

With peers.dat cleared out on 2.0.0.1 it's syncing now at about 1 to 2 blocks per minute. At this rate, with 5400 blocks left, that's 45 hours.  Any thoughts?



6/17/2014 07:41:32 received block 000000001bff93475f5e
6/17/2014 07:41:32 SetBestChain: new best=000000001bff93475f5e  height=494390  trust=2003686276231  date=6/17/2014 07:40:32
6/17/2014 07:41:32 ProcessBlock: ACCEPTED
6/17/2014 07:41:35 Flushing wallet.dat
6/17/2014 07:41:35 Flushed wallet.dat 51ms
6/17/2014 07:41:36 connection timeout
6/17/2014 07:41:36 trying connection 37.187.73.182:7685 lastseen=3.1hrs
6/17/2014 07:41:36 connected 37.187.73.182:7685
6/17/2014 07:41:36 send version message: version 70003, blocks=494390, us=108.36.3.37:7685, them=37.187.73.182:7685, peer=37.187.73.182:7685
6/17/2014 07:41:37 trying connection 107.209.115.183:7685 lastseen=6.5hrs
6/17/2014 07:41:39 partner 37.187.73.182:7685 using an old client 70001, disconnecting
6/17/2014 07:41:39 disconnecting node 37.187.73.182:7685
6/17/2014 07:41:40 getblocks -1 to 00000000000000000000 limit 500
6/17/2014 07:41:42 connection timeout
6/17/2014 07:41:42 trying connection 70.109.50.114:7685 lastseen=7.4hrs
6/17/2014 07:41:43 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000004232927aa9c8e72a720aef33e3713f1d2db5e3b189c329a196a0c24
6/17/2014 07:41:44 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000004232927aa9c8e72a720aef33e3713f1d2db5e3b189c329a196a0c24
6/17/2014 07:41:44 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000004232927aa9c8e72a720aef33e3713f1d2db5e3b189c329a196a0c24
6/17/2014 07:41:44 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000004232927aa9c8e72a720aef33e3713f1d2db5e3b189c329a196a0c24
6/17/2014 07:41:44 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000004232927aa9c8e72a720aef33e3713f1d2db5e3b189c329a196a0c24
6/17/2014 07:41:45 received block 0000000004232927aa9c
6/17/2014 07:41:45 ProcessBlock: ORPHAN BLOCK, prev=00000000009b5bd44885
6/17/2014 07:41:47 connection timeout
6/17/2014 07:41:48 trying connection 24.249.152.169:7685 lastseen=2.8hrs
6/17/2014 07:41:48 connected 24.249.152.169:7685
6/17/2014 07:41:48 send version message: version 70003, blocks=494390, us=108.36.3.37:7685, them=24.249.152.169:7685, peer=24.249.152.169:7685
6/17/2014 07:41:49 trying connection 24.79.26.236:7685 lastseen=8.5hrs
6/17/2014 07:41:53 partner 24.249.152.169:7685 using an old client 70001, disconnecting
6/17/2014 07:41:53 disconnecting node 24.249.152.169:7685
6/17/2014 07:41:54 connection timeout
6/17/2014 07:41:54 trying connection 212.111.15.232:7685 lastseen=31.1hrs
6/17/2014 07:41:59 connection timeout
6/17/2014 07:42:00 trying connection 24.4.45.219:7685 lastseen=5.7hrs
6/17/2014 07:42:05 connection timeout
6/17/2014 07:42:05 trying connection 24.71.151.25:7685 lastseen=8.8hrs
6/17/2014 07:42:08 received block 00000000132935b0740a
6/17/2014 07:42:08 SetBestChain: new best=00000000132935b0740a  height=494391  trust=2003686276248  date=6/17/2014 07:41:00
6/17/2014 07:42:08 ProcessBlock: ACCEPTED
6/17/2014 07:42:10 Flushing wallet.dat
6/17/2014 07:42:10 Flushed wallet.dat 50ms
6/17/2014 07:42:10 connection timeout
6/17/2014 07:42:11 trying connection 192.3.8.163:7685 lastseen=3.7hrs
6/17/2014 07:42:16 connection timeout
6/17/2014 07:42:16 trying connection 205.197.252.28:7685 lastseen=3.9hrs
6/17/2014 07:42:19 getblocks -1 to 00000000000000000000 limit 500
6/17/2014 07:42:21 connection timeout
6/17/2014 07:42:22 trying connection 89.212.241.225:7685 lastseen=3.3hrs
6/17/2014 07:42:27 connection timeout
6/17/2014 07:42:27 trying connection 86.130.243.167:7685 lastseen=3.1hrs
6/17/2014 07:42:29 received block 0000000027d09967a087
6/17/2014 07:42:29 SetBestChain: new best=0000000027d09967a087  height=494392  trust=2003686276265  date=6/17/2014 07:41:27
6/17/2014 07:42:29 ProcessBlock: ACCEPTED
6/17/2014 07:42:31 Flushing wallet.dat
6/17/2014 07:42:31 Flushed wallet.dat 60ms
6/17/2014 07:42:32 connection timeout
6/17/2014 07:42:33 trying connection 70.109.50.114:7685 lastseen=7.4hrs
6/17/2014 07:42:38 connection timeout
6/17/2014 07:42:38 trying connection 85.65.10.239:7685 lastseen=9.2hrs
6/17/2014 07:42:43 connection timeout
6/17/2014 07:42:44 trying connection 41.150.98.237:7685 lastseen=5.4hrs
6/17/2014 07:42:49 connection timeout
6/17/2014 07:42:50 trying connection 94.29.4.181:7685 lastseen=4.5hrs
6/17/2014 07:42:55 connection timeout
6/17/2014 07:42:55 trying connection 174.55.191.118:7685 lastseen=5.6hrs
6/17/2014 07:43:00 received block 0000000036b441b229c7
6/17/2014 07:43:00 SetBestChain: new best=0000000036b441b229c7  height=494393  trust=2003686276283  date=6/17/2014 07:41:42
6/17/2014 07:43:00 ProcessBlock: ACCEPTED
6/17/2014 07:43:00 connection timeout
6/17/2014 07:43:01 trying connection 107.188.144.125:7685 lastseen=6.9hrs
6/17/2014 07:43:02 Flushing wallet.dat
6/17/2014 07:43:02 Flushed wallet.dat 50ms
6/17/2014 07:43:06 connection timeout
6/17/2014 07:43:06 trying connection 174.55.191.118:7685 lastseen=5.6hrs
6/17/2014 07:43:11 connection timeout
6/17/2014 07:43:12 trying connection 75.97.39.235:7685 lastseen=80.6hrs
6/17/2014 07:43:12 received block 0000000019fb5b55c72b
6/17/2014 07:43:12 SetBestChain: new best=0000000019fb5b55c72b  height=494394  trust=2003686276301  date=6/17/2014 07:42:28
6/17/2014 07:43:12 ProcessBlock: ACCEPTED
6/17/2014 07:43:14 Flushing wallet.dat
6/17/2014 07:43:14 Flushed wallet.dat 50ms
6/17/2014 07:43:17 connection timeout
6/17/2014 07:43:17 trying connection 70.109.50.114:7685 lastseen=7.5hrs
6/17/2014 07:43:19 received block 4f7030ced030c0af2bc8
6/17/2014 07:43:19 ProcessBlock: ORPHAN BLOCK, prev=0000000004232927aa9c
6/17/2014 07:43:19 ProcessSyncCheckpoint: pending for sync-checkpoint 4f7030ced030c0af2bc8b4003867372a7a8955511bcb2bda70b0d124d7968fba
6/17/2014 07:43:19 ProcessSyncCheckpoint: pending for sync-checkpoint 4f7030ced030c0af2bc8b4003867372a7a8955511bcb2bda70b0d124d7968fba
6/17/2014 07:43:20 ProcessSyncCheckpoint: pending for sync-checkpoint 4f7030ced030c0af2bc8b4003867372a7a8955511bcb2bda70b0d124d7968fba
6/17/2014 07:43:20 ProcessSyncCheckpoint: pending for sync-checkpoint 4f7030ced030c0af2bc8b4003867372a7a8955511bcb2bda70b0d124d7968fba
6/17/2014 07:43:21 ProcessSyncCheckpoint: pending for sync-checkpoint 4f7030ced030c0af2bc8b4003867372a7a8955511bcb2bda70b0d124d7968fba
6/17/2014 07:43:22 connection timeout
6/17/2014 07:43:23 trying connection 104.34.125.117:7685 lastseen=3.3hrs
6/17/2014 07:43:28 connection timeout
6/17/2014 07:43:28 trying connection 70.67.166.14:7685 lastseen=9.9hrs
6/17/2014 07:43:33 connection timeout
6/17/2014 07:43:34 trying connection 71.232.87.227:7685 lastseen=18.2hrs
6/17/2014 07:43:39 connection timeout
6/17/2014 07:43:39 trying connection 213.136.73.120:7685 lastseen=5.6hrs
6/17/2014 07:43:44 connection timeout
6/17/2014 07:43:45 trying connection 46.164.21.136:7685 lastseen=88.6hrs
6/17/2014 07:43:50 connection timeout
6/17/2014 07:43:50 trying connection 89.128.142.140:7685 lastseen=5.5hrs
6/17/2014 07:43:55 connection timeout
6/17/2014 07:43:56 trying connection 68.195.32.64:7685 lastseen=3.4hrs
6/17/2014 07:44:01 connection timeout
6/17/2014 07:44:01 trying connection 81.143.68.198:7685 lastseen=29.2hrs
6/17/2014 07:44:06 connection timeout
6/17/2014 07:44:07 trying connection 70.109.50.114:7685 lastseen=7.5hrs
6/17/2014 07:44:12 connection timeout
6/17/2014 07:44:12 trying connection 81.164.85.197:7685 lastseen=3.6hrs
6/17/2014 07:44:17 connection timeout
6/17/2014 07:44:18 trying connection 109.74.193.220:7685 lastseen=5.2hrs
6/17/2014 07:44:23 connection timeout
6/17/2014 07:44:24 trying connection 216.54.25.130:7685 lastseen=3.5hrs
6/17/2014 07:44:29 connection timeout
6/17/2014 07:44:29 trying connection 68.195.32.64:7685 lastseen=3.4hrs
6/17/2014 07:44:32 received block 000000002dc0b5375b28
6/17/2014 07:44:32 SetBestChain: new best=000000002dc0b5375b28  height=494395  trust=2003686276319  date=6/17/2014 07:42:32
6/17/2014 07:44:32 ProcessBlock: ACCEPTED
6/17/2014 07:44:33 getblocks 494394 to 000000002dc0b5375b28 limit 500
6/17/2014 07:44:33   getblocks stopping at 494395 000000002dc0b5375b28
6/17/2014 07:44:34 Flushing wallet.dat
6/17/2014 07:44:34 Flushed wallet.dat 50ms
6/17/2014 07:44:34 connection timeout
6/17/2014 07:44:35 trying connection 75.76.52.206:7685 lastseen=84.7hrs

[eBit]

Guys I have updated to version 2.0.0.1. It is here.

https://github.com/Tranz5/bottlecaps/releases/download/2.0/BottleCaps-qt_2.0.0.1.zip

This should help with sync issues. And at this point older versions are forked off.

If you are stuck, you may have to do a full chain download once more.  If you are ok on 2.0 no need to change.

With peers.dat cleared out on 2.0.0.1 it's syncing now at about 1 to 2 blocks per minute. At this rate, with 5400 blocks left, that's 45 hours.  Any thoughts?

Nope, upon restart it likes the other chain again. I'm going to try to redownload from the beginning with a blank wallet.

[PressF1]

Guys I have updated to version 2.0.0.1. It is here.

https://github.com/Tranz5/bottlecaps/releases/download/2.0/BottleCaps-qt_2.0.0.1.zip

This should help with sync issues. And at this point older versions are forked off.

If you are stuck, you may have to do a full chain download once more.  If you are ok on 2.0 no need to change.

With peers.dat cleared out on 2.0.0.1 it's syncing now at about 1 to 2 blocks per minute. At this rate, with 5400 blocks left, that's 45 hours.  Any thoughts?

Nope, upon restart it likes the other chain again. I'm going to try to redownload from the beginning with a blank wallet.

Seems I have similar problems.
 
Edit

I did 2 clean installs of 2001 and one of them picked up the 500K chain which is the right one I think. The other picked up the other chain, 494K. No idea what causes this difference.

[Tranz]

Once the few clients that are on the wrong chain are gone this shouldn't be an issue any more.

You can also do this. Start fresh and use the -connect (not -addnode) in the Config file or the startup switch

use these IPs

(Start up Switches)
-connect=37.59.48.89:7685
-connect=62.210.122.161:7685
-connect=107.170.113.225:7685
-connect=66.172.12.153:7685
-connect=192.99.35.133:7685
-connect=72.78.100.7:7685
-connect=178.238.45.216:7685
-connect=72.52.231.153:7685
-connect=74.105.241.83:7685

Once you are on the right chain, you can restart without the -connects.

So far i have 3 of 3 computers on the 500k chain, only 1 I had to full re-sync. The rest picked up on restart no problems.

[ghostlander]

The fork happened at block 491911 and those clients trapped on the shorter chain cannot re-organise to the longer chain:

Code:

17/06/14 12:28:22 REORGANIZE
17/06/14 12:28:22 REORGANIZE: Disconnect 2626 blocks; 000000000dd458745575..00000000185b11596f0a
17/06/14 12:28:22 REORGANIZE: Connect 8226 blocks; 000000000dd458745575..7d8c51bf9b063fcaa768
17/06/14 12:28:29 ERROR: DisconnectInputs() : UpdateTxIndex failed
17/06/14 12:28:29 ERROR: Reorganize() : DisconnectBlock afddc6baaef6389282cf failed
17/06/14 12:28:29 InvalidChainFound: invalid block=7d8c51bf9b063fcaa768  height=500137  trust=2003988848859  date=17/06/14 12:27:28
17/06/14 12:28:29 InvalidChainFound:  current best=00000000185b11596f0a  height=494537  trust=2004038605111  date=17/06/14 12:11:53
17/06/14 12:28:29 ERROR: SetBestChain() : Reorganize failed
17/06/14 12:28:29 ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint 7d8c51bf9b063fcaa768f865551f8e79d0382a927923067203a8be43af1d58ba

Why? Because the DB wasn't supposed to handle such load.

Code:

Lock table is out of available lock entries
Lock table is out of available object entries

The solution? Create DB_CONFIG file in your %APPDATA% / BottleCaps directory and put the following in:

Code:

set_lg_dir database
set_lk_max_locks 500000
set_lk_max_objects 50000

Restart your client.

Code:

17/06/14 13:26:23 REORGANIZE
17/06/14 13:26:23 REORGANIZE: Disconnect 2626 blocks; 000000000dd458745575..00000000185b11596f0a
17/06/14 13:26:23 REORGANIZE: Connect 8289 blocks; 000000000dd458745575..8bc0c8f7881230740c0c
[...]
17/06/14 13:27:49 REORGANIZE: done
17/06/14 13:28:07 SetBestChain: new best=00000000061aa230f715  height=500201  trust=2004039184082  date=17/06/14 13:17:03
17/06/14 13:28:07 SetBestChain: new best=000000001268558811c0  height=500202  trust=2004039184130  date=17/06/14 13:17:37
17/06/14 13:28:08 SetBestChain: new best=000000000a060d20d1fb  height=500203  trust=2004039184178  date=17/06/14 13:22:55
17/06/14 13:28:08 AcceptPendingSyncCheckpoint : sync-checkpoint at 000000000a060d20d1fb3f076edc761792a496e84275627f8d4d9e803d4fe25c
17/06/14 13:28:08 ProcessBlock: ACCEPTED

Enjoy. I also suggest Tranz to put a checkpoint at 491915 or so to prevent this from happening.

[crackfoo]

Once the few clients that are on the wrong chain are gone this shouldn't be an issue any more.

You can also do this. Start fresh and use the -connect (not -addnode) in the Config file or the startup switch

use these IPs

(Start up Switches)
-connect=37.59.48.89:7685
-connect=62.210.122.161:7685
-connect=107.170.113.225:7685
-connect=66.172.12.153:7685
-connect=192.99.35.133:7685
-connect=72.78.100.7:7685
-connect=178.238.45.216:7685
-connect=72.52.231.153:7685
-connect=74.105.241.83:7685

Once you are on the right chain, you can restart without the -connects.

So far i have 3 of 3 computers on the 500k chain, only 1 I had to full re-sync. The rest picked up on restart no problems.

I sent a msg to Cryptsy to get the new wallet and to please put CAP back online!

Cheers!

www.xpool.ca