State/matureness of library

[SomberNight]

I would like to ask about the current state of this library. In the README, I see you say:

WIP: this is not ready for any real use!
This library is still a work in progress. It contains known bugs (in the satisfier for instance) and there are probably many unknown ones.

Is this still the case? Could you elaborate a bit here?
Also, do you plan to use (/or are you already using) this library in production yourself?

Thank you for your work and this library as-is!

[darosior]

Hey, thanks for the interest. I've been working on-and-off on this library for a while but my goal has been to eventual have something that can be reasonably used by others. I've been constrained by time a lot lately and every single improvement here came with some hurdles (for instance i had to introduce support for BIP340 into coincurve before even supporting Taproot here, thereby having to understand how the binding sausage is made internally which took almost all my allocated time budget to implement TapMiniscript..). But it's really not that far, so if you are interested in this, contributions are vey welcome and i'll make sure to take some time to review them. What were you thinking of using this for?

The main flaw of this library currently is that the satisfier does not consider non-malleable satisfactions at all, i've started tackling it in #26 but it turned out to be more invasive than i had anticipated and paused the work for now.

I have been using it under specific conditions in the Revault and Liana functional test frameworks. I would advise against using it in prod for now, but that might change if it gets some attention.