Jonathan Underwood

Actually..... perhaps this should be done at a lower level: https://github.com/bitcoin-core/secp256k1/issues/1015

There are examples of projects using asmjs in order to shim wasm into React Native. https://github.com/polkadot-js/wasm/blob/v4.4.1/packages/wasm-crypto/src/bridge.ts#L14-L32 However, this is something that should be implemented in tiny-secp256k1 itself. Perhaps we would...

I don't think that's what this solution is using. While getting WASM to work on RN is "hacky af" for the implementer, tiny-secp256k1 native JS code was hacky af and...

yes. you just won't be able to use schnorr.

> I have a fork for this: https://github.com/nahoc10/bip39-esm-support Pull requests welcome, but it seems like your fork completely breaks everything with no attempt to try and maintain compatibility via a...

Looking into the matter further, it seems like there is a common thread is users "unstaking everything" into our deposit address, which results in a UTXO with ADA and non-ADA...

Also, our deposit addresses are all cold multisig, and moving funds outside of pre-determined whitelists requires a firmware update (which we won't develop, as it would lower security) requires multiple...

Looking into the issue further, an increasing number of instances has been occurring, and every single time the customer was unaware that native assets were being sent. (They didn't even...

Using output descriptors with Bitcoin Core directly sounds like the best path forward. https://github.com/bitcoin/bitcoin/blob/v25.0/doc/descriptors.md

Also, I don't see any questions... Just an explanation of something you wanted to make. Are you just going to leave this open until someone makes this thing for you,...