Blockchain Support

[quartzjer]

Document how a telehash mesh can be used to facilitate blockchain-based transactions (both bitcoin/sidechains, and ethereum). For increasing privacy as a transport, and for adding hashnames to a transaction as a form of authorization/grant for access.

[Kagami]

👍 Very interested in such kinds of telehash usage.

[quartzjer]

Do you have any specific use cases or immediate ways you'd like to use it? It's a pretty open field yet, and needs some focused ideas to get started.

[Kagami]

I'm currently researching the way of using telehash as a transport for simple distributed blogging platform (more like Twister). For first prototype it would be enough to just store messages/comments on directly connected nodes signed with the hashname's public keys. But I'm also interested in things like message updates/deletions (not permanent, more like in a wiki) and at first glance blockchain is the right tool for the job. Also it would be helpful to have some sort of nodes discovery mechanisms like in BitTorrent/Bitcoin. Note though that I'm very new to DHT and blockchain so any hints would be greatly appreciated.
I've read discussion with you about the nature of telehash v3 here and as far as I can understand, telehash's goal is to provide the secure E2E transport and it's up to the application to implement blockchain/DHT on top of it. Any tips?

[quartzjer]

I'm a strong advocate of keeping user identity clearly separate network-endpoint identity, and making sure there is a clear mapping between the two, so I'd advise against using a single hashname for both :)

I'm also an advocate of using the JOSE standards for user identity, for all signing/token handling, etc, the tools for JWTs, JWKs, etc are really maturing nicely.

A DHT ends up working best when it's adapted specifically to the app needs, so it might not be that bitcoin or bittorrent's model will be ideal for a distributed blogging model, particularly with the multicast-style needs. Have you looked at NDN at all yet?

[Kagami]

Thanks, I will read the links. Do you know any real examples/implementations of NDN/CCN? It looks interesting. (I've heard but do not know much about it.) Though just storing the data is easy, for me it's more problematic to implement the distributed wiki model which would handle all the message/comments/profiles updates. The only existing model similar to that which I know is blockchain. Am I missing something?

Wow, I didn't know about the separation of user and network identities, thanks. Though now I don't understand how to provide the user-hashname mapping and why it's wrong to use hashname as an user identity. The example chat channel uses hashnames as an user identities. Could you elaborate please?

[quartzjer]

You should connect with @rynomad who build a federated wiki prototype on NDN, the repo is old but I know he's still working on it in some form.

"Users" need to be identified independently so that they can use multiple devices and migrate devices and still carry their identity with them. An endpoint in telehash is designed for it's private keys to never leave a device, be generated and unique to a specific network endpoint. You can think of the hashname for an endpoint as an ipv6 address, that's not how you'd want to identify yourself permanently, just where you're reachable at right now :)

[quartzjer]

I'm going to close this issue and use more specific ones like #102 to track these, as well as the draft of the bitcoin guide.

[ngabo2017]

I want to ask if Blockchain can be combined with NDN to solve some security issues in the NDN architecture, for example, Interest flooding attack, Signature, and content Privacy, DDoS. Thank You!!