Skip to content

Commit

Permalink
feat: confirmations
Browse files Browse the repository at this point in the history
  • Loading branch information
reednaa committed Oct 31, 2024
1 parent a90e0c1 commit 31bbfa7
Showing 1 changed file with 17 additions and 0 deletions.
17 changes: 17 additions & 0 deletions src/content/docs/cross-cats/bitcoin-primer.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -110,3 +110,20 @@ Importantly, the sum of all inputs must be greater than the outputs. The differe
## Proving Bitcoin Transactions

This section has not been written yet.


## Confirmations

SPV clients are not safe at 1 confirmation, it is required that multiple blocks are built on top. This is because anyone can mine a transaction that passes all SPV checks but contains fraudulent transactions. As a result, an SPV client is at best as good as the blocks built on it.

Additionally, the SPV client used does not validate the actual difficulty adjustments. Instead it verifies the 1/4 law. As a result, each block shall only be assumed to hold 1/4 of the validation power as a fully verified Bitcoin block. As a rule of thumb, the below table can be used to map value to number of confirmations.

| Size | Conf. |
|-------------|-------|
| \$0k - \$20k | 2 |
| \$20k - \$100k | 3 |
| \$100k - \$200k | 4 |
| \$200k - \$1m | 5 |
| \$1m+ | 6 |

Note that starting from 5 confirmations, you get full Bitcoin security as 2 Bitcoin blocks will always reorg the chain to the proper difficulty (assuming the minority chain isn't being mined with 51% of the mining power).

0 comments on commit 31bbfa7

Please sign in to comment.