BTC Support?

[bitjson]

If anyone is interested in using Bitauth IDE to develop BTC authentication templates, please comment here.

The application is architected to make switching between VMs possible, it just requires a bit of development work to activate.

[cernael]

Yes please.
I'm currently trying to sketch out a multisig scheme for BTC, and while I probably won't end up becoming too exotic, it would be good to be able to easily verify that I've not accidentally gotten dependent on a BCH-only quirk. :-)

[qertoip]

I would also very much welcome BTC support. Your IDE is great!

[as1ndu]

Hi everyone. What exactly needs to be done? Is there a comprehensive list on what’s pending?

[bitjson]

Hey @as1ndu – I'd love to take pull requests enabling BTC. The biggest challenge is getting the BTC virtual machine implemented in bitcoin-ts. Implementing the virtual machine in bitcoin-ts allows us to step through and examine the evaluation of a program (see this blog post for an example of usage on BCH). It also provides meaningful error messages and other helpful information that VM implementations used in full nodes don't typically offer.

Once the BTC virtual machine is implemented in bitcoin-ts, adding BTC support to the IDE should be quite easy. (The IDE is designed to allow drop-in support for any VM implementation which supports the bitcoin-ts VM interface.)

A good part of the BTC VM is already implemented, there are just a few major components which aren't implemented:

• At the time of the fork, BCH dropped support for the original signing serialization algorithm (on BTC, the pre-SegWit algorithm), but BTC still supports that algorithm outside of SegWit programs. So to create a correct implementation, we'll need to implement it (including the known bugs).
• Also, SegWit support needs to be added. It's a relatively small change in the context of the VM (we're not adding support to e.g. a full node), but the challenge will be ensuring it is correct.

So we're actually quite close to full BTC support, it's just the last 10% that needs to be completed before we can say we have a "correct" implementation. Generally, as long as you're not doing unusual things (like using the deprecated signing algorithm), you can do development in the IDE against the BCH VM (without using the new opcodes added by BCH), and your scripts will work fine on BTC.

You can see how the BCH VM is implemented in this directory. As you dig around, you'll find a great deal of it comes from the common VM directory, which includes all the components which are shared between BTC, BCH, BSV, and other Bitcoin forks.

The outline of the BTC VM is here, but I don't have any immediate plans to finish it myself. I'd love to take pull requests! And I'm very happy to answer questions or help in any way.

[bitjson]

I'm currently trying to sketch out a multisig scheme for BTC, and while I probably won't end up becoming too exotic, it would be good to be able to easily verify that I've not accidentally gotten dependent on a BCH-only quirk. :-)

@cernael – if you're still working on this, feel free to share your script in the telegram group, I'd be happy to help.

[as1ndu]

thanks @bitjson

[arshbot]

At the time of the fork, BCH dropped support for the original signing serialization algorithm (on BTC, the pre-SegWit algorithm)

What algo is this referring to?

[A60AB5450353F40E]

What algo is this referring to?

Signature preimage building algo: https://documentation.cash/protocol/forks/replay-protected-sighash