pull down to refresh

0 sats \ 1 reply \ @robin_linus 7h \ parent \ on: Quick questions about OP_RETURN? Quick answers here. bitcoin
To that end, they intend to write a proof into the Bitcoin blockchain every ten minutes. This proof takes 100 bytes of data. Their current plan is to write that data into one OP_RETURN output accompanied by a fake pubkey hash
That's a common misconception. Indeed, Citrea is frequently writing a state diff and a corresponding proof into the blockchain, but they are using inscriptions for that. Those OP_RETURN transactions are something different. They are used only in case of a dispute during pegout for watchtowers to provide a chainstate proof for a heavier chain than the one the operator claimed to be the canonical chain.
These OP_RETURN transactions likely never hit the chain because there are strong disincentives for operators to make any invalid claims. Thus, ironically, lifting the OP_RETURN limit hardly has any effect in practice. It barely effects the Citrea protocol and it likely doesn't effect what kinds of transactions we see in the chain.
write
preview
0 sats \ 0 replies \ @anon 5h
Isn't this why they need it to be standard though? Because those transactions need to be reliable and can't afford to wait for friendly miner which may take longer than the thief.
reply