Topic: Belacoin - Supercharging entrepreneurship with the power of the blockchain - page 21. (Read 379808 times)

I think bella will cross 20k at the end of this month.

This is the kind of transparency that the developers maintain.Ambia is fully committed and focused on what they are doing.This is definitely a good sign on bela part and the investors shall surely be benefited by their belief in bela team

If I'm not mistaken, you should store wallet.dat file not only in one secured place to avoid your problem.

Securing the Bitcoin-Qt or bitcoind wallet
Bitcoin transactions send Bitcoins to a specific public key. A Bitcoin address is an encoded hash of a public key. In order to use received Bitcoins, you need to have the private key matching the public key you received with. This is sort of like a super long password associated with an account (the account is the public key). Your Bitcoin wallet contains all of the private keys necessary for spending your received transactions. If you delete your wallet without a backup, then you no longer have the authorization information necessary to claim your coins, and the coins associated with those keys are lost forever.

The wallet contains a pool of queued keys. By default there are 100 keys in the key pool. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.

Creating a new address generates a new pair of public and private keys, which are added to your wallet. Each keypair is mostly random numbers, so they cannot be known prior to generation. If you backup your wallet and then create more than 100 new addresses, the keypair associated with the newest addresses will not be in the old wallet because the new keypairs are only known after creating them. Any coins received at these addresses will be lost if you restore from the backup.

The situation is made somewhat more confusing because the receiving addresses shown in the UI are not the only keys in your wallet. Each Bitcoin generation is given a new public key, and, more importantly, each sent transaction also sends some number of Bitcoins back to yourself at a new key. When sending Bitcoins to anyone, you generate a new keypair for yourself and simultaneously send Bitcoins to your new public key and the actual recipient's public key. This is an anonymity feature – it makes tracking Bitcoin transactions much more difficult.

So if you create a backup, and then do more than 100 things that cause a new key to be used, and then restore from the backup, some Bitcoins will be lost. Bitcoin has not deleted any keys (keys are never deleted) – it has created a new key that is not in your old backup and then sent Bitcoins to it. A backup is therefore recommended roughly every 50 transactions (or address creations) just to be safe.

Hey guys. What would be the best way to store my BELAcoins? I want to keep a significant amount for later to see what the coin does, but they're all on exchanges now. If I download the desktop wallet, but my PC crashes.... than what? Will my coins be lost?

Cheers!

Today, we're working on finishing up some design work on various pages and continuing the process of linking the deposits and withdrawals to an automated wallet. After that, the rest of the work is smaller but tedious things, like integrating the user search and the tag search into one search bar, making it so tags are clickable when written in a comment, and other things like that.

We also just received notice that the partner from Kleiner Perkins had to cancel due to scheduling issues. This means is that we won't be pitching on the 13th anymore. We will be aiming to do some pitches later this month and in May though. Without having to worry about preparing for the April 13th pitch, our team can be laser focused on delivering a great Belacam open beta launch. We will also now have time to get feedback and improve the site before we do our next pitch, which increases our chances of success when we do get around to more pitches.

Were all havin the same issue. Its just a diff retargeting thing

We became a sensation over night and the major mining player's directed there asics at us along with the multipools. When people freaked out about VC thing been delayed, the price dropped. Because of that, that insane amount of network hashrate was redirected elsewhere. The BC is just in the process of crunching out the current  block ans when this heppens, all the transactions will take place. There's absolutely nothing to worry about as your coins are safe as they could be in your wallets. The exchanges are no different but trading can still occur as they use offchain methodes to keep things moving.

None of this will be a problem soon enough though as we will be updating to litecoins latest Core along with segwit.

Fear not, we are aware and on top of it.

Is everything okay with the BELA chain?
Our daemon and the BELA explorer have been stuck on 664,377 for quite a long time.

KPCB deal is dead? Okay.

Guys I have some clarifications regarding KPCB investments. For example they want to buy/own 20%. Does it means they will buy 20% of the 33 million tokens?

BELA added to hash-to-coins.com
All miners are welcome