Mischa

Mischa's avatar
Mischa
npub1htpl...axzv
Working in Switzerland as an automation technician with a passion for studying Bitcoin
It is correct that before Core v30, miners could also include large OP_RETURN transactions in blocks, but that choice was made by clearly identifiable actors. Miners are public-facing companies. Deliberately mining large OP_RETURN data could lead to reputational damage, loss of hashrate, and in extreme cases legal consequences. That acted as a natural social and economic brake. With the opening of OP_RETURN, responsibility shifts from individual miners to the network as a whole. Every node now relays these transactions, regardless of their content. This removes clear attribution to a responsible actor. What used to be a conscious choice by a few miners becomes a structural property of the protocol. Large OP_RETURN data and inscriptions increase storage, bandwidth, and computational requirements. That raises the cost of running a node. Over time, fewer people can afford to operate their own nodes, which weakens decentralization and concentrates influence among large operators. In the long run, this can alter Bitcoin’s level of decentralization and change the balance of power within the network.
I really like the idea behind Fanfares. I tested the reward-sharing mechanism with a second account, but it didn’t work as expected. Here’s what I noticed: I was using the Brave browser, and I’m wondering if having cookies disabled prevents rewards from working. When I logged in with my second account, the public key was correct, but the Lightning address shown was different from the one in Primal. I tried logging in twice and got the same result. Also, when I first clicked the link, I was automatically logged in with a new account. In the browser. After that, I switched to my real one. Could that have confused the reward-sharing mechanism or caused it to link the wrong account? @Short Fiat