display: inline;
padding-right: 1rem;
}
+.callout {
+ margin-bottom: 1rem;
+ padding-left: 0.5rem;
+ border-left: 0.2rem solid;
+}
+.callout-info {
+ border-left: 0.2rem solid #086ddd;
+}
+.callout-info > .callout-label {
+ color: #086ddd;
+ font-weight: bold;
+}
+.callout-warn {
+ border-left: 0.2rem solid #ec7500;
+}
+.callout-warn > .callout-label {
+ color: #ec7500;
+ font-weight: bold;
+}
+.callout-error {
+ border-left: 0.2rem solid #e93147;
+}
+.callout-error > .callout-label {
+ color: #e93147;
+ font-weight: bold;
+}
.collectiontag {
font-variant: small-caps;
}
\ No newline at end of file
---
title: Minimum UTXO Value
date: 2023-08-04
-modified: 2024-01-26
+modified: 2024-12-23
description: A look at what Bitcoin dust is, historical fee rates, how fees are calculated, and a decision on a minimum UTXO value to stay above the dust threshold.
tags:
- bitcoin
Because fee rates are the primary variable determining the dust threshold, whether a UTXO is considered dust can change over time. I took a look at historical fee rates, how fees are calculated, and included qualitative projections of future block space demand to determine a UTXO value that will stay above the dust threshold for myself.
-> **TL;DR;**
->
-> Taproot UTXO, 65k sats
+{% callout "info" %}
+**TL;DR:** Taproot UTXO, 65k sats
+{% endcallout %}
### Historical Fee Rates
The highest fee periods in Bitcoin history have been 2018, 2021, and 2023:
The first visible difference based on the box and whisker plot is the noticeable decrease in fee rate variance, likely attributable to better fee estimations. Second, is the 86% decline in median fee rate with an average 194 sats/vB between blocks 504000 and 680000 vs. 27 sats/vB in block 782400.
-> **Note**
->
-> I'm taking a naïve view of transactions, so transactions pushed through using CPFP aren't coalesced into a single transaction with a blended, "effective" fee rate. In theory, this should reduce fee rate spread, but will be relatively centered around the median.
+{% callout "info" %}
+I'm taking a naïve view of transactions, so transactions pushed through using CPFP aren't coalesced into a single transaction with a blended, "effective" fee rate. In theory, this should reduce fee rate spread, but will be relatively centered around the median.
+{% endcallout %}
I don't expect to see major differences in fee rates by script type, but since I have the data available here's what that looks like (it's as expected):
So in ideal dust spending conditions, you would hold a P2TR UTXO and spend it to a P2WPKH output. An input requires more vBytes than an output, so the ideal will change if you are spending few inputs to many outputs.
-> **Note**
->
-> Surprisingly, despite P2SH and P2PKH inputs being the most expensive (in terms of total fees), the fee data above doesn't bear that out. Without doing further digging, I assume it's due to multi-sig being more common with other script types.
+{% callout "info" %}
+Surprisingly, despite P2SH and P2PKH inputs being the most expensive (in terms of total fees), the fee data above doesn't bear that out. Without doing further digging, I assume it's due to multi-sig being more common with other script types.
+{% endcallout %}
### Choosing a Minimum UTXO Value
Putting everything together, here are my assumptions for choosing my minimum UTXO value:
---
title: 'Removing a Drive from a Btrfs Array'
date: 2023-07-05
-modified: 2024-01-26
+modified: 2024-12-23
description: If a drive is failing in an array, Btrfs could block attempts at removing the drive due to corrupted files. A quick write-up of how to get it removed.
tags:
- linux
At this point, I was okay with losing any corrupted/unrecoverable files. You should already be past the point of restoring from backup, attempting other recovery methods, etc. I just wanted to get the dying drive removed from the array since I knew I didn't have critical data on the array.
-> **Warning**
->
-> Make sure you've exhausted all other resources before continuing. Check the [ArchWiki](https://wiki.archlinux.org/title/Btrfs), [Btrfs mailing list](https://archive.kernel.org/oldwiki/btrfs.wiki.kernel.org/index.php/Btrfs_mailing_list.html), etc. This will lead to data loss!
+{% callout "warn" %}
+Make sure you've exhausted all other resources before continuing. Check the [ArchWiki](https://wiki.archlinux.org/title/Btrfs), [Btrfs mailing list](https://archive.kernel.org/oldwiki/btrfs.wiki.kernel.org/index.php/Btrfs_mailing_list.html), etc. This will lead to data loss!
+{% endcallout %}
### Scrub the Array
Start a scrub to identify files blocking the device from getting deleted:
const eleventyImagePlugin = require("@11ty/eleventy-img");
const eleventySyntaxHighlightPlugin = require("@11ty/eleventy-plugin-syntaxhighlight");
const globalMetadata = require("./_data/metadata.json");
+const markdownIt = require("markdown-it")();
const path = require("path");
function relativeToInputPath(inputPath, relativeFilePath) {
// Return the smallest number argument
return Math.min.apply(null, numbers);
});
+ eleventyConfig.addPairedShortcode(
+ "callout",
+ function (content, level = "", format = "md", customLabel = "") {
+ if (format === "md") {
+ content = markdownIt.renderInline(content);
+ } else if (format === "md-block") {
+ content = markdownIt.render(content);
+ } else if (format === "html") {
+ content = content
+ }
+ if (customLabel) {
+ label = customLabel;
+ } else if (level === "info") {
+ label = "🛈 Info"
+ } else if (level === "warn") {
+ label = "⚠ Warning";
+ } else if (level === "error") {
+ label = "! Error"
+ }
+ let labelHtml = label
+ ? `<div class="callout-label">${customLabel || label}</div>`
+ : "";
+ let contentHtml =
+ (content || "").trim().length > 0
+ ? `<div class="callout-content">${content}</div>`
+ : "";
+
+ return `<div class="callout${
+ level ? ` callout-${level}` : ""
+ }">${labelHtml}${contentHtml}</div>`;
+ }
+ );
eleventyConfig.addPassthroughCopy({ "./static/": "/" });
eleventyConfig.addPlugin(feedPlugin, {
type: "atom",
projects / cotsuka.github.io / commitdiff