pull down to refresh

10 sats \ 6 replies \ @Scoresby 27 Jun \ parent \ on: Hunter Beast - Dev, Rust, Bitcoin AMA

So now I'm curious how we will avoid the same fate for quantum resistance soft forks. It seems like the infinite bikeshed (which could be a great horror story concept) will strike again.

How do we avoid it?

write
compose
112 sats \ 5 replies \ @cryptoquick OP 27 Jun

Well, that's already happened, considering 360 took a massive amount of review and back and forth, and even then, the work is still not finished.

But QR efforts have something going for them that covenants do not: a real world forcing function.

reply
462 sats \ 4 replies \ @optimism 27 Jun

What is currently missing in 360?

reply
181 sats \ 3 replies \ @cryptoquick OP 27 Jun

We need to finish the 110 compatibility effort, address SegWit spending rule ambiguity, and scrub the BIP of any of Isabel Foxen Duke's "contributions".

reply
360 sats \ 2 replies \ @optimism 27 Jun

Can you give an example where the BIP itself is not agnostic to 110? I must have missed something!

reply
181 sats \ 1 reply \ @cryptoquick OP 27 Jun

There are a few things we need to change to comply with the 7 changes in 110:

  • SegWit v2 cannot create a new place for annex data
  • Instead of using OP_SUCCESS, we overload usage the six OP_CHECKSIG* type opcodes to allow for multiple algorithms (proving that this does not introduce other problems is taking some time)
  • Witness bytes for lengthy PQ sigs must be chunked into groups of 256 bytes

It's a challenging problem but not impossible to solve.

reply
133 sats \ 0 replies \ @optimism 27 Jun

Wait you lost me. Are you saying that you want to rewrite 360 back to not just p2mr - i.e. more like it was before the last total rewrite?

reply