You are viewing a single comment's thread from:

RE: The evergreen hive sink idea

in LeoFinancelast year

Once the posting key is compromised there will be no way to recover from that.

Sort:  

Yeah I mentioned in the end that it'd have to be extra secured, I'm thinking giving another account permission to posting with the main account as an extra step to keep that key offline as much as possible.

Wait until smart-contracts, or instead of wiping out active/owner - spread them among trusted parties with threshold high enough so many would have to sign transaction in order to use active authority. For example 12 people, where 8 of 12 are required in order to execute transaction :-)

Hmm, that would make sense as well I suppose, but having it too high of people just in case the posting key ever lands in the wrong hands to use it to reset sounds a bit dangerous as well considering some of them may leave/go afk long term. Maybe less people as long as they're trusted in that case?

Less is less complex but more prone to collusion, you need to figure out the proper balance. Those elected trusted individuals doesn't have to be forever, they can gather every few months in order to update the list (to protect from AFK / MIA)

Sorry to jump in on the conversation, but I have a dev question for you. Is it possible to build plugin for the nodes on hive that allows for a messaging system.

Think less on instant messaging and more like inter-blockchain communication.

Is this just a pipe-dream or achievable?

It'd be a great way to utilize smart contract systems for Hive.

Could you explain what kind of messaging you have in mind?

I suspect that this will not sufficiently answer your question (or at the very least show my naïveté, but I'll give it a go.

I'm a newish computer science student. I have the most familiarity with Ethereum Virtual Machine based architectures. They are becoming more abundant in the space. I also want to preface this by saying that I know the implementation here is non-trivial.

Essentially in any case there would need to be read/write functionality with custom-metadata on Hive, an efficient way to keep track of the sequencing of the data, and a way to pass messages as a verifier to/from another blockchain.

I know that this sounds a whole lot like a bridge (because it is really), but it'd be nice if this could be integrated into Hive nodes through plugins because it might encourage the expansion of the number of nodes within the ecosystem. Some of the bridges being built for Hive are nice but they tend to want to be their own thing, or aren't permissionless. This detracts from the value that could be added to Hive if it did this out of the box. I get that there are many moving parts, and that it would have to be substantially tested, but I think it would be worth it.

All of that said, if this is even remotely possible, I'd be willing to give it a go.