Next step?

[xloem]

What's the next change needed to polyglot to move it forward?

[AustEcon]

Whatever you feel like basically. Good candidates are the things on the README roadmap.

UTXO management

• https://github.com/AustEcon/bsvbip32 needs to be ported to use exclusively bitcoinx and then I want the "leaf" keys of the Bip32 tree to be wrapped by bitsv.PrivateKey classes with some kind of API that is intuitive and user-friendly... That unlocks more sophisticated utxo management capabilities...

HTML reference converter tool

Bitsv also needs some work (discussion here: AustEcon/bitsv#52) to handle arbitrary scripts (not just OP_FALSE OP_RETURN ones)... I might look to add bitcoinx as a dependency in some shape or form to help with building custom scripts as well...

Other protocols?

I am open to suggestions!
Thanks for the help thus far 😃

Most of my time is going on this: https://github.com/electrumsv/electrumsv-sdk
At the moment + other projects that take priority... But happy to review PRs.

[xloem]

Thanks; I had missed the README roadmap somehow. Too used to looking straight at the code.

I visited bitcoinx and it seems to have some really powerful features that overlap with some of the features of bitsv. Would it fit in as a dependency of polyglot or a dependency of bitsv?

[AustEcon]

I'm happy to have bitcoinx as a dependency. I know that code well. It is used heavily by electrumsv wallet too.