BitBay OFFICIAL BITBAY Thread Smart Contracts Decentralized Markets Rolling Peg - page 29.

CRYPTONAIRE

sr. member

Activity: 527

Merit: 251

Quality Crypto Collector

Quote from: dzimbeck on February 02, 2020, 07:39:44 PM

Quote from: CRYPTONAIRE on February 02, 2020, 02:45:59 PM

Any news about the latest update that was supposed to happen last week?

I have updated the client, even yesterday I posted an updated version. If that's what you were referring to? As for Latoken we are testing the main net.

I was referring to the update you said was going to fix a little error re reporting of frozen/reserved coins. Did you post that yesterday? I didn't see it announced anywhere.

dzimbeck

legendary

Activity: 2412

Merit: 1044

Quote from: CRYPTONAIRE on February 02, 2020, 02:45:59 PM

Any news about the latest update that was supposed to happen last week?

I have updated the client, even yesterday I posted an updated version. If that's what you were referring to? As for Latoken we are testing the main net.

CRYPTONAIRE

sr. member

Activity: 527

Merit: 251

Quality Crypto Collector

Any news about the latest update that was supposed to happen last week?

88998899

newbie

Activity: 35

Merit: 0

Thanks for the full answer! I only remember one password from the password manager.

dzimbeck

legendary

Activity: 2412

Merit: 1044

Quote from: 88998899 on January 29, 2020, 08:03:24 AM

Thanks David for the answer! But I have another question: can a wallet.dat wallet file with a good password be cracked if my wallet.dat accidentally falls into the wrong hands? Thanks!

If the password is good then I don't think so. Every time a character is added to a password it's complexity increases exponentially. So not even a "quantum" computer could solve a long enough password. On the other hand, you want to be realistic and be able to remember your password. Or else you will find backing up a password in one place and keys in the other. If a wallet file is password protected and you forget or lose that password you also would lose access to your account so consider all of that when backing up.

88998899

newbie

Activity: 35

Merit: 0

Thanks David for the answer! But I have another question: can a wallet.dat wallet file with a good password be cracked if my wallet.dat accidentally falls into the wrong hands? Thanks!

dzimbeck

legendary

Activity: 2412

Merit: 1044

Quote from: 88998899 on January 29, 2020, 05:25:52 AM

Hello! What reliable cloud storage for wallet (wallet.dat) is better to use? Thank you!

I don't personally recommend cloud storage but you can just as well encrypt it with a password in Winrar and email it to yourself. Also it's good to store on a flash drive. Just always remember to not lose passwords.

dzimbeck

legendary

Activity: 2412

Merit: 1044

Quote from: raisinbran on January 28, 2020, 11:16:04 AM

Right now BAY earns about 2.2% annually if continuously staked. Does 2.2% correspond to the 5 BAY rewards earned by Liquid BAY? So would the 40 BAY rewards for Frozen Liquid BAY correspond to 8 * 2.2% = 17.6% ?

Actually that's the thing. The maximum inflation of the economy is 2% but that assumes everyone who stakes does voluntary freeze for the bonus. So in truth the real number is unknown. It is anywhere from .25-2% per year (5-40 coins per block)

dzimbeck

legendary

Activity: 2412

Merit: 1044

Quote from: marecek666 on January 28, 2020, 10:40:03 AM

