Nick

Also running into this issue

Any news on this? I would love to be able to use pgbouncer for my SQLX apps

I fixed this by removing the following block from each affected pod with init probes. ``` hostNetwork: true # To resolve services in the namespace dnsPolicy: ClusterFirstWithHostNet ```

Replace serde + serde_derive + serde_json with miniserde

In the works :) Will be a separate package but will leverage all of bsv-wasm

Hey @xhliu I'm aiming to have something usable for you in about 2 weeks time. I'll keep you posted

I think there is a bug with OP_PICK, I will look into it

Thanks for the issue, here's a new build for you to try out. I'll aim to get a release pipeline for 2.0 out eventually. https://github.com/Firaenix/bsv-wasm/blob/split-modules/packages/bsv-wasm/pkg/bsv-wasm%20node%202.0.0%20alpha.zip

I was under the impression that any OP_IF must have an OP_ELSE followed by an OP_ENDIF, according to the BSV Wiki https://wiki.bitcoinsv.io/index.php/Opcodes_used_in_Bitcoin_Script If this is untrue, I can change this

I'm not 100% certain, but it's worth checking against the Bitcoin SV node interpreter so get it 100% correct