Please join us for our next Socratic Seminar! A special thanks to Strike for the event space.
Doors open at 6pm with discussion starting shortly after!
https://github.com/toneloc/stable-channels
https://x.com/tonklaus/status/1918258692337676433
“The recent pull request to bitcoin core made by peter todd (pull 32359) removes the code to enforce a policy limit on the size and number of OP_RETURN outputs. Additionally, he proposes the removal of the configuration options to allow node runners to modify the maximum size of data carrying transactions.”
@OrangeSurfBTC
intro to bitcoin policy by OrangeSurfBTC
saving the mempool by benthecarman
Antoine Poinsot’s rationale
gmaxwell bitcointalk post
Bitcoin Core OP_RETURN Direction
Remove arbitrary limits on OP_Return (datacarrier) outputs #32359
policy: uncap datacarrier by default #32406 <– does not remove configuration options
Bitcoin Mailing List Discussion
Visuals from 0x_orkun
https://delvingbitcoin.org/t/op-checkcontractverify-and-its-amount-semantic/1527
Poisson Blocks DoS vector in Bitcoin at OP_NEXT by PortlandHODL
PortlandHODL demoes a Poisson Blocks DoS vector in Bitcoin at OP_NEXT. This attack vector creates a block that takes a good performance node 25 minutes to validate. Though in practice this is not feasible from an incentives perspective it does show the need for a cleanup of legacy consensus rules in Bitcoin.