{"id":1582,"date":"2020-02-03T00:01:00","date_gmt":"2020-02-03T08:01:00","guid":{"rendered":"https:\/\/www.opennode.com\/blog\/?page_id=1582"},"modified":"2020-01-30T10:38:51","modified_gmt":"2020-01-30T18:38:51","slug":"confirmation","status":"publish","type":"page","link":"https:\/\/blog.opennode.com\/blog\/glossary\/confirmation\/","title":{"rendered":"Confirmation"},"content":{"rendered":"Reading Time: <\/span> < 1<\/span> minute<\/span><\/span>\n

Confirmation<\/h1>\n\n\n\n

When a miner<\/a> mines a valid block<\/a>, call it block #231765, and broadcasts it to the blockchain<\/a>, the mining<\/a> for block #231766 starts right away. When block #231766 gets mined, all the transactions in block #231765 are now one block deep in the blockchain. This means that the network is essentially \u201cconfirming\u201d, or, trusting, that all those transactions are valid. For a transaction to have \u201cone confirmation\u201d, it needs to be in a block that is 1 block deep on the blockchain.\u00a0<\/p>\n\n\n\n

As blocks get deeper and deeper down the blockchain, they become increasingly immutable. By the time a block gets 3-6 block confirmations, the contents of that block are virtually unchangeable. If one wanted to change or alter a transaction one block below the current block, theoretically they\u2019d have to rehash and remine that block while also mining the current block, which is virtually impossible. <\/p>\n\n\n\n

Links<\/h2>\n\n\n\n