One thing that we could do with Ordinals bloat, is to just to hardcode their list in the source code and not store them at all (possibly in some light-prunning mode).
This is not a HF, not even a SF. It's a simple optimization, not unlike pruning. And segwit witness discount was justified by the ability of (some) nodes to discard witness data. Purely an internal and later on p2p protocol change and an optimization. They are just an easy to identify bloat that could be very easily skipped for a speedup and less resource use. Older clients (or "full archival" node) could still store them, but most of the network don't need them for anything.
That should also put some breaks on the ordinal users who think they are really storing something in there.
dpc
npub1ya…t0gd0
2023-02-04 18:54:14
Author Public Key
npub1yarprdrj3vxyp0su7xqd3u6z047na6792ezas6dqqt5tv4lce4ssjt0gd0Published at
2023-02-04 18:54:14Event JSON
{
"id": "c41819c280db57bfae958ad029725fb08c26fb062362a1ded1084ba425774871",
"pubkey": "274611b4728b0c40be1cf180d8f3427d7d3eebc55645d869a002e8b657f8cd61",
"created_at": 1675536854,
"kind": 1,
"tags": [],
"content": "One thing that we could do with Ordinals bloat, is to just to hardcode their list in the source code and not store them at all (possibly in some light-prunning mode).\n\nThis is not a HF, not even a SF. It's a simple optimization, not unlike pruning. And segwit witness discount was justified by the ability of (some) nodes to discard witness data. Purely an internal and later on p2p protocol change and an optimization. They are just an easy to identify bloat that could be very easily skipped for a speedup and less resource use. Older clients (or \"full archival\" node) could still store them, but most of the network don't need them for anything.\n\nThat should also put some breaks on the ordinal users who think they are really storing something in there.",
"sig": "744905f8345d2d6d0c8de276ec8bd7fc484d8f8c0b09812d222ca23716aec1c0d9ee5b58e6f7fd4c5f4991dd85a11e88834df7cfddc467b8b3f8985971226ff7"
}