You running knots versus core does nothing for how much data is stored by your blockchain. Knots accepts all the same blocks on the chain as core.
BIP-110 also doesn't change anything with regards to the potential storage requirements of running a node since the amount of data stored for any given block remains the same.
At the end of the day, BIP-110 was selling a lie.
Data storage for bitcoin's blockchain remains a linear non-issue. Every block has a max size which means the blockchain grows linearly and therefore storage requirements over time for a pleb node runner is overcome easily with cheap consumer hardware.
If anything, not using OP_RETURN for arbitrary data is what increases node requirements since if that data is otherwise stored in the UTXO set, it WILL increase your node requirements since the UTXO set is stored in RAM, which is also far more costly.
Also, if the ColdCard debacle taught us anything about a proper SDLC, it is that you need robust commit tracking for code changes and the way that Luke maintains Knots mirrors the way that ColdCard maintained its firmware, if not worse. There is no code signing of the changes that Luke is committing to Knots from their source. You lose tracking of what the code changes actually are. It is a pet project of Luke's and I'd caution anyone serious about security to avoid running it.
Tyler Burns
npub1d3…xynp3
2026-08-09 12:38:05 UTC
in reply to nevent1q…5edv
Author Public Key
npub1d30mhvhd0sagmu83wdm26wqk00heptfn05xvgmfx7r9xscstnfcs7xynp3Published at
2026-08-09 12:38:05 UTCEvent JSON
{
"id": "00007ffb137ffbba32571b294e3463428ac310e2c676f487780cb3a0a1c2bb16",
"pubkey": "6c5fbbb2ed7c3a8df0f17376ad38167bef90ad337d0cc46d26f0ca68620b9a71",
"created_at": 1786279085,
"kind": 1,
"tags": [
[
"e",
"242410921564dce0af2955f5c0076d0b05bf942a2ca71b819389aad6bf7e6fcb",
"",
"root"
],
[
"e",
"42bf9be382905e7c8b4fd6f7ffd49108d1f1c47a0d221f0c32b47b93f0f33d29",
"wss://relay.ditto.pub",
"reply"
],
[
"p",
"c69b71dc564fdc350acddff929f25d7202ac1470c87488608bd6d98e426ba763"
],
[
"client",
"Dark Wisp"
],
[
"nonce",
"56781",
"16"
]
],
"content": "You running knots versus core does nothing for how much data is stored by your blockchain. Knots accepts all the same blocks on the chain as core.\n\nBIP-110 also doesn't change anything with regards to the potential storage requirements of running a node since the amount of data stored for any given block remains the same.\n\nAt the end of the day, BIP-110 was selling a lie.\n\nData storage for bitcoin's blockchain remains a linear non-issue. Every block has a max size which means the blockchain grows linearly and therefore storage requirements over time for a pleb node runner is overcome easily with cheap consumer hardware.\n\nIf anything, not using OP_RETURN for arbitrary data is what increases node requirements since if that data is otherwise stored in the UTXO set, it WILL increase your node requirements since the UTXO set is stored in RAM, which is also far more costly.\n\nAlso, if the ColdCard debacle taught us anything about a proper SDLC, it is that you need robust commit tracking for code changes and the way that Luke maintains Knots mirrors the way that ColdCard maintained its firmware, if not worse. There is no code signing of the changes that Luke is committing to Knots from their source. You lose tracking of what the code changes actually are. It is a pet project of Luke's and I'd caution anyone serious about security to avoid running it.",
"sig": "8e8fae351e1dbb6e484a426cdb5ff65f885252d52b70f6e270dc9025e5ed3b472787025b935435b48c132f79bc99dec57969ebe0ba82521e1a5a8ca9efdebe25"
}