@dzimbeck thanks for the reaction, I run QT wallet. Tried to add nodes which are running this latest wallet (from this explorer: https://chainz.cryptoid.info/bay/#!network) , but still the same. Some progress and hours of nothing after that. Never mind, I will sync it somehow, there is about 1/3 of the chain to download left. I have to close/open wallet again and again. Bootstrap could be fine, but there is no official download link and taking the one from somebody on the Internet is not the best solution.

You have to be patient, it takes 10 days to sync the chain at least without bootstrap.

88998899

newbie

Activity: 35

Merit: 0

Hello! What reliable cloud storage for wallet (wallet.dat) is better to use? Thank you!

marecek666

member

Activity: 236

Merit: 12

Quote from: BitBayDoc on January 28, 2020, 02:32:21 PM

Quote from: ExEric3 on January 28, 2020, 02:22:43 PM

Quote from: yshurik on January 24, 2020, 03:36:55 PM

Quote from: ExEric3 on January 24, 2020, 04:57:42 AM

Updated QT wallet to v3 and it stuck on block 2459220, 38 hours ago. Synced from scratch. How fix it?

This may happen as not 100% nodes were updated before hard fork.
So you unluckily stuck into abandoned chain looks like.
Simplest and quick way:

1. stop qt wallet
2. backup wallet.dat somewere
3. remove all files in datafolder except wallet.dat
4. place bootstrap.dat in datafolder
5. start qt wallet

bootstrap file is updated up to Jan 23 - bypassing fork point, so you should be safe after resync.
it may take 2-3 hours to load from bootstrap which is much faster then ordinary resync.

Usually new exchanges dont want use bootstrap file and want sync from scratch like me. But got same errors like @marecek666 had.

We are not using "new" exchanges at this point; when we are ready for them the bootstrap file won't be an issue.

You and @marecek666 seem to be the only ones who are having problems. It's really not that hard.
If you are having so many orphans (like no one else is...), the best thing to do is Resync. Easy.
Everything is running smoothly and was easy to update on my end - and with now at least 75% of coin Stakers.

very simple ... but ordinary resync is not smooth and stuck at random blocks. Wallet is not able to continue and takes everything as an orphan. It is able to accept next blocks for several minutes after the restart.
But I finally got it fully synced after many restarts of the wallet (I did not know about the link for bootstrap). It is synced and staking for now.
anyway thanks for your input Wink

BitBayDoc

jr. member

Activity: 193

Merit: 3

Quote from: ExEric3 on January 28, 2020, 02:22:43 PM

Quote from: yshurik on January 24, 2020, 03:36:55 PM

Quote from: ExEric3 on January 24, 2020, 04:57:42 AM

Updated QT wallet to v3 and it stuck on block 2459220, 38 hours ago. Synced from scratch. How fix it?

This may happen as not 100% nodes were updated before hard fork.
So you unluckily stuck into abandoned chain looks like.
Simplest and quick way:

1. stop qt wallet
2. backup wallet.dat somewere
3. remove all files in datafolder except wallet.dat
4. place bootstrap.dat in datafolder
5. start qt wallet

bootstrap file is updated up to Jan 23 - bypassing fork point, so you should be safe after resync.
it may take 2-3 hours to load from bootstrap which is much faster then ordinary resync.

Usually new exchanges dont want use bootstrap file and want sync from scratch like me. But got same errors like @marecek666 had.

We are not using "new" exchanges at this point; when we are ready for them the bootstrap file won't be an issue.

You and @marecek666 seem to be the only ones who are having problems. It's really not that hard.
If you are having so many orphans (like no one else is...), the best thing to do is Resync. Easy.
Everything is running smoothly and was easy to update on my end - and with now at least 75% of coin Stakers.

ExEric3

full member

Activity: 176

Merit: 100

Quote from: yshurik on January 24, 2020, 03:36:55 PM

Quote from: ExEric3 on January 24, 2020, 04:57:42 AM

Updated QT wallet to v3 and it stuck on block 2459220, 38 hours ago. Synced from scratch. How fix it?

This may happen as not 100% nodes were updated before hard fork.
So you unluckily stuck into abandoned chain looks like.
Simplest and quick way:

1. stop qt wallet
2. backup wallet.dat somewere
3. remove all files in datafolder except wallet.dat
4. place bootstrap.dat in datafolder
5. start qt wallet

bootstrap file is updated up to Jan 23 - bypassing fork point, so you should be safe after resync.
it may take 2-3 hours to load from bootstrap which is much faster then ordinary resync.

Usually new exchanges dont want use bootstrap file and want sync from scratch like me. But got same errors like @marecek666 had.

BitBayDoc

jr. member

Activity: 193

Merit: 3

TEAM: This is pretty cool to see the results of my Liquid, Reserve and Supply% of BAY that everyone is voting on - in the "History" section of my Wallet in the BAY Client.
Monetary History is being made right now and FEW even know it. lol

Right now the Peg Supply%, which is my Supply% also, is 50.99% - that's the lowest I've ever seen it. Very cool - it's working beautifully when the majority vote to deflate!

Even after all these years I thought I knew how all this worked; but as I recently found out from David, I was right in some respects and off the mark in others. Lol

I must say that after I think I now finally grasp what BAY really is, and could become; it is even BETTER than I ever imagined! Shocked

I wonder if the rest of the world knows that D. Zimbeck is one of the greatest, and maybe the greatest Chess Puzzle makers ever?
Not many people in the world are world class Chess players; yet alone world class Chess Puzzle MAKERS... I know I most certainly am not Cheesy

; and don't know anyone else who is. David was a Child Prodigy in Chess and could easily be a Grand Master if that's what he so desired.
His self taught genius and deep sense of fairness for everything business are on display in this BAY peg; and is simply amazing to witness.

D. Zimbeck Reply:
That's nice of you to say, thanks Doc. Yeah for those who are wondering what he's talking about, as I kid I composed puzzles as a "task composer" to set world records and such. I only learned chess at 11 but started composing at 13 and my work was published shortly after. At the time, I collaborated with some composers like Edgar Holladay and Milan Vukcevich both of whom are legends. Holladay used to send me hand written letters in the mail with the board hand drawn and the pieces stamped on. Hahaha the days before the internet or cell phones. The puzzles I created were designed to stump grandmasters and computers, one took me years to prove it's validity and ensure it was dual-free and sound. Since computers weren't any help in proofing it, the work was very demanding. It's a sort of art form. I wasn't really interested in competitive chess.

My work in chess can be found here:
www.zimbeckchess.com

raisinbran

jr. member

Activity: 64

Merit: 2

Right now BAY earns about 2.2% annually if continuously staked. Does 2.2% correspond to the 5 BAY rewards earned by Liquid BAY? So would the 40 BAY rewards for Frozen Liquid BAY correspond to 8 * 2.2% = 17.6% ?

cr197

full member

Activity: 307

Merit: 109

Quote from: marecek666 on January 28, 2020, 10:40:03 AM

@dzimbeck thanks for the reaction, I run QT wallet. Tried to add nodes which are running this latest wallet (from this explorer: https://chainz.cryptoid.info/bay/#!network) , but still the same. Some progress and hours of nothing after that. Never mind, I will sync it somehow, there is about 1/3 of the chain to download left. I have to close/open wallet again and again. Bootstrap could be fine, but there is no official download link and taking the one from somebody on the Internet is not the best solution.

Here is bootstrap
https://github.com/bitbaymarket/bitbay-bootstrap/releases

marecek666

member

Activity: 236

Merit: 12

@dzimbeck thanks for the reaction, I run QT wallet. Tried to add nodes which are running this latest wallet (from this explorer: https://chainz.cryptoid.info/bay/#!network) , but still the same. Some progress and hours of nothing after that. Never mind, I will sync it somehow, there is about 1/3 of the chain to download left. I have to close/open wallet again and again. Bootstrap could be fine, but there is no official download link and taking the one from somebody on the Internet is not the best solution.

dzimbeck

legendary

Activity: 2412

Merit: 1044

Quote from: marecek666 on January 28, 2020, 03:04:37 AM

Really thanks devs for the new version of wallet. It is super to see that the development is going forward. But this new wallet is the worst I have ever seen for syncing. It was not able to start with datadir files synced from previous version (keep crashing). I deleted whole contents of datadir except my wallet.dat and let it sync from the scratch. But it is not able to do full sync. It is doing OK for several minutes and after that stop at random block and for hours nothing after that. Log file contains ten thousands of lines with this:

Quote

ProcessBlock: ORPHAN BLOCK 751, prev=6b9c47a930d19f85eb84f5424cbe8a2ece68eddb0ba96c3783dcdc3a0730fee8
ProcessBlock: ORPHAN BLOCK 751, prev=39d68f41cd954fa5643733b6415243ed2b1c89e1f9b5ace5973752e43325634d
ProcessBlock: ORPHAN BLOCK 751, prev=5b3290efd9c5d72b358355634cd68a2b97a6505ffe0d279deca4cce33e93c5e2
ProcessBlock: ORPHAN BLOCK 751, prev=7aa4ee812b6d9ac199249bca92bd03c60fd7a9c10e39fe23b58c51ea31fb59be
ProcessBlock: ORPHAN BLOCK 751, prev=5da94a777f49afaaf18f58422087fdcb22dbbab32dc0064092215213019248ad
ProcessBlock: ORPHAN BLOCK 751, prev=f8bfb7bc91af2ca16059b0ac89f1bcfbbe5df294aa0972d7d03ca026f385bfe0
ProcessBlock: ORPHAN BLOCK 751, prev=dc8ed177ef4cbae6a3691b31d27526fde5d8dc061e83cc8bb39079bd96999960
ProcessBlock: ORPHAN BLOCK 751, prev=e89926c8fce06c4d8ebdef9ad2e506e507585c59b145b5baea307e779679fea0
ProcessBlock: ORPHAN BLOCK 751, prev=802ddfabc4027007d312246b0cb62857aa2e10375a2984fcd65b69f05ae4a6ee
ProcessBlock: ORPHAN BLOCK 751, prev=c615fcf1c151531e7a42124b50181c1c6a82b4bb72365962b9628a6730ddc072
ProcessBlock: ORPHAN BLOCK 751, prev=b6e385f5fdd501d3b02389eac14c0a3e463f85ba7ee4279543cbdb99b305af0b
ProcessBlock: ORPHAN BLOCK 751, prev=a812341041c24d9bf6d2d94d545f6a1841162e588002f494043a29b69e52d4f7
ProcessBlock: ORPHAN BLOCK 751, prev=fa4e077fe7a7f4b2c66e30137ef827d8fee18efc245dab7a5111f19e6e8cc2d8
ProcessBlock: ORPHAN BLOCK 751, prev=2e3b6d27d2a993591947db9b8783e80c08e9ce94aa7fb911bae4bfd9e95a2285
ProcessBlock: ORPHAN BLOCK 751, prev=6f48a64dc85694cb75a8239c2c409b8b8bf9378c3f012a2fd7ce09d831affe50
ProcessBlock: ORPHAN BLOCK 751, prev=a9eda22eabdee7580667aefc870ae338785527371616e28765d7dfd0004512f6
ProcessBlock: ORPHAN BLOCK 751, prev=7c5ec75ec91108edb203cd9b61bc8e05e2af535f52cfeac3fe76de98e9a3bd61
ProcessBlock: ORPHAN BLOCK 751, prev=09fdfec43ec421e5430710d1290f3e274e0ef8ee8ce0717794e6a88d78c5bc35
ProcessBlock: ORPHAN BLOCK 751, prev=4fe7c64d768949bc9227eae733e7a59b949ec1f3f525e834ba5ac7b4991af458
ProcessBlock: ORPHAN BLOCK 751, prev=2a2d1f21ebba9b138cde866497a8fba52a60f16efef171885c44a32d89db28bc
ProcessBlock: ORPHAN BLOCK 751, prev=dbbe6218665559590dcf50be71c2219bf5f521f2985604376d6644414467bd6c
ProcessBlock: ORPHAN BLOCK 751, prev=0f11497388313d629e556151c5e5f460e748ee11dccf9c3c1917e6776749d1bf
ProcessBlock: ORPHAN BLOCK 751, prev=6a6ccb5adfbb2ce31221a6a4af332dc6ff24b7f2ba17304a7b5655956eb69748
ProcessBlock: ORPHAN BLOCK 751, prev=a579af0c989b2dc162c4f9f2e8f5601e360b61770210938de9c011f6ae21c9e0
ProcessBlock: ORPHAN BLOCK 751, prev=568f611f8a08b964b92d7e91dab65c9e54f981d296a9e9fe185502c3e1d23059
ProcessBlock: ORPHAN BLOCK 751, prev=dd15d586f01976d3b8332afb42b2a6024092975bdf2f8b18850cdac342c89822
ProcessBlock: ORPHAN BLOCK 751, prev=f4e7a564f40eeb979b8971c9f379107ef700dc7749e6e27598cd29c48f6e3839
ProcessBlock: ORPHAN BLOCK 751, prev=0477f56897be51e0e9690209e1943471f89dd6c7bf666bc92a77fa117c6d7845
ProcessBlock: ORPHAN BLOCK 751, prev=5cd4f6c2d1548f7e6bc7d3fa11b5cb4b266674affca344a9ce3384a4cfab3f23
ProcessBlock: ORPHAN BLOCK 751, prev=3f87ee10573fff0c0c0fec3edebd19ea99cd0a7d2c15f93bb40f5730ab3d580a
ProcessBlock: ORPHAN BLOCK 751, prev=59dc6a0164f0cb751edad7d9edaaef858736be4eb0867b80da0e466202cf551d
ProcessBlock: ORPHAN BLOCK 751, prev=a0440a0888c0a7be359162c892b615102d92bdd7dfee687023fdae18df70735b
ProcessBlock: ORPHAN BLOCK 751, prev=866a966784067955dc632b7382545e811470c367cd8ee99301a3ea9862eddc37
ProcessBlock: ORPHAN BLOCK 751, prev=c61366e3180f0741b995b41c79d15423a384c6b9deffcd9932af3a44387f0905
ProcessBlock: ORPHAN BLOCK 751, prev=da9c7850f0b99cd7bd6a69eac8a6fce80f130a3b1df28a743d1c8b1da08c5efc
ProcessBlock: ORPHAN BLOCK 751, prev=84f8184100d485d7a0cb3764b87fca030327056b861dadadd9cf0b9cd4785120
ProcessBlock: ORPHAN BLOCK 751, prev=0de34b0cb181b49901aa3bb3197ad0fb1124efdff7922716c1ad2a1e66137ff7
ProcessBlock: ORPHAN BLOCK 751, prev=c5b523b20a0c3bc7c70b1320840be73759f37ca017e97635b38a142d0c25427e
ProcessBlock: ORPHAN BLOCK 751, prev=52f14e9238e8be4277e16237dcd1741aac00c949b18d4d77737fbfc01f086c0e
ProcessBlock: ORPHAN BLOCK 751, prev=8c68d040c538bebc59352ea4a377acd8c289310851310023b99e8bddae006637
ProcessBlock: ORPHAN BLOCK 751, prev=61b56b32d7b18ae9c1f93248e74d856b0c6b40faf2e63ffc1d4d8ac795f85126
ProcessBlock: ORPHAN BLOCK 751, prev=26a6258e8c70858f206e8ead1f2aaab16ab6a625c51a52fc9d229e17718f7fd5
ProcessBlock: ORPHAN BLOCK 751, prev=c036a1850117322b0311b8496cd98c1e4736b15262e8b5b9c11b95571f762c98
ProcessBlock: ORPHAN BLOCK 751, prev=452a11197afa6567abc990d1a13e4a9fc9c422267533f86607700025d1e005ae
ProcessBlock: ORPHAN BLOCK 751, prev=b3caf19df6f4a80affc600693f52da0da65fb1c152686572d818e37b466f6398
ProcessBlock: ORPHAN BLOCK 751, prev=a39b6654ef522d4eda785684f8595225a4df5250379dc0e6d823264b3165ec31
ProcessBlock: ORPHAN BLOCK 751, prev=9278edf80299b7abae1271c8ef738feb82bb8e9b9806b29adf79379dcbdfdf10
ProcessBlock: ORPHAN BLOCK 751, prev=e264068cf4455b6614aeaaab40b61cb0ad599b5dd7f1d67673873cd4baf33976
ProcessBlock: ORPHAN BLOCK 751, prev=aa1355d0445953ee6f4525080b3dab11a3cb941c77502ded6c7d8faae98fb4e7

I have to close wallet, delete generated log file (it is prety large) and start it again. It can continue in syncing again after that. But it stops on another random block again. So have to close and start it again for syncing another blocks until next stop ...
Running on i5-3470, 16GB, SSD, Win8.1, 1Gbps symmetric connection. Previous wallet was well working.

Well first off the newest Halo wallet pre vs post fork downgraded leveldb to match the QT (I wanted to stay on the newer version but Bitcoin also runs old version so Yshurik convinced me to make it compatible). However I'm not sure if you are running Markets/Halo wallet or QT. Since that change was only to markets wallet.

Orphan blocks have nothing to do with the wallet, it's a local phenomenon on the chain. It's possible there is a group of nodes that didn't port over to the fork or you updated too late or some nodes are staking different length of the chain and it should self-correct. So when you have so many orphans the best thing to do is to resync. You can save yourself a lot of time by downloading the bootstrap. I will ask the team to post a link to it. Since I don't have it off hand however I think we now have it automated to update the bootstrap. Hopefully someone will post a bootstrap link here shortly.

marecek666

member

Activity: 236

Merit: 12

Really thanks devs for the new version of wallet. It is super to see that the development is going forward. But this new wallet is the worst I have ever seen for syncing. It was not able to start with datadir files synced from previous version (keep crashing). I deleted whole contents of datadir except my wallet.dat and let it sync from the scratch. But it is not able to do full sync. It is doing OK for several minutes and after that stop at random block and for hours nothing after that. Log file contains ten thousands of lines with this:

Quote

ProcessBlock: ORPHAN BLOCK 751, prev=6b9c47a930d19f85eb84f5424cbe8a2ece68eddb0ba96c3783dcdc3a0730fee8
ProcessBlock: ORPHAN BLOCK 751, prev=39d68f41cd954fa5643733b6415243ed2b1c89e1f9b5ace5973752e43325634d
ProcessBlock: ORPHAN BLOCK 751, prev=5b3290efd9c5d72b358355634cd68a2b97a6505ffe0d279deca4cce33e93c5e2
ProcessBlock: ORPHAN BLOCK 751, prev=7aa4ee812b6d9ac199249bca92bd03c60fd7a9c10e39fe23b58c51ea31fb59be
ProcessBlock: ORPHAN BLOCK 751, prev=5da94a777f49afaaf18f58422087fdcb22dbbab32dc0064092215213019248ad
ProcessBlock: ORPHAN BLOCK 751, prev=f8bfb7bc91af2ca16059b0ac89f1bcfbbe5df294aa0972d7d03ca026f385bfe0
ProcessBlock: ORPHAN BLOCK 751, prev=dc8ed177ef4cbae6a3691b31d27526fde5d8dc061e83cc8bb39079bd96999960
ProcessBlock: ORPHAN BLOCK 751, prev=e89926c8fce06c4d8ebdef9ad2e506e507585c59b145b5baea307e779679fea0
ProcessBlock: ORPHAN BLOCK 751, prev=802ddfabc4027007d312246b0cb62857aa2e10375a2984fcd65b69f05ae4a6ee
ProcessBlock: ORPHAN BLOCK 751, prev=c615fcf1c151531e7a42124b50181c1c6a82b4bb72365962b9628a6730ddc072
ProcessBlock: ORPHAN BLOCK 751, prev=b6e385f5fdd501d3b02389eac14c0a3e463f85ba7ee4279543cbdb99b305af0b
ProcessBlock: ORPHAN BLOCK 751, prev=a812341041c24d9bf6d2d94d545f6a1841162e588002f494043a29b69e52d4f7
ProcessBlock: ORPHAN BLOCK 751, prev=fa4e077fe7a7f4b2c66e30137ef827d8fee18efc245dab7a5111f19e6e8cc2d8
ProcessBlock: ORPHAN BLOCK 751, prev=2e3b6d27d2a993591947db9b8783e80c08e9ce94aa7fb911bae4bfd9e95a2285
ProcessBlock: ORPHAN BLOCK 751, prev=6f48a64dc85694cb75a8239c2c409b8b8bf9378c3f012a2fd7ce09d831affe50
ProcessBlock: ORPHAN BLOCK 751, prev=a9eda22eabdee7580667aefc870ae338785527371616e28765d7dfd0004512f6
ProcessBlock: ORPHAN BLOCK 751, prev=7c5ec75ec91108edb203cd9b61bc8e05e2af535f52cfeac3fe76de98e9a3bd61
ProcessBlock: ORPHAN BLOCK 751, prev=09fdfec43ec421e5430710d1290f3e274e0ef8ee8ce0717794e6a88d78c5bc35
ProcessBlock: ORPHAN BLOCK 751, prev=4fe7c64d768949bc9227eae733e7a59b949ec1f3f525e834ba5ac7b4991af458
ProcessBlock: ORPHAN BLOCK 751, prev=2a2d1f21ebba9b138cde866497a8fba52a60f16efef171885c44a32d89db28bc
ProcessBlock: ORPHAN BLOCK 751, prev=dbbe6218665559590dcf50be71c2219bf5f521f2985604376d6644414467bd6c
ProcessBlock: ORPHAN BLOCK 751, prev=0f11497388313d629e556151c5e5f460e748ee11dccf9c3c1917e6776749d1bf
ProcessBlock: ORPHAN BLOCK 751, prev=6a6ccb5adfbb2ce31221a6a4af332dc6ff24b7f2ba17304a7b5655956eb69748
ProcessBlock: ORPHAN BLOCK 751, prev=a579af0c989b2dc162c4f9f2e8f5601e360b61770210938de9c011f6ae21c9e0
ProcessBlock: ORPHAN BLOCK 751, prev=568f611f8a08b964b92d7e91dab65c9e54f981d296a9e9fe185502c3e1d23059
ProcessBlock: ORPHAN BLOCK 751, prev=dd15d586f01976d3b8332afb42b2a6024092975bdf2f8b18850cdac342c89822
ProcessBlock: ORPHAN BLOCK 751, prev=f4e7a564f40eeb979b8971c9f379107ef700dc7749e6e27598cd29c48f6e3839
ProcessBlock: ORPHAN BLOCK 751, prev=0477f56897be51e0e9690209e1943471f89dd6c7bf666bc92a77fa117c6d7845
ProcessBlock: ORPHAN BLOCK 751, prev=5cd4f6c2d1548f7e6bc7d3fa11b5cb4b266674affca344a9ce3384a4cfab3f23
ProcessBlock: ORPHAN BLOCK 751, prev=3f87ee10573fff0c0c0fec3edebd19ea99cd0a7d2c15f93bb40f5730ab3d580a
ProcessBlock: ORPHAN BLOCK 751, prev=59dc6a0164f0cb751edad7d9edaaef858736be4eb0867b80da0e466202cf551d
ProcessBlock: ORPHAN BLOCK 751, prev=a0440a0888c0a7be359162c892b615102d92bdd7dfee687023fdae18df70735b
ProcessBlock: ORPHAN BLOCK 751, prev=866a966784067955dc632b7382545e811470c367cd8ee99301a3ea9862eddc37
ProcessBlock: ORPHAN BLOCK 751, prev=c61366e3180f0741b995b41c79d15423a384c6b9deffcd9932af3a44387f0905
ProcessBlock: ORPHAN BLOCK 751, prev=da9c7850f0b99cd7bd6a69eac8a6fce80f130a3b1df28a743d1c8b1da08c5efc
ProcessBlock: ORPHAN BLOCK 751, prev=84f8184100d485d7a0cb3764b87fca030327056b861dadadd9cf0b9cd4785120
ProcessBlock: ORPHAN BLOCK 751, prev=0de34b0cb181b49901aa3bb3197ad0fb1124efdff7922716c1ad2a1e66137ff7
ProcessBlock: ORPHAN BLOCK 751, prev=c5b523b20a0c3bc7c70b1320840be73759f37ca017e97635b38a142d0c25427e
ProcessBlock: ORPHAN BLOCK 751, prev=52f14e9238e8be4277e16237dcd1741aac00c949b18d4d77737fbfc01f086c0e
ProcessBlock: ORPHAN BLOCK 751, prev=8c68d040c538bebc59352ea4a377acd8c289310851310023b99e8bddae006637
ProcessBlock: ORPHAN BLOCK 751, prev=61b56b32d7b18ae9c1f93248e74d856b0c6b40faf2e63ffc1d4d8ac795f85126
ProcessBlock: ORPHAN BLOCK 751, prev=26a6258e8c70858f206e8ead1f2aaab16ab6a625c51a52fc9d229e17718f7fd5
ProcessBlock: ORPHAN BLOCK 751, prev=c036a1850117322b0311b8496cd98c1e4736b15262e8b5b9c11b95571f762c98
ProcessBlock: ORPHAN BLOCK 751, prev=452a11197afa6567abc990d1a13e4a9fc9c422267533f86607700025d1e005ae
ProcessBlock: ORPHAN BLOCK 751, prev=b3caf19df6f4a80affc600693f52da0da65fb1c152686572d818e37b466f6398
ProcessBlock: ORPHAN BLOCK 751, prev=a39b6654ef522d4eda785684f8595225a4df5250379dc0e6d823264b3165ec31
ProcessBlock: ORPHAN BLOCK 751, prev=9278edf80299b7abae1271c8ef738feb82bb8e9b9806b29adf79379dcbdfdf10
ProcessBlock: ORPHAN BLOCK 751, prev=e264068cf4455b6614aeaaab40b61cb0ad599b5dd7f1d67673873cd4baf33976
ProcessBlock: ORPHAN BLOCK 751, prev=aa1355d0445953ee6f4525080b3dab11a3cb941c77502ded6c7d8faae98fb4e7

I have to close wallet, delete generated log file (it is prety large) and start it again. It can continue in syncing again after that. But it stops on another random block again. So have to close and start it again for syncing another blocks until next stop ...
Running on i5-3470, 16GB, SSD, Win8.1, 1Gbps symmetric connection. Previous wallet was well working.

dzimbeck

legendary

Activity: 2412

Merit: 1044

That's nice of you to say, thanks Doc. Yeah for those who are wondering what he's talking about, as I kid I composed puzzles as a "task composer" to set world records and such. I only learned chess at 11 but started composing at 13 and my work was published shortly after. At the time, I collaborated with some composers like Edgar Holladay and Milan Vukcevich both of whom are legends. Holladay used to send me hand written letters in the mail with the board hand drawn and the pieces stamped on. Hahaha the days before the internet or cell phones. The puzzles I created were designed to stump grandmasters and computers, one took me years to prove it's validity and ensure it was dual-free and sound. Since computers weren't any help in proofing it, the work was very demanding. It's a sort of art form. I wasn't really interested in competitive chess.

My work in chess can be found here:
www.zimbeckchess.com

Topic: BitBay OFFICIAL BITBAY Thread Smart Contracts Decentralized Markets Rolling Peg - page 29. (Read 542094 times)