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

please do your homework and think again if you did not understand what I wrote.

The price is definitely protected! And, it's very real. It's not a "magic meaningless number".
Please do your homework...

The price in this case is not protected, it is artificial, just some magic meaningless number as long as 99.5% of coins are frozen.

3-4 years? Like Craig was saying almost 7! This was the original feature promised since BitBay started. Not to mention the pages and and pages of text talking about it since it's inception. Also it's fully democratic and a user can still trade their reserve. So it's not true to say coins are "frozen" against anyones will. They are more than welcome to sell their BAYR and I'm sure users would love to scoop up a majority of the BAYR at a discount.

Besides, I would rather sell 1% of my bag for what is already 10x of the previous bottom than to have no price protection whatsoever.  

Also with liquidity this thing can sky rocket because the economy can inflate because it's super cheap to buy up all of the liquid coins at this point which would push the peg over it's target forcing it to inflate. Not to mention a trader can buy up reserve and sell it at a premium when it converts to liquid. So much strategy involved and I feel like it takes trading to another level.

We've had the dynamic peg on our roadmap since the launch of the coin back in Nov. 2014
We've had whitepaper released on the dynamic peg since 2018

You can still sell your reserve coins. You simply have to wait for 1 month time lock to expire before the exchange can allow you to trade.

The reserve market on the exchange will be selling at a sub premium price obviously. Yet due to the timelock protocol, the exchange can run into supply bottlenecks even for the reserve coin supply.
This is beneficial to the price for those that can already sell reserve coins on exchange.

@donarito - Where have you been the last 3 or 4 years? lol
BAYS Homepage 2nd Paragraph - "BitBay’s Dynamic Peg is purely decentralized, allowing every participant to vote on which direction the price may go."
-We have voted to decrease the amount of "supply" to protect our price.
Also
BAYS Homepage 3rd Paragraph - "Every user has two balances of $BAY, liquid and reserve. During a price crash, stakers can collectively vote to “freeze” a portion of the entire liquid supply. This decreases the supply of everyone’s remaining liquid coins."
-Right now, the supply is about 0.5%. So the Peg is working just as intended - to protect our value.

Therefore, your coins will be unfrozen (like the rest of us), when we vote to increase the supply.
Your coins are not frozen against your will; as much as they ARE frozen as a result of everyone else's will.
This is the beauty of our Dynamic Peg.  PRICE PROTECTION against pumps and crashes. Cheers!

guys, I went through all things here but still do not understand - I have some amount of frozen coins, and only about 1% of liquid coins. When my coins are unfrozen? I do not think it is fair that my coins are frozen against my will. Taking into account that they are on a wallet since 2017 or 2016.

Hi everyone we have a good solution to avoid future splits using a reputation system. This can effect any coin, for us it was just bad luck. We post a patch shortly. In the meantime you can keep up with one of the main chains via bootstrap.

** Important update **

The team has found an additional layer of complexity to the "split-chain" issue, and we must ask you to wait a little longer for an updated solution. We want this fix to be as easy as possible for every user, so everyone can be on the correct chain. Please note: This issue will not effect your balance, and all coins are safe. If you are currently staking on either chain, please continue to do so; however, we recommend that you not send any transactions until the next announcement.

Thank you for your patience, we will have another update for you soon.

Another easy way to check on the Market Client if you are on the right chain or not (if you are staking):
On the dashboard see what your “Actual Balance” is. Make a note.
Then go to: https://chainz.cryptoid.info/bay/
Find your address on the “Rich List”.
If your “Rich List” amount of Bay, if you’re staking, is LESS than the amount showing on your personal “Market Client Actual Balance” – Then you are on the right chain.
If your “Rich List” amount of Bay, if you’re staking, is THE SAME as the amount showing on your personal “Market Client Actual Balance” – Then you are on the wrong chain. Please follow the advice above to resolve.

Here are directions on how to identify which chain you are on, and update to the correct one if needed:

Markets Client:
https://forum.bitbay.market/t/how-to-identify-and-resolve-the-split-chain-issue-from-03-23-20-markets-client-version/2301

