Kevin's Bacon on Nostr: So about the OP_RETURN and filters debate, this is something I had been worried about ...
So about the OP_RETURN and filters debate, this is something I had been worried about with Bitcoin for a while: I knew there needed to be a feedback mechanism where information about the cost of the data used for noderunning was communicated to the network, where each individual node could communicate prices in a market. I realized eventually that it does have this, but it's rough: the consensus and the specific code of the machines. We might need to engineer an upgrade that will allow easier price setting that doesn't give anyone unilateral control, like a typical market but one that is distributed, anonymized, and failsafe.
Published at
2025-05-11 14:29:13Event JSON
{
"id": "81ca09394c82a99dd5d974d9d2c0702f59dc7fc18e99db75f28a9aaa9fb15410",
"pubkey": "3dda45008a0391d7933e1ae7cc3b844bfd91c92ddefd0f55ce6afd025776f2db",
"created_at": 1746973753,
"kind": 1,
"tags": [],
"content": "So about the OP_RETURN and filters debate, this is something I had been worried about with Bitcoin for a while: I knew there needed to be a feedback mechanism where information about the cost of the data used for noderunning was communicated to the network, where each individual node could communicate prices in a market. I realized eventually that it does have this, but it's rough: the consensus and the specific code of the machines. We might need to engineer an upgrade that will allow easier price setting that doesn't give anyone unilateral control, like a typical market but one that is distributed, anonymized, and failsafe.",
"sig": "5efb906c8098ff0ea39b0d58f9db9b5f33daf6f6a20a88289c81e178ad52347847cdea49ef3ba5071054689bcceffa27a8277162ac979644ae68eddc0847b510"
}
