jgriffiths

>If there are wallets that do this inconsistently, I'm inclined to think those wallets should use relative paths. The problem is that there is no concept of full vs relative...

> But when m is present we can assume it's absolute? Or not? Unfortunately not, see e.g https://github.com/rust-bitcoin/rust-bitcoin/blob/master/src/util/bip32.rs#L414 where a derived key of depth 1 is further derived using an...

Hi @benma We do have plans for supporting receiving and spending from taproot outputs. However at this stage we are still in the planning stage of how we will structure...

Hi @ChristopherA long time no chat, hope you are well. Wally supports paying to P2TR outputs already, I assume you mean support for receiving and spending from taproot inputs. Its...

Note that the parsing code still allocates a large buffer for each child when generating scripts; I intend to fix this by computing the exact required length up-front in the...

> I'm sorry. The implementation is totally suitable for typical use, please don't apologise! My desire to reduce these allocations is only for the special case of using wally on...

Note: Moving back to WIP, I think we need a couple more features.

> For the Miniscript part, how about we look into making https://github.com/sipa/miniscript/ a library and exposing a C API? C++ code is not acceptable for wally, and our implementation requirements...

> Is it still WIP? What is left to be done there? Any way i can help this work to move forward? Hi @darosior sorry for the late reply. This...

Hi @weedcoder This error is indicating that wally was not compiled with `-DBUILD_ELEMENTS=1` on the command line. `Makefile` sets this in `CFLAGS` for you so please check your build environment...