Bitcoin Forum
May 06, 2024, 06:02:08 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Question About Simultaneously Mined Blocks and the Possible Consequences  (Read 132 times)
butka (OP)
Full Member
***
Offline Offline

Activity: 434
Merit: 246


View Profile
May 09, 2018, 09:26:02 AM
Merited by ABCbits (1)
 #1

This is a question that has been lingering in my mind for some time. I think I know the answer but maybe I'm wrong. Hopefully someone can clear this for me.

In a totally decentralized peer to peer network, two miners relatively far from each other (if you can say this) mine a block approximately at the same time.

They announce their solutions, and we have a situation where two blockchains propagate through the network. Each one of them is being accepted by their closest local nodes and continues to spread out.

Roughly speaking, after some time we should have a situation where half of the network has accepted one blockchain, and the other half of the network another.

If this logic is valid, than the first half of the network should already be mining a new block on top of their version of the blockchain, and the second half on top of theirs.

Again, if this logic holds, is it so that the one who mines the next (second) block decides the overall winner?

If the second block is found within the first half of the network, their blockchain is the ultimate winner (as the longest one), and the other half of the network has to revert to the solution of the first half and abandon their version of the blockchain.

Is this indeed so?
1715018528
Hero Member
*
Offline Offline

Posts: 1715018528

View Profile Personal Message (Offline)

Ignore
1715018528
Reply with quote  #2

1715018528
Report to moderator
1715018528
Hero Member
*
Offline Offline

Posts: 1715018528

View Profile Personal Message (Offline)

Ignore
1715018528
Reply with quote  #2

1715018528
Report to moderator
If you want to be a moderator, report many posts with accuracy. You will be noticed.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
Xynerise
Sr. Member
****
Offline Offline

Activity: 322
Merit: 363

39twH4PSYgDSzU7sLnRoDfthR6gWYrrPoD


View Profile
May 09, 2018, 09:29:20 AM
 #2

Nodes store both copies until one with a cumulative higher proof of work emerges.
See my post here for details on blockchain reorgs
etherixdevs
Jr. Member
*
Offline Offline

Activity: 203
Merit: 3


View Profile
May 09, 2018, 09:33:29 AM
 #3

It can happen. you will have two competing blocks. Let's call them A and B.

Assume A was solved just a second or two before B. This means A is likely to have propagated to most of the network than block B, but let's assume it's not a huge margin.

Other miners who received the A block before receiving the B block will try to mine on top of A. Miners who received B first will try to mine on top of B.

If the next block to be found is on top of block A, the miners mining on top of B will abandon B and go back to mining the A chain. The reverse is true if a block were to be solved on top of B first.

Of course, a block could be mined on top of A and another on top of B at roughly the same time, causing the same problem again. The competition between chain A and B will just continue until it gets resolved. This is part of the reason why most people suggest waiting for multiple blocks of confirmation before assuming a transaction is non-reversible.

The block that gets abandoned is called a an orphan block and any chain built on top of it is an orphan chain.
butka (OP)
Full Member
***
Offline Offline

Activity: 434
Merit: 246


View Profile
May 09, 2018, 10:34:31 AM
 #4

Nodes store both copies until one with a cumulative higher proof of work emerges.
See my post here for details on blockchain reorgs
I see, thanks for the link and for clearing this up. After all, it is a little bit more complicated than I thought.
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!