bitcoin-dev

Congestion Control via OP_CHECKOUTPUTSHASHVERIFY proposal

Congestion Control via OP_CHECKOUTPUTSHASHVERIFY proposal

Original Postby Anthony Towns

Posted on: May 22, 2019 20:49 UTC

In a bitcoin-dev thread, ZmnSCPxj expressed their opinion that the CoinJoin feature is not much improved by a recent opcode addition.

However, one user countered that this feature could make it easier to do a coinjoin during a high fee period and still claim funds later. The user also added that coordination may not be made much easier by this addition unless the coinjoin group stays in a Layer 2-ish protocol and coordinates to cut-through transactions. The user provided an example of how this could work but added that it comes with much harder coordination problems.Regarding the replacement of SIGHASH_NOINPUT with the new opcode, the same user disagrees with this idea. They believe that this does not replace ANYPREVOUT or similar features. They also think that lightning is improved by this opcode because it makes it cheaper to create lightning channels during a high fee period. Users can create 1000 channels via a single output with this opcode and wait until there's a low fee period to publish the funding transaction cheaply. The user thinks that eltoo could also be slightly simplified with this opcode.