From 8a4bd1b9db06827358e703c31122b0bd038fa1dc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A2u=20Cao?= Date: Mon, 12 May 2025 13:17:49 +0400 Subject: [PATCH] More precise wording --- 2/bitcoin-data-storage-comparison.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/2/bitcoin-data-storage-comparison.md b/2/bitcoin-data-storage-comparison.md index ded13c5..398906a 100644 --- a/2/bitcoin-data-storage-comparison.md +++ b/2/bitcoin-data-storage-comparison.md @@ -1,10 +1,10 @@ | Method | Description | Pros | Cons | Pruning Ease | |-------------------------|--------------------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------| -| `OP_RETURN` | Stores data in unspendable output, up to 80 bytes. | Standard, no UTXO bloat, designed for pruning | Limited to 80 bytes, fees, may not persist in pruned nodes | High: Prunable post-validation | -| Dust Transactions | Small, unspent outputs with embedded data, often left unspent. | More data than OP_RETURN, persistent until spent | Bloats UTXO, higher fees, seen as spam | Low: Stays in UTXO until spent | -| Address Encoding | Encodes data into Bitcoin addresses, ~17 bytes. | No BTC spent, specific use cases | Very limited size, non-standard, custom handling | Medium: Prunable if unspent | -| Storing Hashes | Stores hash (e.g., 32 bytes) on-chain, often via OP_RETURN, data off-chain. | Efficient, low cost, no UTXO bloat | Off-chain data risks, accessibility issues | High: Prunable like OP_RETURN | -| Non-standard Transactions | Non-standard transaction types to embed data, not widely supported. | Flexible storage | Unsupported by many nodes, seen as spam, may be removed | Variable: Depends on UTXO impact | +| `OP_RETURN` | Stores data in unspendable output, up to 80 bytes. | Standard, no UTXO set bloat, designed for pruning | Limited to 80 bytes, fees, may not persist in pruned nodes | High: Prunable post-validation | +| Dust Transactions | Small, unspent outputs with embedded data, often left unspent. | More data than OP_RETURN, persistent until spent | Bloats UTXO set, higher fees, seen as spam | Low: Stays in UTXO set until spent | +| Address Encoding | Encodes data into Bitcoin addresses, ~17 bytes. | No BTC spent, specific use cases | Very limited size, non-standard, custom handling | Medium: Prunable if unspent | +| Storing Hashes | Stores hash (e.g., 32 bytes) on-chain, often via OP_RETURN, data off-chain. | Efficient, low cost, no UTXO set bloat | Off-chain data risks, accessibility issues | High: Prunable like OP_RETURN | +| Non-standard Transactions | Non-standard transaction types to embed data, not widely supported. | Flexible storage | Unsupported by many nodes, seen as spam, may be removed | Variable: Depends on UTXO set impact | **Citations:**