FrozenBytes - A decentralized File sharing cryptocurrency network

[FrozenBit]

  LIKE THIS IDEA OR FROZENBIT?

DONATE: 15yqW7NaGUbq1B3WZ6Th1m1XNaMaiSzHar
https://blockchain.info/address/15yqW7NaGUbq1B3WZ6Th1m1XNaMaiSzHar
 BALANCE: 0.15

  We'll over the last few months I've been working on a project called FrozenBit. It's a trustless multi signature crypto-currency security platform > https://bitcointalk.org/index.php?topic=673533.0
 
Now the frozenbit is nearing completion I thought I'd share my second Idea with the community.


 We'll I wanted to run by the community, which has greatly supported my last project, another project idea I had.

FrozenBytes [because once's it's uploaded it'll never go away] (Name can change don't get mad at this plz) A decentralized file sharing platform.



The goal is to create something like openbazaar but based on the mechanics of the pirate bay.


 ACQUISITION OF PLATFORM:

 The platform will be downloaded and run like a qt wallet. Users will download the "blockchain" all the files currently uploaded. The wallet qt will not vary from other qt's except no currency will be used (CONTINUE READING BELOW TO SEE WHY). WILL ATTEMPT TO INTEGRATE PRIVACY TOOLS.

 Alternatively other methods can be examined if file pool reaches extremely high levels.





