Quote from: kuroman on January 15, 2014, 01:14:14 AM

Interessting, If I understood correctly, this works Torrent, only difference is that this uses the experience acquired from cryptocurrency to provide privacy, to maintain the system working, and to award the users.

I see that the fondamentals are great and it's a rational idea, but I have several questions, from a technical standpoint, but I guess it's still to early now, as from what I read you guys still looking for devs and brainstorming

I look at it as a way of monetizing torrent streaming; at least for the WeTube DAC that will be built on top of BitCloud. We definitely want as many questions as possible to come our way because it will help us with the brainstorming process. There are too many different aspects of the protocol for us to handle on our own right now, which is why we're seeking devs.

Quote from: panonym on January 15, 2014, 01:19:06 AM

So it's the idea on paper, but no dev nor code?

Gonna read

Correct. We are searching for devs to help us turn this idea into a reality.

Quote from: jimhsu on January 15, 2014, 01:27:14 AM

Quote from: dance4x on January 15, 2014, 01:21:09 AM

Quote from: jimhsu on January 15, 2014, 12:35:59 AM

Basic questions:

1. Where is the data stored? How much redundancy? Obviously you need data to serve content.
2. How do you ensure that users are actually serving the correct data?
3. How will you validate the amount of data being served? (Imagine that an attacker controls both sending and receiving nodes. It would be trivial to fake the amount of bandwidth "used").
4. What types of data will you disallow? (This has many important legal consequences, as I'm sure you can imagine.) If everything is "allowed", I'd imagine most users unwilling to participate in fear of lawsuits/retaliation/subpoenas.
5. What is a "coin"? (unit of storage/bandwidth?) What is "difficulty"?

3. Nodes cannot cheat the system because there are multiple nodes sharing the same file. The node that the user connects to is chosen at random.

Edit: Decided to go ahead and answer number 3.

I assume this is a torrent-like scheme where files are broken into independent, verifiable (by hash) pieces, is that correct?

Storing data in nodes seems to assume unbounded storage space. How will you make sure that nodes actually have the requisite storage space? Particularly important for high bandwidth, storage constrained systems (I'm talking about VPSes, of course, which will probably be the source of the majority of the bandwidth).

It also seems like at least in the beginning, the system will not come close to even saturating bandwidth. In that case, what determines who gets block rewards? Random chance? Latency?

As of right now, the system is not breaking files into pieces. The nodes store the entire file. Multiple nodes have to be able to store the full file to make sure that nodes can't cheat the system. I haven't discussed breaking up files into parts with Liberman, but that seems like something that would make sense for larger moderators with a lot of nodes.

You are correct in assuming that VPSs will be the majority of the nodes. If the files on the nodes server don't match the file list from the moderator, they get dropped from the system. Having said that, I think your question points out the need for breaking down files into pieces. This system could work as long as the nodes were still chosen at random. We still have to make sure nodes can't cheat the system.

You'll have to wait for an answer from Liberman for your last point.

Quote from: ming08108 on January 15, 2014, 12:49:01 AM

Couldn't someone just share with themselves?

See point #3 from my previous post.