Bitcoin Forum
May 25, 2024, 05:18:35 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Proof of Work algorithm in the public chain.  (Read 120 times)
A.N.D. (OP)
Newbie
*
Offline Offline

Activity: 19
Merit: 2


View Profile
March 20, 2020, 04:48:44 PM
Merited by aliashraf (1)
 #1

Proof of Work algorithm in the public chain.
This is a hybrid algorithm. The algorithm is not typical. The algorithm is more secure than standard POW. There are no analogues at the moment. It is like a bipartisan political system. On the one hand, miners, on the other hand, coin holders. Each of the parties individually cannot influence the system as a whole.

Additional protection against attacks 51%.
Mining pools together will not be able to attack blockchain.
This algorithm is more environmentally friendly. You can save a lot of energy while maintaining the current security level of the blockchain compared to the standard POW.

https://drive.google.com/open?id=1Ca36qzsXf5bAqm2pFZafQDGdNSyPKSEx

I published this algorithm in a general topic, but, apparently, experts do not go there, there are no comments on the algorithm.
Please leave comments after reading.
aliashraf
Legendary
*
Offline Offline

Activity: 1456
Merit: 1174

Always remember the cause!


View Profile WWW
March 20, 2020, 10:22:40 PM
 #2

OP,

Thank you for sharing. I just finished reading your article. Although I strongly support and appreciate your intentions, I afraid your work is not matured enough to be discussed in detail. You need to keep working on it harder both in terms of design and representation, IMO. Some points for now:

1- Combining two very different approaches to cryptocurrency and blockchain is a bold choice but it won't work without extensive research on the very basic ideas behind the approaches.

2- You are absolutely silent about the networking layer: How pow miners and stake nodes should communicate for the miner to have the signed UNI from the specific node? What do we have to do with availability issues? IOW, what happens if the ode with the respective UNI is down?

3- What happens if the designated node is malfunctioning intentionally or not and declines to sign the appropriate message?

A.N.D. (OP)
Newbie
*
Offline Offline

Activity: 19
Merit: 2


View Profile
March 21, 2020, 07:34:09 PM
Last edit: March 21, 2020, 07:44:16 PM by A.N.D.
 #3

OP,

Thank you for sharing. I just finished reading your article. Although I strongly support and appreciate your intentions, I afraid your work is not matured enough to be discussed in detail. You need to keep working on it harder both in terms of design and representation, IMO. Some points for now:

1- Combining two very different approaches to cryptocurrency and blockchain is a bold choice but it won't work without extensive research on the very basic ideas behind the approaches.

2- You are absolutely silent about the networking layer: How pow miners and stake nodes should communicate for the miner to have the signed UNI from the specific node? What do we have to do with availability issues? IOW, what happens if the ode with the respective UNI is down?

3- What happens if the designated node is malfunctioning intentionally or not and declines to sign the appropriate message?





Thanks for taking the time to read. Of course, for implementation it is necessary to develop in more detail, while this is only an idea.
The interaction of miners and signing nodes occurs on mutually beneficial conditions. The miner is interested in obtaining a signature with a minimum numerical value to reduce the complexity of mining. The signing node is interested in having its signature included in the block and receiving a reward. If for some reason the miner cannot get UNI signatures, then the algorithm turns into a standard POW, since it is impossible to reduce the complexity.
If some node intentionally does not sign the message, then the miner includes in the block any other UNI with a minimum value.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!