Dan Gould

Here's the requested log with `RUST_LOG=debug RUST_BACKTRACE=1 ./contrib/test_local.sh` [nix-bitcoind-mac-fail.log](https://github.com/user-attachments/files/18593676/nix-bitcoind-mac-fail.log) I'm also perplexed by tests failing when I run just the v2 suite in this configuration: ```log running 5 tests test...

valkey is the obvious candidate that comes to mind.

Unfortunately `sled` hasn't been maintained for 2 years which I reasoned was OK for `payjoin-cli` since it's a bit of a demo tool, but probably not ok for the aspirationally...

Noting this isn't really so much tech debt as it is maintenance. When the dependency was taken on it was state of the art, and the state of the art...

Another thing I'd really like with this is environments for `payjoin-ffi` languages where we can just call `payjoin-ffi/python/contrib/test.sh` like we do with all of the other targets. This is a...

On this topic, Does it then make sense to use sqlite's in-memory :memory: database to keep our dependency tree simpler if we're going to use it for payjoin-cli #867 #873?...

@thebrandonlucas I do want a nix flake that provides the environment for us to compile, release, and run language bindings and their tests. Ideally everything was in a single top...

@nothingmuch reinforced to me that indeed each language can have its own flake that composes at the top level and recommended https://github.com/the-nix-way/dev-templates as a reference.

At this point nix integration tests seem to be the priority. We're struggling with dart/redis/docker combo and eliminating docker would be a great help in that it would let us...

Fixed by #448