Description

This would make all the tests possible to run locally.
It enhances developer experience and facilitates onboarding of new contributors.

Additions:

• Crate auditing capabilities using rustsec/advisory-db.
• Local and CI caching of all artifacts from running cargo {check,build,test} in the whole workspace.
  Superseds .github/workflows/audit.yml.
• Pre-commit checks for everything that we enforce (gpg-signed/conventional commits, and some goodies like typos, so docs: fix spelling errors #1086 kind of things are not necessary anymore)
• Instructions and rationale in NIX.md

Closes bitcoindevkit/bdk_wallet#129.
Superseds #1122 and #1156.

Pinneds Dependencies:

• bitcoind: pinned to 0.25.0
• electrs: pinned to Blockstream's esplora using the Fedimint deployment, check jkitman/nixpkgs@61ccef8 and https://github.com/fedimint/fedimint/blob/master/flake.nix#L5

TODO:

• Fix llvm deps.
• Fix openssl errors.
• Fix dependencies on MacOS.
• Fix WASM.
• Fix MSRV.
  Add a custom CargoMSRV.lock? (Or maybe a CargoMSRV.toml with the pinned MSRV dependencies and then cargo generate-lockfile with Rust MSRV?)
  Depends on solving fix: build crane-utils using a different toolchain ipetkov/crane#422
• move all the logic from cont_integration.yml to flake.nix (all the cargo update -p)
  From the Fedimint suggestion we'll use crane.
  This would allow caching of a lot of things
  Then the user would call nix buid -L .#MSRV --keep-failed and so on.
  This would also eliminate all the multiple runs-on in cont_integration.yml to a single one where each step would be a name and run the nix build command.
• Add DeterminateSystems/magic-nix-cache-action to cache stuff in CI.
• Update CONTRIBUTING with instructions. Use fedimint instructions for inspiration.
• nix develop:
  • default: Rust latest
  • MSRV
  • WASM
• nix flake check:
  • clippy
  • audit
  • rustfmt
  • Rust latest test
    • --all-features
    • --no-default-features
  • MSRV test
    • --all-features
    • --no-default-features
  • WASM (--target wasm32-unknown-unknown) test
    • -p bdk --no-default-features --features bitcoin/no-std,miniscript/no-std,bdk_chain/hashbrown,dev-getrandom-wasm
    • -p esplora --target wasm32-unknown-unknown --no-default-features --features bitcoin/no-std,miniscript/no-std,bdk_chain/hashbrown,async
  • cachix/pre-commit-hooks.nix
    • signed commits
    • conventional commits with commitizen
    • typos
    • rustfmt
• Add a CI to update Cargo.lock (is this possible?)
• Add a CI to update flake.lock
• Delete .github/workflows/audit.yml
• Port Code Coverage to Nix
• Nixify the Nightly Docs CI
• Add numtide/devshell
• Clean up commit messages (this is a mess of squash fixup and ammends 😂)

Nix Commands

• nix flake show: show all possible commands from the flake.
• nix develop: creates a devShell with all the things you need to develop installed.
  Also handles ENV vars.
  Currently is bash, git, ripgrep, bitcoind (pinned), electrs (pinned), openssl, pkg-config, libiconv, and latest stable Rust with all goodies.
  It also handles specific MacOS deps: Apple XCode SDKs (for bitcoind and electrsd crates).
  Open to suggestions on what to include.
  • nix develop .#MSRV: same but with Rust MSRV.
• nix flake check:
  • checks for typos, gpg-signed commits, conventional commits, rustfmt, nixpkgs-fmt (.nix files).
  • runs clippy in all workspace (pinned to 1.67.0) with --all-features --all-targets -- -D warnings.
  • runs cargo check in all workspace (latest stable Rust).
  • checks dependencies for security advisory using rustsec/advisory-db.
  • test everything!!! (see below the individual checks in .#checks.${system}.{CHECK}
• nix build -L .: runs cargo build in all workspace with latest stable Rust.
  • nix build -L .#stable: runs cargo build in all workspace with latest stable Rust.
  • nix build -L .#MSRV: runs cargo build in all workspace with MSRV stable Rust.
  • PLACEHOLDER: ...
• nix build -L .#checks.${system}.{CHECK}: runs a specific CHECK. In my case system = aarch64-darwin then it is nix build .#checks.aarch64-darwin.CHECK.
  • pre-commit-check: checks for typos, conventional commits, nixpkgs-fmt (.nix files).
  • clippy: runs clippy in all workspace (pinned to 1.68.0) with --all-features --all-targets -- -D warnings.
  • fmt: runs cargo fmt with --all -- --check --config format_code_in_doc_comments=true in all workspace with latest Rust.
  • audit: checks dependencies for security advisory using rustsec/advisory-db.
  • latest: cargo build in whole workspace using latest Rust.
  • latestAll: cargo test --all-features in whole workspace using latest Rust.
  • latestNoDefault: cargo test --no-default-features in whole workspace using latest Rust.
  • latestNoStdBdk: cargo test -p bdk --no-default-features --features bitcoin/no-std,miniscript/no-std,bdk_chain/hashbrown using latest Rust.
  • latestNoStdChain: cargo test -p bdk_chain --no-default-features --features bitcoin/no-std,miniscript/no-std,hashbrown using latest Rust.
  • latestNoStdEsplora: cargo test -p bdk_esplora --no-default-features --features bitcoin/no-std,miniscript/no-std,bdk_chain/hashbrown using latest Rust.
  • MSRV: cargo build in whole workspace using MSRV Rust.
  • MRSVAll: cargo test --all-features in whole workspace using MSRV Rust.
  • MSRVNoDefault: cargo test --no-default-features in whole workspace using MSRV Rust.
  • MSRVNoStdBdk: cargo test -p bdk --no-default-features --features bitcoin/no-std,miniscript/no-std,bdk_chain/hashbrown using MSRV Rust.
  • MRSVNoStdChain: cargo test -p bdk_chain --no-default-features --features bitcoin/no-std,miniscript/no-std,hashbrown using MSRV Rust.
  • MSRVNoStdEsplora: cargo test -p bdk_esplora --no-default-features --features bitcoin/no-std,miniscript/no-std,bdk_chain/hashbrown using MSRV Rust.

Notes to the reviewers

1. We are adding automatic pre-commit checks with checks for typos, gpg-signed commits, conventional commits, nixpkgs-fmt (.nix files).
   This is done automatically if the user has Nix and devshell installed.
   If not, it will be checked on CI, or with a nix flake check.
   I fixed a bunch of typos and added the .typos.toml to whitelist somethings like hashes, addresses, etc that were being flagged as false positives.

2. I am adding in the building cache/tests a crate name and version.
   This does not interact with the name or versioning in any of bdk's crates Cargo.toml

   To avoid this nasty warning in Nix:

   trace: warning: crane will use a placeholder value since `name` cannot be found in /nix/store/ja4yr1m9ba72gy3pbr2vg540zjdbzp33-source/Cargo.toml
   to silence this warning consider one of the following:
   - setting `pname = "...";` in the derivation arguments explicitly
   - setting `package.name = "..."` or `workspace.package.name = "..."` in the root Cargo.toml
   - explicitly looking up the values from a different Cargo.toml via
     `craneLib.crateNameFromCargoToml { cargoToml = ./path/to/Cargo.toml; }`

3. We are using legacyPackages instead of packages in the ci build calls because legacyPackages allows nested sets, e.g.:

   legacyPackages = ci = {
     latest = {
       all = ...;
       noDefault = ...;
       ...
     };
     MSRV = { ... };
     WASM = { ... };
     codeCoverage = ...;
   };

   It makes a nice grouping of all CI stuff under the same call:

   nix build -L .#ci.latest.{CHECK}

4. Removed the ci/ dir with the Dockerfiles for hardware signer testing.
   We are not using them, removed in bdk v1.0.0-alpha.0 #793,
   more specifically in 3f5a78a.
   Related Move hardware signer into its own crate #872.
   NOTE: speculos can be run under Nix

   • https://github.com/alamgu/speculos/tree/with-nix-build
   • Add shell.nix LedgerHQ/speculos#323

5. We are moving from mozilla/grcov to taiki-e/cargo-llvm-cov.
   Why? 3 reasons:

   1. Mozilla's grcov is a big thing, it does coverage for a lot of things C/C++, JS, Java, and Rust.
      cargo-llvm-cov uses Rust's native coverage tools via LLVM.
   2. crane (craneLib.cargoLlvmCov) supports natively cargo-llvm-cov which will be much easier to make it work and maintain
   3. Our friends at fedimint also use cargo-llvm-cov with crane so it makes easier to collaborate in improvements and issues.

Potential issues:

• We had to remove Cargo.lock from the .gitignore. Nix (crane) needs it for deterministic stuff.
  From the crane FAQ:

  First consider if there is a release of this project available with a lock file as it may be simpler and more consistent to use the exact dependencies published by the project itself. Projects published on crates.io always come with a lock file and nixpkgs has a fetchCrate fetcher which pulls straight from crates.io.

  Also Rust changed their Cargo.lock commit policy a couple months ago:

  For years, the Cargo team has encouraged Rust developers to commit their Cargo.lock file for packages with binaries but not libraries. We now recommend people do what is best for their project. To help people make a decision, we do include some considerations and suggest committing Cargo.lock as a starting point in their decision making. To align with that starting point, cargo new will no longer ignore Cargo.lock for libraries as of nightly-2023-08-24. Regardless of what decision projects make, we encourage regular testing against their latest dependencies.

• Mismatch versions between the executables under the *_EXEC env vars for bitcoind/electrsd crates and the version the crate thinks to have.

• Centralizes CI maintainability to people that have Nix experience.

• We are removing the auto-download feature of bitcoind and electrsd in the bitcoind_rpc and esplora crates. I added an explanation in the repo and crates' README.mds. This also simplifies a little bit the MSRV pinning of deps.

Changelog notice

Checklists

All Submissions:

• I've signed all my commits
• I followed the contribution guidelines
• I ran cargo fmt and cargo clippy before committing

New Features:

• I've added tests for the new feature
• I've added docs for the new feature

Bugfixes:

• This pull request breaks the existing API
• I've added tests to reproduce the issue which are now passing
• I'm linking the issue being fixed by this PR