FEATURES OF THE PLATFORM:

 The platform will easily include upload and download. It'll also contain a search, and INSTEAD OF LINKS WHEN A FILE IS UPLOADED IT GENERATES WHAT IS EQUAL TO A TX HASH. This hash is what will be the "link" to the exact file. We could also integrate store front features and have a currency integrated. That way people can easily sell music and such for money. Effectively creating a way for people to profit off of their music/movies/ whatever via crypto currency.  (BASICALLY HAVE A LOCK PAGE AND SAY "SEND XXX CURRENCY TO ADDRESS", WHICH EFFECTIVELY WILL BE USERNAME)

 JUST REALIZED THERE COULD ALSO BE METHODS TO MAKE IT HARDER TO PIRATE PAID FOR STUFF. We could entirely encode stuff with the tx. If a file has that tx byte or whatever still in it we could have stops in place to prevent it from being re-uploaded. A better system of creators protection (Blah blah blah fuck copyright... Don't care... These are ideas roll with it.)

 Also to prevent people from downloading what is effectively 100% porn we could include previews for songs/images?



NOTE SAME STEPS CAN BE TAKEN WITH NON-PAID FILES

WALK ME THROUGH IT:

 You'll start out by downloading the client, which I want to be available via mobile (an app would be preferred), windows, linux and mac

 Next you'll allow the blockchain to sync

 Once this is done you'll see your username (ADDRESS) and password (PRIVATE KEY) you'll use this to login. P.S. I just effectively made it theoretically impossible to hack accounts.

 Next you'll want to upload something, so you'll see a tab saying upload. You'll click that it'll ask for info (keep in mind this is a bitcoin qt type client) about the file and you upload [only things like name, artist etc.]

 It'll then ask you about making it paid, which you'll say yes because you worked hard on this song.

 Then the file will upload and it'll generate a "Tx" which will be the link allowing you to share this file.

 Since it's paid it'll have the send xxx to download lock over it.






NOW I'M A PERSON WHO WANT'S THIS FILE:

 I'm buying from my favorite artist who's name is calvin and goes by the the address of 1satoshiscousinssitersunclesroommate . I heard he released a new song, and I want it.

 I see his tx on his website is

 wowsuchcurrenymuchfilesharewow

 I enter this into my client to find "To download file sent xxx frozenbyte coins to 1satosh............" (which remember is his username)

 I then can download this song, I paid the artist and am starting an ecosystem all within it's self.





 I WANT TO KNOW WHAT YOU THINK! I ALSO NEED YOUR HELP! EVERYTHING HERE IS BASICALLY THEORETICAL AT THIS POINT, HOWEVER, I WILL BE UPDATING WHITE BLUEPRINTS AND DESIGNS ABOUT HOW IT WILL WORK/DESIGN.




LIKE THIS IDEA OR FROZENBIT?

DONATE: 15yqW7NaGUbq1B3WZ6Th1m1XNaMaiSzHar
https://blockchain.info/address/15yqW7NaGUbq1B3WZ6Th1m1XNaMaiSzHar

 BALANCE: 0.15

 Want to learn more?

IRC: #frozenbit
EMAIL: calvin@frozenb.it
twitter: twitter.com/frozenbitio

[digitalindustry]

I love that you persist here on this dead forum (its cute) - but this project is an awesome innovation.

use this topic to link others -

the real Crypto community should get behind this.

do you have a Proton email account in the works, the "Police state" will want to know how you plan to do this.

[DarkFox]

Hello,

As I said on IRC, this is a great idea; but scalability is a huge problem.

" FrozenBytes [because once's it's uploaded it'll never go away] (Name can change don't get mad at this plz) A decentralized file sharing platform. "

Never? Frozen alright... Free upload? Trivial to fill the network's storage capacity essentially creating a DoS attack that can only be revived by (1) restarting [lose all the files] or (2) expanding [how much can you expand with an active attacker always uploading junk?]


" JUST REALIZED THERE COULD ALSO BE METHODS TO MAKE IT HARDER TO PIRATE PAID FOR STUFF. We could entirely encode stuff with the tx. If a file has that tx byte or whatever still in it we could have stops in place to prevent it from being re-uploaded. A better system of creators protection (Blah blah blah fuck copyright... Don't care... These are ideas roll with it.) "

Yea... No. If someone wants to reupload a file; they simply need to change any single bit they desire. If this is an image or a song, most of the bits may be flipped to bypass the basic deduplication from the hash function.
This could be changing a colour from #000000 to #000001, the user can't see any difference. Another method that the pirate may use without affecting the quality, would be to simply add null padding to the end of the file.


" Also to prevent people from downloading what is effectively 100% porn we could include previews for songs/images? "

Should the uploader decide to include previews, there is no way to know that the "thumbnail" or cut down audio track are even the original file.

With a song, however, you may reduce overhead of another copy by splitting the content. Below, k1 = public, k2 = premium (pay-for).

90 second song = decrypt(k1,[30 seconds]) + decrypt(k2,[60 seconds])

Here, there is no integrity for the last 60 seconds, the user may check the first 30 and it may be the right song and they pay, to find the 60 seconds were fake.


" Once this is done you'll see your username (ADDRESS) and password (PRIVATE KEY) you'll use this to login. P.S. I just effectively made it theoretically impossible to hack accounts. "

Username = public key
Password = private key

Oh, so no username; as the public is derived from the private. The public identifier for the user is simply addressable. The point here, is that the file isn't protected by both user+pass, but instead just pass. Where this key is only a 256-bit key.
Yes, yes, 2^256 is a good keyspace for a secure key and it does scale well. I'm just clarifying this here, it's only 2^256, not 2^256+2^160 (private+public). Should the curve and keyspace ever in the future be broken (so far; we don't know any effective attacks*) then all data would be public to all (and we can't delete it \o/).

Theoretically? No. Cryptographically, maybe? Such that you define something cryptographically secure by the fact that it's computationally difficult enough that it would take an aweful lot of time (I.e. 10s of years)

*: A brute force attack isn't effective, it's iterating over every possible key (slow), an effective attack would involve reversing the math; which with ECDSA on Bitcoins' curve of choise secp256k1 is currently cryptographically secure.


Payment..... Lets just talk on IRC about this.

• Alice pays bob for content.
• Bob must be online to confirm to send alice the secret; this is worse then an unseeded-torrent.
• If the network can send alice the key without bob; then Alice can do the same without the network

Cheers, DarkFox.

[FrozenBit]

Hello,

As I said on IRC, this is a great idea; but scalability is a huge problem.

" FrozenBytes [because once's it's uploaded it'll never go away] (Name can change don't get mad at this plz) A decentralized file sharing platform. "

Never? Frozen alright... Free upload? Trivial to fill the network's storage capacity essentially creating a DoS attack that can only be revived by (1) restarting [lose all the files] or (2) expanding [how much can you expand with an active attacker always uploading junk?]


" JUST REALIZED THERE COULD ALSO BE METHODS TO MAKE IT HARDER TO PIRATE PAID FOR STUFF. We could entirely encode stuff with the tx. If a file has that tx byte or whatever still in it we could have stops in place to prevent it from being re-uploaded. A better system of creators protection (Blah blah blah fuck copyright... Don't care... These are ideas roll with it.) "

Yea... No. If someone wants to reupload a file; they simply need to change any single bit they desire. If this is an image or a song, most of the bits may be flipped to bypass the basic deduplication from the hash function.
This could be changing a colour from #000000 to #000001, the user can't see any difference. Another method that the pirate may use without affecting the quality, would be to simply add null padding to the end of the file.


" Also to prevent people from downloading what is effectively 100% porn we could include previews for songs/images? "

Should the uploader decide to include previews, there is no way to know that the "thumbnail" or cut down audio track are even the original file.

With a song, however, you may reduce overhead of another copy by splitting the content. Below, k1 = public, k2 = premium (pay-for).

90 second song = decrypt(k1,[30 seconds]) + decrypt(k2,[60 seconds])

Here, there is no integrity for the last 60 seconds, the user may check the first 30 and it may be the right song and they pay, to find the 60 seconds were fake.


" Once this is done you'll see your username (ADDRESS) and password (PRIVATE KEY) you'll use this to login. P.S. I just effectively made it theoretically impossible to hack accounts. "

Username = public key
Password = private key

Oh, so no username; as the public is derived from the private. The public identifier for the user is simply addressable. The point here, is that the file isn't protected by both user+pass, but instead just pass. Where this key is only a 256-bit key.
Yes, yes, 2^256 is a good keyspace for a secure key and it does scale well. I'm just clarifying this here, it's only 2^256, not 2^256+2^160 (private+public). Should the curve and keyspace ever in the future be broken (so far; we don't know any effective attacks*) then all data would be public to all (and we can't delete it \o/).

Theoretically? No. Cryptographically, maybe? Such that you define something cryptographically secure by the fact that it's computationally difficult enough that it would take an aweful lot of time (I.e. 10s of years)

*: A brute force attack isn't effective, it's iterating over every possible key (slow), an effective attack would involve reversing the math; which with ECDSA on Bitcoins' curve of choise secp256k1 is currently cryptographically secure.


Payment..... Lets just talk on IRC about this.

• Alice pays bob for content.
• Bob must be online to confirm to send alice the secret; this is worse then an unseeded-torrent.
• If the network can send alice the key without bob; then Alice can do the same without the network

Cheers, DarkFox.

 Thanks, I hope to work with the developers and YOU on the IRC to fix some of these issues.

 Likewise REMEMBER SOME OF THESE ISSUES ONLY AFFECT STORE FRONTS.

 And the antipiracy thing isn't perfect, just thinking of ways to maybe make a more stable environment of non-duplicate files.

[FrozenBit]

 Thanks for everyones help thus far. If you'd like to help, please message me on forum or leave a comment on this topic.

 There are a few kinks/bugs to work out, but I'm 100% sure we'll be fully able to complete this project by next February WITH the help of YOU.

[FrozenBit]

STAY TUNED FOR MORE INFO COMING VERY SOON.

[jjgallow]

" Also to prevent people from downloading what is effectively 100% porn we could include previews for songs/images? "

I'll say it.

Why would you want to prevent this?

Serious question.