Bitcloud is going to be based on Tahoe-LAFS

[Javier R. Sobrino]

On 03/02/14 19:34, Ben Laurie wrote:
> Cool. I dug a bit deeper, and in
> https://github.com/wetube/bitcloud/blob/master/Bitcloud%20Nontechnical%20White%20Paper.md
> I notice you talk about cloudcoins, based on proof-of-bandwidth.
>
> This is a scheme I can approve of, given that coins are generated by
> doing something useful, rather than just heating up the planet.
>
> But ...
>
> a) What are cloudcoins useful for? Is the idea that they'll magically
> acquire value, like Bitcoins do?
>
> b) What about proof-of-storage?
>

Hi Ben!
In our original idea, Bitcloud was going to be a DAO, that is, it was
going to have a blockchain.
But now, we are separating Bitcloud, which is going to be just the
protocol, form the DAOs going on top of it. For example, Wetube is going
to be a DAO and an interface for Bitcloud, and there is where the
business is going to happen.
In that sense, Bitcloud is going to be the protocol serving statistics
so individual DAOs can construct an economy around it.
We are updating the papers these days, as they have become obsolete.

Let me paste here what is going to be Bitcloud. Bassically it is just a
super-set of Tahoe-LAFS, a modification of it to become the base for
DAOs needing to use storage:

Bitcloud provides a method for storing data in a distributed collection
of nodes or meshnetwork and is comprised of these main components:

 1. A method to reliably distribute data across connected nodes using
    Bitcloud, with the potential to scale up to millions of nodes.
 2. Hot plug-in/plug-out of nodes.
 3. Safeguard of the data, such as given N number of nodes, only N/3 of
    them are needed to provide the complete file.
 4. Fast parallel reconstruction of files.
 5. QoS measurement of individual nodes and node grids, with statistics
    stored in a node pool file.
 6. Automatic Certificate Authorities (CA) management, for secure
    reliable connections.
 7. Each node and user is associated with a CA managed by a gateway or
    publisher.
 8. Difficult generation and global acceptance of CAs encouraged by a
    reputation system.
 9. Secure encrypted storage in such a way that individual nodes cannot
    know what they are storing by simple prospecting into the data.
10. Arrangement of the nodes in grids, each grid providing specialized
    content storage for contract publishers.
11. Both public and private grids can coexist.
12. The public grid is the collection of all the nodes in the entire
    Bitcloud and its content cannot be censored.
13. Private grids are managed by publishers, in charge of curating the
    content.


So if you are interested in the ideas, just let us know. I think we have
a great opportunity here not only to boost Tahoe-LAFS ideas, but to
become the new revolutionary protocol of the new Internet that is coming.
As we are a high level protocol, nothing impedes us to base Bitcloud on
TCP/IP routings, but also on future meshnetworks protocols.
I think Tahoe-LAFS uses a meshnet topology, it only needs to be improved
a bit (like including CAs and publishers) and we can success.

Let me know if you're interested. Of course all participants will be
appropriately credited and be part of the funding process, when it comes.

Best regards,

Javier.