Background problem
For some time now I have been reviewing the c ++ code to find a more decentralized way to bring hive to the ETH network. At this moment WHIVE is processed by a central node which reviews both blockchains, so that this process is decentralized it should be directly in the blockchain code. But this has a problem which is that hive would need to save state of the external blockchain as ETH.
This is not good from my point of view considering that hive is a second layer network for this I was thinking and came to the conclusion to solve this problem not only for WHive but for other dapps that are running at this time without the need for smart contracts. What I would like to propose to you is what I call sub-consensus accounts, these accounts would allow decentralizing processes without the need for smart contracts.
What are subconcensus accounts
The sub-consensus accounts are the typical accounts of all users but with the only difference that they do not have keys but they will wonder why we want accounts without keys, it is simple the idea is that through a voting system it can be defined which accounts will serve as multi-authority. When defining this multi-authority process in a subconcensu account, the users within hive decide which accounts are associated and there would be no problem that 1 single user with the owner keys has control of everything. This allows code to be executed outside of the main blockchain and the multi-authority accounts would serve as validators to define whether or not a process is performed on the main hive network.
What do you want to solve
What I want to solve is the possibility of creating contracts by developers in which the consensus is through multi-authority this in the main network but the code to be executed by a validator account is outside the main blockchain. What allows this to be done is that the validator accounts carry out the execution of their codes in a network completely outside a network of the hive blockchain but the processes such as transfers, votes are at the level of the hive blockchain and to carry out these transactions it would be necessary to reach a multi-authority concensus.
I would like to know what you think about this process that I am raising and if your thoughts on this process.
Seems like a useful goal, but I'm not sure that this would be the best solution. We already have a voting system for determining what happens on Hive. Why not simply give this authority to the consensus witnesses?
The problem is simple to leave all this in the main layer requires programming in c ++ and requires hardforks for updates, on the other hand creating validation accounts the processes of the main network hive is only responsible for deciding which are the validation accounts and these Accounts will already have their own memory and disk systems to carry a separate process which allows better scalability.
Keep in mind that this will not only work for whive but also other dapps since it will allow these dapps to carry their own concensus systems in a 2 layer network.
I have thought about that type of solution for a second layer for quite some time now. I am not good at coding (I did some stuff using visual basic almost 20 years ago to solve a data storing issue where I worked at back then), but the issue that I was looking at regarding a 2nd layer was what consensus algorithm to use to determine which accounts have signing authority.
The only problem that I see is that needing multiple accounts to sign each transaction before broadcasting it to the core layer has some scalability issues (because of the time it would take to gather and process those signatures by each validator).
Having atomic swap capabilities on hive could be a posible solution..?
Congratulations @ederaleng! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s) :
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPDo not miss the last post from @hivebuzz: