@dzimbeck
@BitBayDocThanks for the replies guys! Now a few more queries: I have downloaded v3.0.0.15-gf683d6; is this correct? Reason I ask is that there appears to be no discernible difference from previous version. I have a frozen balance = 0; is this simply because I have not yet voluntarily frozen anything? Where does the supply = 100% appear? And does it matter to me? How do I freeze coins exactly? Do I have to freeze ALL of my coins, or simply a number that I specify? As for paying attention BBD, I never take my eyes off this thing. I'm not into many crypto projects, just a handful, and BAY is my absolute favourite. Gold-plated, diamond-studded excellence! Sorry about all the queries, but I'm not a techie like you bods, so I need all the help I can get!  Thanks for the feedback  . I didn't realize you were using QT and not Halo. In that case your version sounds correct. You won't see a frozen balance if you haven't voluntarily frozen anything(although you may see reserve coins if the supply changes). The supply appears at the top of the QT and it matters to know the supply to know the size and health of the economy in my opinion. To freeze there are options for voluntary liquid freeze (4 month lock 40 coins reward) and reserve transfer/freeze (1 month lock 20 coins reward). You simply send the coins to yourself with one of those options selected. You don't have to freeze anything if you don't want to. The reason people do it is to get a boost in staking rewards. And some people only choose to freeze a certain portion of their account. Also they choose to freeze in batches of no more than 100k per transaction/freeze so they can be ensured consecutive stakes. Since I don't think QT batches the outputs (Halo does do that for you however QT doesn't) |
|
|
|
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. Oh I guess we forgot to report back to Bitcointalk. That has been out for I think over a week. So sure please update the client from bitbay.market Your frozen balance will definitely show. And also we have raised the supply to 100% so anyone who wants to freeze voluntarily to get the stake reward bonus can do so. If using Halo just remember to break for change if you have any large inputs over 100k. |
|
|
|
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. |
|
|
|
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. |
|
|
|
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. |
|
|
|
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 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. |
|
|
|
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: 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. |
|
|
|
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 |
|
|
|
Thanks, congrats everyone.
Also to the question about freezing, Halo batch freezes for you in advanced sending. I tested it however I'm missing an API command (listfrozen) I didn't realize Yshurik split those up so the frozen balance won't show until the next update which should be in a week. Of course you can still voluntarily freeze in Halo now. We may drop supply temporarily just to test all the features but before Latoken launch there is a good chance the community will raise it to zero so the crypto world gets to see it gradually progress forward. This is up for discussion.
May I ask, what is this "next update"? Is there anything we need to do in preparation for it? Also, the staking appears to be behaving oddly again. Payouts, which were for 19.99994446, have now dropped to 4.99994446. And they are VERY infrequent. My wife has 1.3 million BAY. She has received three of these payments into her wallet since the fork activated. I have over 20 million coins in my wallet, but I have received zero payments. Any thoughts? The reason is the cost to vote is 5554... that number was chose arbitrarily The software will not vote if you ask it not to. You can see all of this in the settings tab. In fact, the software may only vote about 100-200 times before it forces you to return to the settings tab and decide to vote again. This makes it so nobody falls asleep at the wheel voting in a way that harms the system. Big stakers will want to then revisit the software every couple days to ensure the vote is set to automatic(community algorithm) or whatever they choose. |
|
|
|
Thanks for the replies.
@shaydinblue: I was aware that the peg is active, I was really just following up on the post by BitBayDoc re freezing/reserving. BBD said he was not going to freeze/reserve until after next update, implying he had the choice. I was just wondering why coins were being reserved without any action being taken.
@yshurik: what exactly is the difference between reserved coins and frozen coins?
Doc was mistaken when he used the term reserve/frozen interchangeably An output in the peg instead of being an integer is simply an array of values. These values say when parts of those coins will be reserve or liquid. The difference between reserve and liquid are simply that reserve moves slower and must be locked for 1 month or "frozen". Therefore: Liquid coins move immediately Reserve coins can move but must be frozen Frozen coins can not move All of those coin types can be staked and each one gets a different reward. Deliberately Frozen Liquid only for 4 months(40 coins) Frozen reserve or liquid(20 coins) Majority reserve in an input(10 coins) Majority liquid in an input(5 coins) https://www.docdroid.net/d5wcK4D/dynamic-peg-visual-technical-reference-20190528.pdfThat doc is what we send exchanges ^ So far the PDF is the best visual explainer we have. As for the "fix" in Halo in the advanced tab you can see the ability to do "Reserve Transfer" or "Voluntarily Freeze Liquid": The first freezes for one month getting the 20 coin bonus The second freezes for 4 months getting the 40 coin bonus Sending those freezes work right now but I overlooked an API command (listfrozen) thinking it should show up in listunspent. No big deal, just means Halo won't show or stake the frozen coins until I update it this week. Also I realize BitBay/Halo client needs better documentation so we will wait for enough feedback on what everyone would like to see to help them understand the peg client. I think the community should definitely organize the docs and materials we have for the peg. Because, we have a lot of good blog posts, learning materials but our community just doesn't have it all in one place like an FAQ. We should link such a thing on the site. |
|
|
|
We need to update that to be compatible with the peg. You could send to it but the funds may not show up at the wallet, you can instead export the private key to the QT for now until it's updated. |
|
|
|
|
Thanks, congrats everyone.
Also to the question about freezing, Halo batch freezes for you in advanced sending. I tested it however I'm missing an API command (listfrozen) I didn't realize Yshurik split those up so the frozen balance won't show until the next update which should be in a week. Of course you can still voluntarily freeze in Halo now. We may drop supply temporarily just to test all the features but before Latoken launch there is a good chance the community will raise it to zero so the crypto world gets to see it gradually progress forward. This is up for discussion.
My thoughts were, if coins are frozen too fast then the true liquid supply may be underestimated to cause a pump over the starting floor of 20 cents or overestimated and then coins may be sold at too high of a supply burning newcomers. However if we just let the peg do its "thing" supply and demand will gradually adjust in parity with volume and liquidity. At least that's my thoughts but I think we are a guinea pig for a very new system so there may not be any way to know what the liquid supply will be until some trading happens. It's anyones guess as to if liquid supply at 20 cents is only a few million dollars or even less or more. I wouldn't be surprised if it was slightly lower than current numbers because it would match the true liquidity and volume starting out. And there is nothing wrong with that because other communities quickly see our proven stability.
But maybe it doesn't matter either way. After all, this system is designed to be protected against speculation and manipulation. The algorithm that most people will vote with doesn't "think" it just adjusts supply to match the floor. Also as a community we might want to tweak that after we see the results. I would think that in most cases the community will do what makes the most sense for their positions. Voluntary freezing for higher stake maybe also has a cursory effect.
|
|
|
|
I'm using the latest market client (2.0). What is the difference between "Actual Balance" and "Available Balance"?
Actual balance is how many coins you have. Available balance is how many coins you can spend at that specific moment. Things that effect your available balance: *Coins may be reserved for contracts, so the software sets it aside *Some coins may be set in reserve due to the peg *Coins may be frozen due to the peg *You might have coins coming in on a stake or on a spent transaction For example, if you were doing a contract the software will want to set those coins aside so you don't use them for something else. This way, when a valid offer comes the software can automatically accept it. There are many different scenarios when the software can't or doesn't want to spend certain coins. Check the history tab and on the left hand side panel it should show you if you are staking coins, if you had pending contracts, or whatever the reason is for the discrepancy. It's possible you loaded the wallet unlocked, it found a stake, spent it and is waiting for it to confirm. A stake can take an hour or so to confirm. Also in response to time of fork it's very possible it will be within 24-48 hours. That was our target and I think we can fork at close to 65% of the network over. Since all of our major stakers are on the right chain. |
|
|
|
I'm not sure what I've done wrong but its all going a bit pear shaped.
I done the initial upgrade which was all good then I was prompted to upgrade again..then it got stuck at 2450882 at 99%.
Then I started a resync with the added new nodes and new boot strap now it stops at 40320 at 1%.
I'm thinking of uninstalling it and starting from scratch but i'm worried as ive got the wallet.dat the wallet-original.dat and I'm confused as fuck.
So David what would you do in my shoes and could you explain it in an idiot proof way as I'm shit with computers what I should do..cheers dude.
Well in Halo wallet the wallet.dat file only tracks transactions and your keys are key1.private and key2.private(only QT uses wallet.dat). Of course you can back up anything you want and should always have multiple backups of your keys. It shouldn't get stuck. However you can send your debug.log file to me via PM (that file is in bitbaydata directory). The bootstrap might not be loading properly or it could be busy doing something. You could try syncing from scratch if bootstrap isn't working for you. Even a new install is fine, if you do that just do a regular install, load your keys and sync. |
|
|
|
Im doing a resync and its going really slowly over an hour and still at 2%..I added the new nodes to the conf file (must you delete the old ones?) from chainz website.
Anything else I could do...or is this normal.
Thats possible, our chain has gotten pretty large. As long as the number of blocks keeps increasing it's fine. I know the team is updating the bootstrap but not sure when. |
|
|
|
Im doing a resync and its going really slowly over an hour and still at 2%..I added the new nodes to the conf file (must you delete the old ones?) from chainz website.
Anything else I could do...or is this normal.
Thats possible, our chain has gotten pretty large. I know the team is updating the bootstrap but not sure when. |
|
|
|
-snip
Just updated my QT wallet to v. 3.0.0 and it litterally took less than 5 minutes ( wallet.dat back up included).
How can I check if I'm on the correct chain and not on a fork of it?
Sorry for noobr question : may someone please provide me an advice regarding the bolded part? Well first you should be running the latest software. And then how to know for sure the best bet is to look at chainz and see what their block height is and compare it to yours. Sometimes it might be off by a few blocks and fix itself due to reorganization. But basically the way to know is to compare to other users. |
|
|
|
So remember everyone, if you haven't already please update to the newest Halo client or the newest QT(3.0). We are forking in a week. Not updating is bad and can put you on the wrong chain. Also we need as many people as possible staking since that helps secure the fork. |
|
|
|
ok...last question, I hope.......do I need to do a rescan?..........it seems to be stuck at 99%...I'm going to turn it off and on again, that's always a winner.
Not rescan, resynchronize. So remove files in bitbaydata except wallet.dat(for Halo) and if QT remove files except wallet.dat in the bitbay folder in appdata directory. Since if you got stuck on an orphan chain that would be the only solution. |
|
|
|
|
Show Posts
