For some days I've been posting in the ANN subforum about a new approach I've been working on, a blockchain protocol inspired in (the computational abstraction of) biological processes. As ppl there seem to be more concentrated on "getting rich, fast" undercurrent of ICOs, pre-ICOs, and the lot, decided to slightly change the tune by posting here. It might even prove useful to detect a weakness in the protocol..!
The example below represents a strand of the Genetic Blockchain, encoding 5 separate bonding sites, or equivalently, enabling 5 GenS (our Tokens) to be recognized and transact. If you read the presentations you'll know what's all about.
183933811891895175126234591221258156984322212014110755103156170172651
007118716216217620416110143244238108248126196965779271161456310071169
204214811951781891001948032482342524869151132138120102253135105160114
280208401552076214923645158159128677226944017910517202991651142251212
104211230140136171124216561432555525173237142572521792392040181402164
217613311772213301612312032512173141424311940459126442175128240141160
132171301891681401991812119821931231749979165121401071772132281533725
354246215542393171150254110129388720211420722372271020517313621219042
341071041522183252381457177107901653108123207223195187718581721689130
752231311088420710820816470792122292032311820319110214917853233129216
602455721668230582431031342191327822824733248228421601031953425325123
169106196911414412619824230
Having a cryptographically secure platform (e.g. to back a cryptocurrency) means no rogue Tokens should be able, ever, to bond to the blockchain. For a fully successful attack you should still be able to crack-open, e.g. a Token (taking "ownership" of it and rewriting its value) and the ledger (supplanting the registers associated to the value encrypted in the hijacked Token, and in any Tokens that have ever been in a transaction with it). But still.
So this one for the crypto-geeks in here, if they want to have a go: the matching digits for the bonding site in the first position, corresponding to the first of the 5 Tokens issued (and embedded in the code above) are 65101771118538 | 6567101773738 | 6710185617738 | 677375837738. Notice that I've generated them all having the same termination (38) to give a little help (hope not!). These 4 bases are, of course, unencrypted.
If anyone can pull them out from the code above, then it will show I need to go back to the maths and try harder..! (did spend lots of paper and pencil already) The encryption here does not directly follow any of the (highly secure) standard protocols in use.
Perhaps this is an unfair check, as the litmus test is in the software platform itself and whether you can, e.g. intercept regs in memory, do code injection and so on as the bonding process takes place, which is what a hacker would normally try to do, amongst a myriad of other tricks.
BTW the original post and links to the presos can be found here
https://bitcointalk.org/index.php?topic=2098265.0The whole damn thing is a new protocol idea. A one-off for now, but if it proves secure, stable and it delivers as planned, who knows.
Cheers
Ed
