v0.1.3

Verify before you install

Every artifact here is signed with GitHub build provenance — a Sigstore attestation binding the
file's digest to this repository, this workflow, and the commit that built it. There is no
maintainer key to fetch and no trust-on-first-use step.

gh attestation verify BTCPayServer.Plugins.Flint.btcpay --repo sethforprivacy/flint

Offline, against the attestation.jsonl bundle attached below rather than GitHub's API:

gh attestation verify BTCPayServer.Plugins.Flint.btcpay \
  --bundle attestation.jsonl --repo sethforprivacy/flint

SHA256SUMS is attested too, so it can be trusted once verified. One quirk: BTCPay's PluginPacker
writes it with a single space between hash and filename. GNU sha256sum -c accepts that; macOS's
shasum -a 256 -c rejects the whole file, so on macOS compare shasum -a 256 <file> by eye.

Installing

Server settings → Plugins → Upload plugin, and select BTCPayServer.Plugins.Flint.btcpay.
BTCPay restarts itself to finish. Requires BTCPay Server 2.4.1 or newer, on a non-Alpine host.

Read CHANGELOG.md for what is in this
release and how far it has actually been proven, and the
trust model, before you put money
through it.

What's Changed

• Label sweep transactions in the wallet; move deposits behind Advanced by @sethforprivacy in #16
• Release 0.1.3 by @sethforprivacy in #17

Full Changelog: v0.1.2...v0.1.3

v0.1.2

Verify before you install

Every artifact here is signed with GitHub build provenance — a Sigstore attestation binding the
file's digest to this repository, this workflow, and the commit that built it. There is no
maintainer key to fetch and no trust-on-first-use step.

gh attestation verify BTCPayServer.Plugins.Flint.btcpay --repo sethforprivacy/flint

Offline, against the attestation.jsonl bundle attached below rather than GitHub's API:

gh attestation verify BTCPayServer.Plugins.Flint.btcpay \
  --bundle attestation.jsonl --repo sethforprivacy/flint

SHA256SUMS is attested too, so it can be trusted once verified. One quirk: BTCPay's PluginPacker
writes it with a single space between hash and filename. GNU sha256sum -c accepts that; macOS's
shasum -a 256 -c rejects the whole file, so on macOS compare shasum -a 256 <file> by eye.

Installing

Server settings → Plugins → Upload plugin, and select BTCPayServer.Plugins.Flint.btcpay.
BTCPay restarts itself to finish. Requires BTCPay Server 2.4.1 or newer, on a non-Alpine host.

Read CHANGELOG.md for what is in this
release and how far it has actually been proven, and the
trust model, before you put money
through it.

What's Changed

• chore(deps): Bump Microsoft.NET.Test.Sdk from 18.8.1 to 18.9.0 by @dependabot[bot] in #10
• chore(deps): Bump xunit.runner.visualstudio from 3.1.5 to 4.0.0 by @dependabot[bot] in #11
• Move the tests to Microsoft.Testing.Platform, and take xunit.v3 4.0.0 by @sethforprivacy in #13
• Slim the merchant-facing UI ahead of going public by @sethforprivacy in #14
• Release 0.1.2 by @sethforprivacy in #15

Full Changelog: v0.1.1...v0.1.2

v0.1.1

Verify before you install

Every artifact here is signed with GitHub build provenance — a Sigstore attestation binding the
file's digest to this repository, this workflow, and the commit that built it. There is no
maintainer key to fetch and no trust-on-first-use step.

gh attestation verify BTCPayServer.Plugins.Flint.btcpay --repo sethforprivacy/flint

Offline, against the attestation.jsonl bundle attached below rather than GitHub's API:

gh attestation verify BTCPayServer.Plugins.Flint.btcpay \
  --bundle attestation.jsonl --repo sethforprivacy/flint

SHA256SUMS is attested too, so it can be trusted once verified. One quirk: BTCPay's PluginPacker
writes it with a single space between hash and filename. GNU sha256sum -c accepts that; macOS's
shasum -a 256 -c rejects the whole file, so on macOS compare shasum -a 256 <file> by eye.

Installing

Server settings → Plugins → Upload plugin, and select BTCPayServer.Plugins.Flint.btcpay.
BTCPay restarts itself to finish. Requires BTCPay Server 2.4.1 or newer, on a non-Alpine host.

Read CHANGELOG.md for what is in this
release and how far it has actually been proven, and the
trust model, before you put money
through it.

What's Changed

• Serialise CI builds: fix the deps.json write race the v2.4.2 bump exposed by @sethforprivacy in #3
• Bump btcpayserver submodule: v2.4.1 -> v2.4.2 by @github-actions[bot] in #4
• Update README to remove status and limitations by @sethforprivacy in #1
• Queue funded regtest runs instead of letting them collide on the shared wallet by @sethforprivacy in #5
• Put a caution callout back on the README front page by @sethforprivacy in #6
• chore(deps): Bump Breez.Sdk.Spark from 0.19.2 to 0.22.0 by @dependabot[bot] in #8
• Release 0.1.1 by @sethforprivacy in #9

New Contributors

• @sethforprivacy made their first contribution in #3
• @github-actions[bot] made their first contribution in #4
• @dependabot[bot] made their first contribution in #8

Full Changelog: v0.1.0...v0.1.1

v0.1.0

Verify before you install

Every artifact here is signed with GitHub build provenance — a Sigstore attestation binding the
file's digest to this repository, this workflow, and the commit that built it. There is no
maintainer key to fetch and no trust-on-first-use step.

gh attestation verify BTCPayServer.Plugins.Flint.btcpay --repo sethforprivacy/flint

Offline, against the attestation.jsonl bundle attached below rather than GitHub's API:

gh attestation verify BTCPayServer.Plugins.Flint.btcpay \
  --bundle attestation.jsonl --repo sethforprivacy/flint

SHA256SUMS is attested too, so it can be trusted once verified. One quirk: BTCPay's PluginPacker
writes it with a single space between hash and filename. GNU sha256sum -c accepts that; macOS's
shasum -a 256 -c rejects the whole file, so on macOS compare shasum -a 256 <file> by eye.

Installing

Server settings → Plugins → Upload plugin, and select BTCPayServer.Plugins.Flint.btcpay.
BTCPay restarts itself to finish. Requires BTCPay Server 2.4.1 or newer, on a non-Alpine host.

Read CHANGELOG.md for what is in this
release and how far it has actually been proven, and the
trust model, before you put money
through it.

Full Changelog: https://github.com/sethforprivacy/flint/commits/v0.1.0