You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now v1 forces P2SH encoding, at least for MPMA transactions. Both v1 and v2 should default to multi-sig, since P2SH is unreliable (#2270#1383). (It's also probably more expensive in many cases, because it uses multiple transactions.) All of this is a stopgap, given we're gonna be doing all encoding using witness data in the near future (cf. #1375).
The text was updated successfully, but these errors were encountered:
So it turns out that our P2SH encoding no longer works with recent versions of Bitcoin Core. It was the default only when use_old_api=False was specified. This is causing loss of user funds. Here's the test demonstrating that: #2283
In addition, there were two other bugs in the P2SH implementation:
Right now v1 forces P2SH encoding, at least for MPMA transactions. Both v1 and v2 should default to multi-sig, sinceP2SH is unreliable (#2270 #1383). (It's also probably more expensive in many cases, because it uses multiple transactions.) All of this is a stopgap, given we're gonna be doing all encoding using witness data in the near future (cf. #1375).The text was updated successfully, but these errors were encountered: