Bitcoin is Layer 0 (non-witness bits) and bounded by 1MB via Bitcoin consensus.
SegWit is Layer1 (witness bits) and bounded by 4MB via discounting in Bitcoin Consensus.
L0 < 1 MB
L0+L1 < 4 MB
L1 is anchored to L0.
L0 is Bitcoin consensus
L1 is SegWit consensus
To combat this discount and objective deviation from 1MB blocks as defined by Satoshi, nodes can bound their total block data back to 1 MB by pruning witness.
L0 < 1 MB
L0+L1 < 1 MB
This means by node policy, what is stored in L1 (witness bits) can be filtered and defined by the user. We can use objective fees paid and transaction efficiency to enforce 1 MB blocks at the node level without breaking Bitcoin consensus. SegWit is a soft fork thus optional. All txs are Layer 0 valid, but not all txs make into Layer1 blockspace bounded by 1 MB and Nakamoto Consensus at the node level. The witness is just not saved. SegWit fights for what memory is remaining after L0 validity and consensus. It’s opt in.
The more nodes that enforce this change to SegWit validity, the more it will have an external influence on the network. Totally backwards compatible and consensus valid. Just not forwards compatible. Let the 4MB nodes store everything, we filter to 1MB max as valid. I cannot force anyone to change their consensus rules. But if you want your SegWit to be saved/real on my node, you can follow my policy. This is how we can combat L1 spam, especially when 1 MB enforced at the L2/LN level for valid channel state. This will eradicate the SegWit discount by forcing competition over L0 fees, making the cost to spam L0 via op_return more costly due to conserved and finite 1MB blockspace across all layers in total.
At some point, the consensus change will be feasible by logic. A node running better Bitcoin physics will always outlast those who discount their bits.
A POW hardfork to fix spam is not necessary, all it does is inject fiat into the thermodynamic curve by manually adjusting difficulty. Invariance is lost.
Jackk / Jack K
npub183…faslh
2026-09-04 14:45:13 UTC
Author Public Key
npub18384z4sjgdfy7vr76thzwtru7jncysz0hcapwesxqsak44p8aemsyfaslhSeen on
wss://nos.lolPublished at
2026-09-04 14:45:13 UTCEvent JSON
{
"id": "eb5fc4d49013ad8234e38e16142fd911674b5ac53a0284bf324a5600ec70887d",
"pubkey": "3c4f51561243524f307ed2ee272c7cf4a782404fbe3a176606043b6ad427ee77",
"created_at": 1788533113,
"kind": 1,
"tags": [
[
"client",
"Primal iOS"
]
],
"content": "Bitcoin is Layer 0 (non-witness bits) and bounded by 1MB via Bitcoin consensus.\n\nSegWit is Layer1 (witness bits) and bounded by 4MB via discounting in Bitcoin Consensus.\n\nL0 \u003c 1 MB\nL0+L1 \u003c 4 MB\n\nL1 is anchored to L0.\nL0 is Bitcoin consensus\nL1 is SegWit consensus\n\nTo combat this discount and objective deviation from 1MB blocks as defined by Satoshi, nodes can bound their total block data back to 1 MB by pruning witness.\n\nL0 \u003c 1 MB\nL0+L1 \u003c 1 MB\n\nThis means by node policy, what is stored in L1 (witness bits) can be filtered and defined by the user. We can use objective fees paid and transaction efficiency to enforce 1 MB blocks at the node level without breaking Bitcoin consensus. SegWit is a soft fork thus optional. All txs are Layer 0 valid, but not all txs make into Layer1 blockspace bounded by 1 MB and Nakamoto Consensus at the node level. The witness is just not saved. SegWit fights for what memory is remaining after L0 validity and consensus. It’s opt in.\n\nThe more nodes that enforce this change to SegWit validity, the more it will have an external influence on the network. Totally backwards compatible and consensus valid. Just not forwards compatible. Let the 4MB nodes store everything, we filter to 1MB max as valid. I cannot force anyone to change their consensus rules. But if you want your SegWit to be saved/real on my node, you can follow my policy. This is how we can combat L1 spam, especially when 1 MB enforced at the L2/LN level for valid channel state. This will eradicate the SegWit discount by forcing competition over L0 fees, making the cost to spam L0 via op_return more costly due to conserved and finite 1MB blockspace across all layers in total.\n\nAt some point, the consensus change will be feasible by logic. A node running better Bitcoin physics will always outlast those who discount their bits.\n\nA POW hardfork to fix spam is not necessary, all it does is inject fiat into the thermodynamic curve by manually adjusting difficulty. Invariance is lost. ",
"sig": "75cfc5d3eadf108fb1e37da011b3ce2ccd82121d1c09334c85b47fba95d8a5d53defcdfb53326bb10fb698816cd4adab4ba7354d6c3dbc16fd1dbfce69d0434c"
}