I think the notion that the blockchain is Bitcoin's database is wrong.
* the UTXO set is the database
* the blocks take the database from one consistent state to the next.
* the blocks are needed only by newly started nodes to recreate the database.
In this context,
* OP_RETURN is not bloating the database as it never enters it.
* Encoding data in non-OP_RETURN outputs does bloat the database.
Switching what you call "the database" doesn't change the problem with bloat, but maybe the perspective changes a little bit.
kalle
npub1g9…fy05t
2025-05-08 17:38:15 CEST
Author Public Key
npub1g9ym6t98cz9tvvsac865zak83txjjhd2yqcdegzwsqg2mxfww9xs8fy05tSeen on
wss://relay.damus.ioPublished at
2025-05-08 17:38:15 CESTEvent JSON
{
"id": "88894049af782270ca44feeb14f3bc18e6a51b1baea0f3d2ab3b3e63f5217582",
"pubkey": "4149bd2ca7c08ab6321dc1f54176c78acd295daa2030dca04e8010ad992e714d",
"created_at": 1746718695,
"kind": 1,
"tags": [],
"content": "I think the notion that the blockchain is Bitcoin's database is wrong.\n\n* the UTXO set is the database\n* the blocks take the database from one consistent state to the next.\n* the blocks are needed only by newly started nodes to recreate the database.\n\nIn this context, \n\n* OP_RETURN is not bloating the database as it never enters it.\n* Encoding data in non-OP_RETURN outputs does bloat the database.\n\nSwitching what you call \"the database\" doesn't change the problem with bloat, but maybe the perspective changes a little bit.",
"sig": "dcab0638eaa33caab54b627f2f1ae9fab05519f2eda8c280a95b5c01a36a66e5dd7f25b9907654759917bce59a2ce2d3e02e7ccdb0977f0653bb043c90aa73b0"
}