pull down to refresh

34 sats \ 1 reply \ @Bitcoiner1 10h \ on: Quick questions about OP_RETURN? Quick answers here. bitcoin
What do you support? Unlimited Core or Knots further restricting OP_RETURN?
write
preview
0 sats \ 0 replies \ @Murch 3h
I think it is a reasonable idea to drop the OP_RETURN limit at this time. I left the following concept ACK:
Concept ACK on removing the limit on OP_RETURN size and count.
The limit on OP_RETURNs size is ineffectual, causes increased node traffic, and drives mining centralization. While I have no personal desire for more large OP_RETURNs on the blockchain, it is preferable to have data be written into OP_RETURNs than the UTXO set, and it is preferable to see the transactions I’m competing with in my mempool, than to incentivize build-out of mechanisms for direct submission to the largest mining pools.
Regarding Knots, I would not let my money be touched by a node that is maintained by a single developer as a side project via picking open (unfinished) Bitcoin Core pull requests to a 1000+ commit patch set.
reply