Mad Jackal
2020-12-10 00:44:01
PoW consensus does not provide for the concept of "finalizing" a block or transaction - for PoW this is a probabilistic concept. Since the PoW considers forks as normal, a block can theoretically be "canceled" at any depth. However, practice has established that the probability of replacing a block at a depth of more than 6 did not occur, therefore it is considered that if there are 6 or more other blocks "on top" of the block, then transactions in it are "conditionally finalized".
Thank you for your helpful answer. Can i set configuration when client listens to the server, server send me blocks with different of 6 to the best block? I mean server send me only new blocks of height=current_height - 6? I'm looking for an RPC request message to do that instead implementing a logic for
Sorry, but I don't work with bitcoin wallets and clients, so I don't know :-(
You said any block may be "canceled" in any height, so that made me think about implementing and handling the logic properly. Thank you for your answer :-)