[ANN] Link - The Blockchain File Sharing Protocol
-
Kevlar, I think you did it better. With the exception of 0 and F, the 2nd byte F is the only one that needs to be explicitly describing the module itself.
So now there’s 15 OpCodes for each module.0 is the core, F keeps it tied together, 1 is for users. I claim 2 (20 - 2F) for FLUX.
EGGCELENTE.
-
There’s no one else doing this lol. I love it. They’ll be cloning us soon.
-
Kevlar, I forked the suppository. I’ll be working on Modules.md and modules/FLUX/README.md. Goosebumps.
-
[quote name=“Tuck Fheman” post=“41448” timestamp=“1386477154”]
If there will exist categories, will they be handled via the keywords?
[/quote]Categories are something that can be left up to the users to define. For instance, they could make a special keyword that starts with a #, and whatever follows it is a category… “#tucksporn”. Then it’s up to the client how they want to deal with organizing them.
[quote]
(source file) File type.
(source file) File size.
[/quote]Included and included! 8)
[quote]
A few “Arbitrary user-defined meta-data” to be used as users please. Possibly to cover the three above.
[/quote]Included! 3 for 3! :D
[quote]
Edit : What about the ability to make these private? Sure the source file can be encrypted, but what about allowing entries to be private (password protected or otherwise) or the ability to designate who the source files are made available to be it individuals or a group or a continent, etc.
[/quote]Well, it’s the blockchain. You can’t specify who can/can’t see the blockchain. Encryption is the correct solution.
-
[quote name=“zerodrama” post=“41449” timestamp=“1386477214”]
I’ll take #2 for Flux. I’ll play with some kind of module registration steps but we are go. o/.
[/quote]Perfect. :) 2 is reserved for Flux!
[quote author=zerodrama link=topic=5558.msg41457#msg41457 date=1386478519]
Kevlar, I forked the suppository. I’ll be working on Modules.md and modules/FLUX/README.md. Goosebumps.
[/quote]Awesome! Very excited. ;D
-
[quote name=“Kevlar” post=“41459” timestamp=“1386479163”]
“#tucksporn”
[/quote]lulz
[quote author=Kevlar link=topic=5558.msg41459#msg41459 date=1386479163]
Included! 3 for 3! :D
[/quote][Celebratory GIF]
-
Ok! Meta-data is done, sequencing is done, and the first example test sequence is done! How exciting! Go check it out!
I’m going to do one more example sequence, then I’m going to encode it and send it to the blockchain! I’ll keep you posted!
I need a torrent to encode for the next example. Specifically a magnet link. Does anyone have any suggestions?
-
[url=http://thepiratebay.sx/torrent/8188870/TPB_AFK__The_Pirate_Bay_Away_from_Keyboard_(2013)_720p_h264_581m]http://thepiratebay.sx/torrent/8188870/TPB_AFK__The_Pirate_Bay_Away_from_Keyboard_(2013)_720p_h264_581m[/url]
-
I think I’ll take on the job of cheerleader.
You guys are doing awesome!
[img]http://www.totalprosports.com/wp-content/uploads/2012/03/cheerleader-gifs.jpg[/img]
-
Just reading about this guy:
[url=http://datacoin.info]datacoin.info[/url]
Looks like a similar - albeit different concept.
-
That looks like it would be one giant chain. Please forgive this question, because it’s been birthed in a pool of total ignorance, but would a file sharing blockchain suffer issues from a ballooning size? I know there has been mostly technical discussion here, so if its been addressed or is irrelevant, just pat me on the back and give me a sugar cookie.
-
[quote name=“Nixxle” post=“41910” timestamp=“1386564560”]
That looks like it would be one giant chain. Please forgive this question, because it’s been birthed in a pool of total ignorance, but would a file sharing blockchain suffer issues from a ballooning size? I know there has been mostly technical discussion here, so if its been addressed or is irrelevant, just pat me on the back and give me a sugar cookie.
[/quote]Yes it would.
Link protocol simply makes torrent files available.
Flux will enable massive file storage.
-
[quote name=“Nixxle” post=“41910” timestamp=“1386564560”]
That looks like it would be one giant chain. Please forgive this question, because it’s been birthed in a pool of total ignorance, but would a file sharing blockchain suffer issues from a ballooning size? I know there has been mostly technical discussion here, so if its been addressed or is irrelevant, just pat me on the back and give me a sugar cookie.
[/quote]No… blockchains with lots of usage suffer from a ballooning size. When you embed Link in the blockchain, you destroy coins, meaning you’ll NEVER send them again. That means you’ll NEVER grow the blockchain with those coins again.
-
Ha! I did it.
Wrote up a program in Node that accepts the magnet link, name, and keywords, and generates the addresses. The code is in github here: https://github.com/TSavo/Link
You can even check them on blockchain.info, and see the link encoded message!
[code]
C:\NodeLink\NodeLink>node LinkAddressMaker.js
What is the magnet link? magnet:?xt=urn:btih:fbab636f9c91fb58038055dfce83cd8099a
7366e&dn=TPB+AFK%3A+The+Pirate+Bay+Away+from+Keyboard+%282013%29+720p+h264+581m
What is the name?TPB AFK: The Pirate Bay Away from Keyboard (2013) 720p h264 581
m
Keywords?TPB AFK,The Pirate Bay,Away From Keyboard,Simon Klose,Documentary,720p
17y2f5PYdSwFhzPTjPpMTVmZVTsttnpzk9
1B3qGjZ9SeqtuTcddSk5GHBry8BQnpRDWz
19xGyZ8rM6BxouZH6NDRVpJr4dkwrCfZ2M
16EPybUXLYBsUvPGCjNYdvPh8V5SnACDYY
16waq56MzXV8RKtA4x8XB34MLcJZHAEiTv
1C3gki8S17uBbE8WTnkKe1ciihEJvSphn9
15PpNfoKrEqwFoEPo8maqgUJM5Wfwe9vBe
1AwfpgH8E6c4K273EVsd4jNY7oheZybKZz
19tHysnPeZZuiXsxwBGxzuxsXzPEjWxBz9
1C4pgbr41jxhfWpVEkvHGSih5eRGUiWjDy
15aVij3HUiLfCwKz7mEroiFQbsYqkAUjKZ
1AWzRKnFNC6y5QLSngBMc4JDGM2AMbJAog
1BS5WuK3FynDCSjQpAwE2HAT9MwHmnCeGn
1AtMVTEx3eduyjRvAcUhok4Gsd3YjsZdGy
1BDCgV8ZgmTFz18ASzmhiJgXqbYuxPToBr
[/code]Try putting that first address into blockchain.info. Not only is it a valid address, but if you look at the hash160, you’ll see the Link protocol in action!
[code]
4c696e6b0100866d61676e65743a3f78743d7572
^^^^^^^^ Link Start sequence
^^ Inline payload op-code
^^^^ size
^^^^^^^^^^^^^^^^^^^^^ The magnet link (well, the first few bytes)
[/code]Ooooooooomg so exciting!
Ok, next up is to do it with Feathercoin addresses, and then to actually send the transaction using your donated coins.
But for that I need to know: What’s the Feathercoin version number? Bitcoin is 0x00 for mainnet. What’s FTC’s?
-
[img]http://whinybaby.files.wordpress.com/2013/04/mind-blown.jpg[/img]
+1 rep
and
110 ftc coming your way.[img]http://image.bayimg.com/2b719c8bc91b2374fe431bf2e7c73d60bcd26f47.jpg[/img]
[size=8pt]Sorry, tried to cut or hide or spoiler but I couldn’t figure out how. If someone can give me the BBcode, I’ll fix this… or simply just remove the screencap.[/size]
-
Ok, I spent a bunch of time cleaning up the code.
You can now do:
[code]
var sequence = new LinkSequenceBuilder();
sequence.addPayloadInline(magnet);
sequence.addName(name);
sequence.addKeywords(keywords);
var buf = new Buffer(sequence.toString(), “hex”);
var addresses = encodeAddresses(buf, 0x00);
for (x in addresses) {
console.log(addresses[x]);
}
[/code]Which I think is a whole lot cleaner than my first pass. Bushstar just got back to me with the version number for Feathercoin so I’m gonna give it a try here in just a few…
Edit: Tried it out in the code… looks pretty feathery to me!!!
[code]
C:\NodeLink\NodeLink>node LinkAddressMaker.js
What is the magnet link? aaaaaaaaaaaa
What is the name?aaaaaaaaaaaa
Keywords?aaaaaaaaaaaaaaa
6khUSbZaZtMv7czsXDqxWKgKTxofTBbtzY
6djhcj3jj1v97miAFqNZ97Vzdaqw1RCTQS
6ncLzEh3A1MJ3G7CkakETFdLwE3h93Aa1z
[/code]I’m going to give it a try… wish me luck!
-
[me=Calem]wishes Kevlar all the luck possible![/me]
-
So it ALMOST worked using the client.
Unfortunately the client stuck the change address in the middle of the sequence:
[url=http://ftc.cryptocoinexplorer.com/tx/cc66ef78c1bcfbaf2a691b3dda77847bc80350ad262f17af38f7950879ecaef2#o2]http://ftc.cryptocoinexplorer.com/tx/cc66ef78c1bcfbaf2a691b3dda77847bc80350ad262f17af38f7950879ecaef2#o2[/url]
Bummer. Owell, this simply means I’ll have to write my own client to do the sending so it always gets the sequence in the right order.
OMG I’m so excited that this almost worked. If you ignore that change send, you can see it totally did exactly what it was supposed to!!!
Tomorrow I’ll work on some code to reverse the process and read them back out of the blockchain. It’s pretty straightforward actually. ;D
-
Hi five!
I’ll be watching with anticipation. This seems to be the most awesome idea I’ve seen pitched for the use of the network to date.
100% Behind you Kevlar!
-
astonished :o
