Not all bitvm transactions transfer values on L1, and not all of them use HTLCs
> do you consider it a spam if a Metaprotocol is demonstrating that exact soft fork
It is spam imo if and only if the metaprotocol's transactions add more data to bitcoin than would otherwise be there, data with a purpose other than the ones outlined in my definition. There's nothing wrong with simulating a soft fork in a metaprotocol, imo. But if, in service of demonstrating that feature, you use bitcoin as a text dump for your metaprotocol's data, that's spammy.
Super Testnet
npub1yx…c399s
2026-01-15 19:53:15 UTC
in reply to nevent1q…6wul
Author Public Key
npub1yxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96s8c399sSeen on
wss://nos.lolPublished at
2026-01-15 19:53:15 UTCEvent JSON
{
"id": "ec38ebb1d557fdb18832adfb180732bd72fef77b757006891fa0dc7f768d065a",
"pubkey": "2183e94758481d0f124fbd93c56ccaa45e7e545ceeb8d52848f98253f497b975",
"created_at": 1768506795,
"kind": 1,
"tags": [
[
"alt",
"A short note: Not all bitvm transactions transfer values on L1, ..."
],
[
"e",
"90b9b9b300d0d02f44c517d9052f9e8d4468f81044d539eed3d5424600984fc5",
"wss://nostr.oxtr.dev/",
"root",
"2183e94758481d0f124fbd93c56ccaa45e7e545ceeb8d52848f98253f497b975"
],
[
"e",
"1a1ef33ae11403277de210c3115cc8f41556337cfd24c6ef841865bc4f8f6fbc",
"wss://nostr.bitcoiner.social/",
"",
"2183e94758481d0f124fbd93c56ccaa45e7e545ceeb8d52848f98253f497b975"
],
[
"e",
"f9e62c8ef3bde86ab3994709e8f480ca3b6c9fad757a31f9c825f56a5fe0b1ef",
"wss://relay.damus.io/",
"reply",
"930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9"
],
[
"p",
"aac07d95089ce6adf08b9156d43c1a4ab594c6130b7dcb12ec199008c5819a2f",
"wss://multiplexer.huszonegy.world/"
],
[
"p",
"2183e94758481d0f124fbd93c56ccaa45e7e545ceeb8d52848f98253f497b975",
"wss://relay.damus.io/"
],
[
"p",
"930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9",
"wss://nostr.heliodex.cf/"
]
],
"content": "Not all bitvm transactions transfer values on L1, and not all of them use HTLCs\n\n\u003e do you consider it a spam if a Metaprotocol is demonstrating that exact soft fork\n\nIt is spam imo if and only if the metaprotocol's transactions add more data to bitcoin than would otherwise be there, data with a purpose other than the ones outlined in my definition. There's nothing wrong with simulating a soft fork in a metaprotocol, imo. But if, in service of demonstrating that feature, you use bitcoin as a text dump for your metaprotocol's data, that's spammy.",
"sig": "8b2025d5b5c63eae1408d472ce57e12aa76a043b9c2ff2ab484de0a28dc81cbd2fb831aa5881c840614e8727da0e6e4df0b1959657c5897fcb845b69f529c3c9"
}