QT Wallet:
https://forum.bitbay.market/t/how-to-identify-and-resolve-the-split-chain-issue-from-03-23-20-qt-version/2300/2

I can confirm the above info is true. This also should explain why some users transactions didn't show on Latoken. We will of course favor the version of the split that Latoken is on. We are preparing a patch in the meantime. Let this be a reminder to everyone to always stake when you can to support the network. We will push a patch for when there is limited stakers. In a nutshell this happens when chain trust vs chain length causes two factions of similar sized groups of stakers to split. It happens when difficulty is the same and an adjustment can not solve it. Therefore it happens when only a few people stake. There is no good solution without compromising the proven and tested staking logic. However I have a few ideas of how to handle this when there are not enough stakers as we can follow trusted stakers in an order only when small split conditions are met.

So, if your most recent block hash matches chainz then you are on the wrong chain and should resync like above instructions says. It's critical this be done with bootstrap to avoid accidentally being on wrong side again. You may also notice chainz block height is not the same as yours. Perhaps you are 5-10 blocks ahead of them for example. That would be evidence you are on the correct chain but you should ALSO make sure by checking a recent block hash of theirs to see if it shows up in your chain. I think also you can use block explorer in QT to search for recent chainz block.

Sorry for the inconvenience. And if you sent a TX to Latoken and it didn't confirm on the exchange, don't worry. When you resync those coins will be back in your wallet and you can simply submit the transaction again once you are on the correct side of the split. If you are a major staker, contact me to make sure you are indeed on the right side of the split.

Also:

To find out what side of the split you are on, you can do the following:
For client  enter this command in debugger:
text=str(BLK.getblock("3e5b4548be900aa721f56815eda345ebec9f9e1bd81a3fb3b4a8c1839ef38b3d"))
If it doesn't return a block or says that block isn't found its busy and just try it until it gives either that it wasn't found or it was found. If its found you are on wrong side.
For QT try getblock 3e5b4548be900aa721f56815eda345ebec9f9e1bd81a3fb3b4a8c1839ef38b3d
if it returns block, you are on the wrong side.

From the team:

"We have found a split in the blockchain. Please do not send any Bay while we investigate. Also please keep staking.

So, by the looks of it there will be a two-step fix. First we focus on getting everyone on the same side. That would be the Latoken side of the chain. While we do that, David and yshurik will work on an update that prevents this from happening again. We have a bootstrap for you that will take you to the right side https://github.com/bitbaymarket/bitbay-bootstrap/releases/tag/v1
Everyone that is in sync with chainz download that and follow these instructions:
1. Stop client/wallet
2. Backup wallet.dat / keys
3. Remove all files in data folder except wallet.dat (and testnet/ if testnet was used)
4. Place bootstrap.dat in data folder (for client) or data dir (for Qt wallet)
5. Start client/wallet
6. Wait 2-4 hours"

Don't look now, but BAY is leading the seven day moving average (+381.6%) on CoinGecko's 1st Page by a GiNormous amount!
...And ranked 79th I might add. Quietly.

David's Dynamic Peg is working beautifully to stabilize the price - on the way up...
Reminder - David Zimbeck was the 1st person in history to make a smart contract (bit halo) non-theoretical, before Ethereum.

We still need more volume. I do believe it will start to manifest here shortly.

We've come a long, long, long way since late 2014!
Congratulations BAY Team!!!
2020 is our Year Zero.

Thank you everyone for your help, all clear!

QT and Markets/Halo wallet are not compatible. Halo is multisig (2 keys) and QT uses single key.
Also your Markets/Halo wallet must be updated to the newest version (2.2)
There is an updater on the website

There are new versions of the wallet. You will need to update to access the current chain...

In Halo 1.37 my wallet was created from these 2 pairs:
key1.private
key1.share
key2.private
key2.share

Now I am trying to use the QT wallet and I would like to import my account from Halo 1.37, is there a way to do it? It seems that it automatically created a new seed as soon as I opened it

I fully agree. The timing is quintessentially PERFECT.