0.015

We are upgrading open SSL just to be on the safe side, had to take the site down until this is completed.


http://heartbleed.com/

Understood. Thanks for looking into it, at least! I feel a bit better already! I am a very paranoid person. It's borderline psychotic.

How about coinroyale? Would love to be able to really see the provable fairness for myself as I am very paranoid!

Indeed, they made a LOT of BTC off of people such as mLiberty

Our development process is very different from most. We want to provide working solutions one by one than promising you the moon, and taking 3 years to deliver. In our first development run, you can run web nodes that sell bandwidth. These nodes sell bandwidth, and shuttle files around the network.

Lets say:
Node A: Is a node with 56 KBit/s and 1 TB storage
Node B: 10 MBit/s upload and 1 TB storage

Node A will be treated as a "passive" node, and Node B will be treated as an "active" node.

People will want to use Node B because of the faster speed. On the other hand, Node A, has 1 TB of unused storage. So people will upload files to Node B, and Node B will charge for bandwidth and storage. Node B has to maintain file redundancy in case it goes down, so it will buy storage space from Node A, and verify periodically through hashing that Node A is storing the correct data. Node B can also rely on other external services, or another decentralized network such as MaidSafe to physically store the files.

Node's B motive is to approach 100% saturation of its resources. So using Dropbox prices and 3x redundancy, Node B could generate about ~$150 a month. About half of this is from selling its hard drive, the other half is from reserving a small cache space and then shuttling uploaded files to other nodes and networks.

Node A would earn substantially less. It would serve as a very poor shuttle for data. Furthermore because of the low bandwidth, it would be very hard to achieve full saturation of the hard drive.

But wait, we still have a use for Node A. If we could pre-load Node A will files. Let's say tons of small < 100kb files that are slated for long term storage (lets say these are used on a backup application and probably won't really be accessed much at all). Therefore Node A would only have to pass hash verifications, and the occasional file transfer. It can also approach full saturation.

Makes sense but an option to back up each/all wallets would be nice.

You're right and that's a big question Rosplinpl!  RGBKey we are currently developing private key assignment to users as well as escrow and multisig.  These are my thoughts at a high level.

How you're safe from us: We have the highest level of proof of solvency available.  We use the Gregory Maxwell method of showing the total verifiable amount of user funds.  Any logged in user sees a leaf icon on their dashboard that shows their individual balance included in the hierarchical tree.  Independent auditors are great, we make every one of our users an independent auditor of our funds.

Further, we show the public addresses of our cold storage wallets so you can see the money exists on the blockchain.  You can see them here.  https://bitcoinwallet.com/resource.php

How we're safe from theft: We mandate all users to have 2FA and user data is encrypted.  Our cold storage is actually cold storage.  There is no automatic replenishment of the hot wallet.  We don't disclose our security at an infrastructure level but we know the pursuit of perfect security in the background never ends.

I encourage you to visit our site to see what we're doing, not because we claim to have solved every difficult problem, but because we're trying to make bitcoin more accessible to the mainstream.

Price
price.bitcoinwallet.com

Bounty offered to Mycelium developers

We are developping the BitID authentication protocol. Basicaly it's an open standard to facilitate user's registration in login on a service using its Bitcoin key (it could be compared to "Facebook connect" on the UX and flow). User scans a QRcode which contains a bitid:// URI, it's parsed for validity by the wallet and a confirmation is prompted. After choosing a Bitcoin address, the URI is signed and a POST is made in the callback addres contained in the URI.

For the full explication of the protocol, examples and demo please refer to our GitHub :
https://github.com/bitid/bitid

To be successfull, BitID must be implemented in most of the popular wallets. We would like to start the development with Mycelium (because it has already the signing message functionality). To motivate developers we are offering a bounty of 1 BTC.

What is needed to do :

• register the bitid:// scheme (so it is activated in case of click)
• throw a bitid:// intent when scanning a BitID QR code
• decode the URI and verify its format
• display a request for authentication showing the domain name callback and ask for validation
• ask the user to pick up or create a Bitcoin address for the authentication (show the last Bitcoin address used if this is a known callback address)
• sign the BitID URI with the private key
• POST the signature, the URI and the public key to the callback URL
• completion dialog : success/retry/cancel

Please PM me for more details and specifications.

Eric

Not really, I'd venture to say competition doesn't exists at this point and may not ever exist. They will all seamlessly integrate through APIs. After all you probably have a Facebook AND a Twitter right? You might have a preference, but still use both.

Our early supporters will get to play around with the web nodes. Those just get stuff working and allow you to play around with our platform.

Should not be a problem when we have our apps for that. We also plan on working with Maidsafe for the whole sell your hard drive part.

We have removed our whitepaper because we want to refine it a bit more. At least according to those numbers if you sold you hard drive at Dropbox prices you would make $2,000 a year off your 2 TB. You will be a very happy camper when we add proof of resource to Storj.

We aren't promising that quite yet as the computer science algorithms need a ton more work, but you might be able to run a web node (if you don't mind doing a decent amount of config) and make a nice sum of coins that way.