Repository navigation
Releases
v0.7.5
v0.7.5
The macOS download is signed with a Developer ID certificate and notarized by Apple, so it installs with a normal double-click. The Windows and Linux downloads are unsigned: their guarantee is provenance, not a certificate — every asset was built from this exact commit in one gated workflow run, is covered by the CI-generated SHA256SUMS and its release-key signature SHA256SUMS.asc, and carries a GitHub Sigstore build attestation. See SIGNING.md.
Built from main at commit b254fe6f6fc724f25e0c40658bd430c4bffaedcb.
- Opens an existing BSMS native-SegWit multisig wallet with two or three physical keys; the file defines the quorum, and the app checks its public balance.
- Prepares a partial send with a declared change branch or the guarded
standard BIP48 /1/* branch anchored by the BSMS first receive address.
Unsupported layouts can explicitly Send All without change. Shows final outputs and fee. - Refuses inferred change when a bare wildcard matches the first address
directly instead of anchoring the BIP48 /0/0 receiving branch. - Uses bundled HWI 3.2.0 over stdin to request the number of hardware signatures required by the BSMS quorum.
Only signatures verifying against the reviewed PSBT are retained;
signer-returned metadata is discarded before finalization. - Gives each device discovery and authorization check up to three minutes and deliberate on-device signing
up to ten minutes, including Ledger's multiple review screens. - Offers Bitcoin mainnet plus the Testnet4 and Mutinynet practice networks
through one engine. The practice networks are a test bench for developers,
not what this app is for. A custom-Signet checkpoint distinguishes Mutinynet
from ordinary Signet.
A new Mutinynet wallet and practice coins are required; Testnet4 coins
do not transfer across networks. - Opens on Bitcoin mainnet. The practice networks are reached only through
the "Enter Developer Mode" gate on the opening screen, which asks for
confirmation first and lasts for the session: the app reopens on mainnet.
Inside the gate the choice is Mutinynet or Testnet4: live Bitcoin is the
network the gate returns to, not one of its options.
Send All is never preselected; a nonstandard wallet without an established
change branch explains why a smaller payment is unavailable. - Clears old signer/final details whenever a new payment is prepared,
including the network the retired final screen was bound to.
Rechecks selected confirmed outputs before preparation and broadcast;
a lost broadcast response is treated as outcome unknown, never retried. - Broadcasts on the selected network after a separate confirmation. Mainnet
submission needs one explicit confirmation on the final screen and a backend
opt-in that fails closed when omitted. It never asks for a PIN or seed. - Saves an optional unsigned PSBT and an opt-in privacy-limited diagnostic
report. Dependencies are hash-locked; native libusb digest is required.
Downloads — every platform built from this exact commit in one gated run:
Bitcoin-Easy-Signer-v0.7.5-macOS.dmg— macOS, Apple SiliconBitcoin-Easy-Signer-v0.7.5-windows-x64.zip— Windows x64Bitcoin-Easy-Signer-v0.7.5-linux-x86_64.AppImage— Linux x86_64Bitcoin-Easy-Signer-v0.7.5-linux-x86_64.tar.gz— Linux x86_64, unpackagedbitcoin-easy-multisig-signer-v0.7.5.tar.gz— source
Verify any download against SHA256SUMS and its release-key signature
SHA256SUMS.asc (the public key is signing-key.asc in this repository),
and check each file's GitHub Sigstore build attestation.
BUILD-SBOM.json, BUILD-SBOM-windows-x64.json and
BUILD-SBOM-linux-x86_64.json inventory each packaged environment and its
native libusb.
Use at your own risk. Bitcoin Easy Signer is free, open-source software
maintained by Bitseeker LLC, without warranty or guarantee. Real Bitcoin can be
sent from this build: verify the destination, amount and fee on your signing
devices before approving, and treat an unconfirmed payment as unfinished.
Hardware signers commonly hide the change output, so check the change address
in the wallet software that holds the wallet file, not on a device screen.
Bitcoin Easy Signer 0.7.5
This release answers the Color Team cycle-11 audit of the v0.7.4 tree, which
graded
v0.7.3 findings are converted by execution: the referee personally re-broke
the 4xx→unknown branch and the unknown-conversion branch, watched each named pin go
red, restored the copy byte-for-byte and watched it go green. All forty-four
earlier findings were carried with no regression.
The grade is held by two missing alarm tests, not by a defect. CT-47 is the
settings-refusal branch of the not-sent boundary: when the configured Esplora URL
is not a plain URL the app refuses to send, and because that happens before the
request is written the reviewed payment stays retryable — the right behaviour, but
no test could fail if the branch regressed. CT-49 is the same control's claim about
position: the existing pin checked which exception each input shape raises, not
that no request object had been built, so moving a refusal below the point of no
return would have kept the suite green.
Nothing the operator had not reviewed was ever signed or sent in any version of
this software. This release changes no transaction construction, signing, fee or
network rule, and no button does anything new. Three of its five scheduled items are
tests; the other two are a type guard at the engine's own entry point and one
raise that keeps a Ctrl-C distinguishable from a lost reply.
This release closes CT-45, CT-46, CT-47, CT-49 and CT-51, records the three notes
the audit called housekeeping (CT-48, CT-50, CT-52) and restates the two carried
ones (CT-38, CT-44). Each is in releases/PATCH-0.7.5.md row by row, with its
closing test and its break-and-watch result, and every control the cycle touches was
broken on a disposable copy and watched red before being restored
(releases/BREAK-AND-WATCH-0.7.5.md).
What changed
- The settings refusal now has an alarm. A settings-rejected Esplora URL is a
provable non-send: the app refuses before writing anything and the reviewed
payment stays retryable. The new test drives three rejected URL shapes through the
engine and asserts the refusal class and that no request was opened. RowCM-50. - The not-sent boundary's position is pinned. A second test patches the request
constructor and the opener, drives five pre-POST refusals, and asserts neither was
ever called — so the claim "the refusal happens before the point of no return" is
now a test rather than a comment. RowCM-50. - The engine refuses non-contract argument types. A non-string chain or hex
passed directly to the engine used to escape as a rawTypeErroror
AttributeError; both are now the not-sent refusal, because nothing can have been
written at that point. The app's own call sites are unchanged. RowCM-50. - A deliberate abort stays a deliberate abort. If the submit is interrupted
(Ctrl-C, interpreter shutdown) the wallet is still paused and the payment still
recorded — bytes may have left — but theKeyboardInterruptis re-raised
unchanged instead of being reported as an unknown broadcast outcome. RowCM-46. - The newest release window's history is pinned. The automatic record test now
reads the newest row ofRELEASE-HISTORY.mdand requires every run id and the
counts in it, the same way the 0.7.3 row is held, so a window cannot under-count
itself silently again. Tests intests/test_hardening_pins.py.
Verification
The suite is 744 tests, green in the checkout and in the extracted source archive;
all eleven page-script suites pass; CONTROLS.md is 50 rows with every row bound to
a marker inside its own range and to a test the build loads. Every claim above was
broken on a disposable copy, watched red, restored byte-for-byte and watched green.
What this release does not claim
It does not claim the settings branch or the boundary's position could fail in
production at 0.7.4 — they could not, and the referee executed both. It claims the
suite would have stayed green if they had, which is the clause the audit's grade
binds on, and that is now false. It does not weaken the release gate: the Apple
notarization staple is still required, and a failure still publishes nothing.
v0.7.4
v0.7.4
The macOS download is signed with a Developer ID certificate and notarized by Apple, so it installs with a normal double-click. The Windows and Linux downloads are unsigned: their guarantee is provenance, not a certificate — every asset was built from this exact commit in one gated workflow run, is covered by the CI-generated SHA256SUMS and its release-key signature SHA256SUMS.asc, and carries a GitHub Sigstore build attestation. See SIGNING.md.
Built from main at commit 9d4d7bb471c80512cac7b7dc6c014855393cac4f.
- Opens an existing BSMS native-SegWit multisig wallet with two or three physical keys; the file defines the quorum, and the app checks its public balance.
- Prepares a partial send with a declared change branch or the guarded
standard BIP48 /1/* branch anchored by the BSMS first receive address.
Unsupported layouts can explicitly Send All without change. Shows final outputs and fee. - Refuses inferred change when a bare wildcard matches the first address
directly instead of anchoring the BIP48 /0/0 receiving branch. - Uses bundled HWI 3.2.0 over stdin to request the number of hardware signatures required by the BSMS quorum.
Only signatures verifying against the reviewed PSBT are retained;
signer-returned metadata is discarded before finalization. - Gives each device discovery and authorization check up to three minutes and deliberate on-device signing
up to ten minutes, including Ledger's multiple review screens. - Offers Bitcoin mainnet plus the Testnet4 and Mutinynet practice networks
through one engine. The practice networks are a test bench for developers,
not what this app is for. A custom-Signet checkpoint distinguishes Mutinynet
from ordinary Signet.
A new Mutinynet wallet and practice coins are required; Testnet4 coins
do not transfer across networks. - Opens on Bitcoin mainnet. The practice networks are reached only through
the "Enter Developer Mode" gate on the opening screen, which asks for
confirmation first and lasts for the session: the app reopens on mainnet.
Inside the gate the choice is Mutinynet or Testnet4: live Bitcoin is the
network the gate returns to, not one of its options.
Send All is never preselected; a nonstandard wallet without an established
change branch explains why a smaller payment is unavailable. - Clears old signer/final details whenever a new payment is prepared,
including the network the retired final screen was bound to.
Rechecks selected confirmed outputs before preparation and broadcast;
a lost broadcast response is treated as outcome unknown, never retried. - Broadcasts on the selected network after a separate confirmation. Mainnet
submission needs one explicit confirmation on the final screen and a backend
opt-in that fails closed when omitted. It never asks for a PIN or seed. - Saves an optional unsigned PSBT and an opt-in privacy-limited diagnostic
report. Dependencies are hash-locked; native libusb digest is required.
Downloads — every platform built from this exact commit in one gated run:
Bitcoin-Easy-Signer-v0.7.4-macOS.dmg— macOS, Apple SiliconBitcoin-Easy-Signer-v0.7.4-windows-x64.zip— Windows x64Bitcoin-Easy-Signer-v0.7.4-linux-x86_64.AppImage— Linux x86_64Bitcoin-Easy-Signer-v0.7.4-linux-x86_64.tar.gz— Linux x86_64, unpackagedbitcoin-easy-multisig-signer-v0.7.4.tar.gz— source
Verify any download against SHA256SUMS and its release-key signature
SHA256SUMS.asc (the public key is signing-key.asc in this repository),
and check each file's GitHub Sigstore build attestation.
BUILD-SBOM.json, BUILD-SBOM-windows-x64.json and
BUILD-SBOM-linux-x86_64.json inventory each packaged environment and its
native libusb.
Use at your own risk. Bitcoin Easy Signer is free, open-source software
maintained by Bitseeker LLC, without warranty or guarantee. Real Bitcoin can be
sent from this build: verify the destination, amount and fee on your signing
devices before approving, and treat an unconfirmed payment as unfinished.
Hardware signers commonly hide the change output, so check the change address
in the wallet software that holds the wallet file, not on a device screen.
Bitcoin Easy Signer 0.7.4
This release answers the Color Team cycle-10 audit of the v0.7.3 tree, which
graded
referee personally re-broke CT-27's marker arm and its clear, CT-29's reconcile and
CT-33's transport tuple, and watched each named pin go red; CT-32, CT-34 and CT-35
were closed by written dated owner acceptance; and all twenty-six earlier findings
were carried with no regression. The grade holds on two new findings in the delta.
CT-36 (Medium) is the one that matters. broadcast_transaction treated every
HTTP 4xx as a definite refusal: the payment had not been sent, so the wallet
stayed retryable and the in-flight marker was cleared. But a 4xx arrives after
the server has the complete signed transaction — an honest Esplora answers exactly
that way when it already holds the payment — so a second, differently reviewed
payment of the same wallet could leave with the pause the previous cycle added
never armed. One examiner demonstrated that end to end and the referee
re-executed it. Nothing the operator had not reviewed was ever signed; this is
a classification defect in what the app told itself about a reply, not a
substitution or a forged payment.
CT-41 (Low) is the missing alarm behind the early in-flight half of the same
gate: deleting that half left every named pin green, because the request simply
fell through to the in-lock half and was refused there. The protection worked; the
test that was supposed to hold it could not fail.
This release closes CT-36, CT-37 (the same defect in its raw-exception form),
CT-41, CT-43 (the previous window's history under-counted its runs) and the two
inventory gaps CT-39 and CT-40. Each is in releases/PATCH-0.7.4.md row by row,
with its closing test and its break-and-watch result, and every control the cycle
touches was broken on a disposable copy and watched red before being restored
(releases/BREAK-AND-WATCH-0.7.4.md).
This release changes app behaviour in one direction: a payment whose outcome the
app cannot prove is now treated as unknown, not as refused. It does not change
how an honest payment is prepared, signed, checked or broadcast, or which networks
are offered, or the fee ceilings. The engine's wire behaviour is unchanged — only
its classification of an answer.
What changed
- A status code is not proof that nothing was sent. Only the checks that run
before the request is written — unsupported network, missing mainnet opt-in,
unusable size, invalid hex, a settings refusal — raiseBroadcastNotSent, and
those keep the reviewed payment retryable because the app can prove it never
left. Everything after the bytes are handed over, 4xx included, raises
BroadcastOutcomeUnknown, carries the server's own words as evidence, records
the payment against the wallet and pauses it with one sentence: "The broadcast
result is unknown: the server answered HTTP 400 after receiving this payment, so
it may already have been accepted. Do not send this payment again. Check the
transaction on an explorer or ask for help before proceeding." RowsCM-49and
CM-50. - Anything else that escapes the submit is treated the same way. A raw failure
from the submit path — aRuntimeError, a bug, an uncatalogued exception — is
converted to the unknown outcome under the same lock, because it proves nothing
about whether bytes were written. The fail-safe direction is the pause. Row
CM-46. - The early in-flight half now has its own alarm. The test arms the marker
before the request and asserts the refusal, the message, that the broadcaster was
never called, and that no explorer was asked about the wallet's outputs. Row
CM-38. - The previous window is disclosed as it happened. The v0.7.3 row in
RELEASE-HISTORY.mdnow names all five dispatched runs and nine attempts — the
cancelled dispatch, the candidate built without notarization that the promote's
manifest check refused, the two failed attempts inside the macOS job — with the
plain statement that nothing was published from any failure. A new pin reads that
row and fails if any run id or either count goes missing. - Two protections that had no row now have one. The final-versus-review
comparison (CM-47) and thepreparation_idbinding on the money endpoints
(CM-48) were real — the panel broke both and watched them refuse — and
CONTROLS.mdis now at 50 rows, each bound by a test to a marker inside its
cited range. - Three notes are recorded, not fixed. The previous plan's stale test
citation (CT-38), the lying-txid residual that keeps a wallet paused (CT-42) and
the legacy-tag inventory (CT-44), each with where this cycle records it.
Downloads
Verify every download against SHA256SUMS and its SHA256SUMS.asc. The release
carries one checksum file covering macOS, Windows and Linux, plus
BUILD-SBOM.json. See SIGNING.md for the signature and provenance policy, and
releases/platform-state.json for the platform posture this release was built
under.
v0.7.3
v0.7.3
The macOS download is signed with a Developer ID certificate and notarized by Apple, so it installs with a normal double-click. The Windows and Linux downloads are unsigned: their guarantee is provenance, not a certificate — every asset was built from this exact commit in one gated workflow run, is covered by the CI-generated SHA256SUMS and its release-key signature SHA256SUMS.asc, and carries a GitHub Sigstore build attestation. See SIGNING.md.
Built from main at commit a227da4073f705cbb4ca47f939e80fc0921c77d7.
- Opens an existing BSMS native-SegWit multisig wallet with two or three physical keys; the file defines the quorum, and the app checks its public balance.
- Prepares a partial send with a declared change branch or the guarded
standard BIP48 /1/* branch anchored by the BSMS first receive address.
Unsupported layouts can explicitly Send All without change. Shows final outputs and fee. - Refuses inferred change when a bare wildcard matches the first address
directly instead of anchoring the BIP48 /0/0 receiving branch. - Uses bundled HWI 3.2.0 over stdin to request the number of hardware signatures required by the BSMS quorum.
Only signatures verifying against the reviewed PSBT are retained;
signer-returned metadata is discarded before finalization. - Gives each device discovery and authorization check up to three minutes and deliberate on-device signing
up to ten minutes, including Ledger's multiple review screens. - Offers Bitcoin mainnet plus the Testnet4 and Mutinynet practice networks
through one engine. The practice networks are a test bench for developers,
not what this app is for. A custom-Signet checkpoint distinguishes Mutinynet
from ordinary Signet.
A new Mutinynet wallet and practice coins are required; Testnet4 coins
do not transfer across networks. - Opens on Bitcoin mainnet. The practice networks are reached only through
the "Enter Developer Mode" gate on the opening screen, which asks for
confirmation first and lasts for the session: the app reopens on mainnet.
Inside the gate the choice is Mutinynet or Testnet4: live Bitcoin is the
network the gate returns to, not one of its options.
Send All is never preselected; a nonstandard wallet without an established
change branch explains why a smaller payment is unavailable. - Clears old signer/final details whenever a new payment is prepared,
including the network the retired final screen was bound to.
Rechecks selected confirmed outputs before preparation and broadcast;
a lost broadcast response is treated as outcome unknown, never retried. - Broadcasts on the selected network after a separate confirmation. Mainnet
submission needs one explicit confirmation on the final screen and a backend
opt-in that fails closed when omitted. It never asks for a PIN or seed. - Saves an optional unsigned PSBT and an opt-in privacy-limited diagnostic
report. Dependencies are hash-locked; native libusb digest is required.
Downloads — every platform built from this exact commit in one gated run:
Bitcoin-Easy-Signer-v0.7.3-macOS.dmg— macOS, Apple SiliconBitcoin-Easy-Signer-v0.7.3-windows-x64.zip— Windows x64Bitcoin-Easy-Signer-v0.7.3-linux-x86_64.AppImage— Linux x86_64Bitcoin-Easy-Signer-v0.7.3-linux-x86_64.tar.gz— Linux x86_64, unpackagedbitcoin-easy-multisig-signer-v0.7.3.tar.gz— source
Verify any download against SHA256SUMS and its release-key signature
SHA256SUMS.asc (the public key is signing-key.asc in this repository),
and check each file's GitHub Sigstore build attestation.
BUILD-SBOM.json, BUILD-SBOM-windows-x64.json and
BUILD-SBOM-linux-x86_64.json inventory each packaged environment and its
native libusb.
Use at your own risk. Bitcoin Easy Signer is free, open-source software
maintained by Bitseeker LLC, without warranty or guarantee. Real Bitcoin can be
sent from this build: verify the destination, amount and fee on your signing
devices before approving, and treat an unconfirmed payment as unfinished.
Hardware signers commonly hide the change output, so check the change address
in the wallet software that holds the wallet file, not on a device screen.
Bitcoin Easy Signer 0.7.3
This release answers the Color Team cycle-9 audit of the v0.7.2 tree, which
graded ⛔ BLOCKED on one new Medium finding, CT-27. The v0.7.1
conversion criterion was met by execution — the referee re-broke CT-22, CT-24
and CT-25 and watched each named test go red, CT-23 and CT-26 closed by dated owner
acceptance, and all twenty-one earlier findings were carried with no regression —
but the code added for CT-22 placed its pause in the wrong place in time.
Both halves of the broadcast pause read a record that was written only after
the first broadcast returned, and that call is bounded by
BROADCAST_TIMEOUT_SECONDS = 20.0. While the first payment was on the wire the
pause was still empty, so a second, separately reviewed and consented payment
passed both halves and was broadcast. Two examiners demonstrated it end to end
through the real /api/* routes. Threat row T-11 forbids exactly that outcome, and
the framework's ruling 4 makes a T-11 violation blocking at any severity. Nothing
was signed that the operator had not reviewed: this was a sequencing defect, not a
substitution.
This release closes CT-27 and the false comment beside it (CT-28), makes the
pending record per-transaction (CT-29), adds one missing exception class to the
settings transport tuple (CT-33), and closes the two inventory gaps the audit named
(CT-30, CT-31). Each is in releases/PATCH-0.7.3.md row by row, with its closing
test and its break-and-watch result.
This release changes app behaviour. It does not change how an honest payment is
prepared, signed, checked or broadcast, or which networks are offered, or the fee
ceilings, and wallet_service.py changes only a docstring.
What changed
- The pause is armed before the money leaves, not after. A per-wallet in-flight
marker is set inside the same critical section that checks for it, and the lock is
released before the network call — so no slow broadcaster can stall the rest of
the app. Both halves of the pause read the marker: the early refusal, which runs
before any explorer is asked, and the one under the pre-submit lock. Every exit
clears it, so a refused payment is still there to retry. The operator sees one
fixed sentence: "A payment from this wallet is still being submitted. Wait for
that result before sending another." Three tests pin it — a held broadcast, a
marker armed mid-request so only the in-lock read can refuse, and a definite
refusal that must leave nothing armed — and all three were break-and-watched.
RowsCM-38andCM-43. - The pause remembers every payment, not just the last one. The record is now a
dictionary per wallet in submission order, and a refresh clears only the
transactions the explorer reports confirmed. A second completed payment can no
longer overwrite the first, and confirming the newer one can no longer lift the
pause the older one still needs. RowCM-44. - A connection reset mid-reply is the documented refusal, not a generic
failure.verify_esplora's tuple now carriesOSError, the class a
ConnectionResetErrorbelongs to, matching the explorer and broadcaster tuples
that already do. A real-socket test resets the connection after the reply head,
because the older tests stubbedurlopenand could not produce the shape. Row
CM-40. - The inventory now names both halves of the pause and the archive scan.
CM-38covers the early half,CM-43the check-and-arm,CM-44the reconcile,
andCM-45the source-archive secret scan — the control that stops a credential
reaching a tag, which had no row before.CONTROLS.mdis at 45 rows, each bound
by a test to a marker inside its cited range and to a test that loads. - Three record-keeping notes are recorded rather than left implicit. The
previous plan's line citations had gone stale (CT-32),explorer_get's
truncated-body contract is now documented at the function (CT-34), and the
previous release window's five failed candidate attempts are named in
RELEASE-HISTORY.mdandCURRENT-STATUS.md(CT-35).
Downloads
Verify every download against SHA256SUMS and its SHA256SUMS.asc. The release
carries one checksum file covering macOS, Windows and Linux, plus
BUILD-SBOM.json. See SIGNING.md for the signature and provenance policy, and
releases/platform-state.json for the platform posture this release was built
under.
v0.7.2
v0.7.2
The macOS download is signed with a Developer ID certificate and notarized by Apple, so it installs with a normal double-click. The Windows and Linux downloads are unsigned: their guarantee is provenance, not a certificate — every asset was built from this exact commit in one gated workflow run, is covered by the CI-generated SHA256SUMS and its release-key signature SHA256SUMS.asc, and carries a GitHub Sigstore build attestation. See SIGNING.md.
Built from main at commit 1e51dcfa45d6f61c83c14aeb1998725fbd705ba9.
- Opens an existing BSMS native-SegWit multisig wallet with two or three physical keys; the file defines the quorum, and the app checks its public balance.
- Prepares a partial send with a declared change branch or the guarded
standard BIP48 /1/* branch anchored by the BSMS first receive address.
Unsupported layouts can explicitly Send All without change. Shows final outputs and fee. - Refuses inferred change when a bare wildcard matches the first address
directly instead of anchoring the BIP48 /0/0 receiving branch. - Uses bundled HWI 3.2.0 over stdin to request the number of hardware signatures required by the BSMS quorum.
Only signatures verifying against the reviewed PSBT are retained;
signer-returned metadata is discarded before finalization. - Gives each device discovery and authorization check up to three minutes and deliberate on-device signing
up to ten minutes, including Ledger's multiple review screens. - Offers Bitcoin mainnet plus the Testnet4 and Mutinynet practice networks
through one engine. The practice networks are a test bench for developers,
not what this app is for. A custom-Signet checkpoint distinguishes Mutinynet
from ordinary Signet.
A new Mutinynet wallet and practice coins are required; Testnet4 coins
do not transfer across networks. - Opens on Bitcoin mainnet. The practice networks are reached only through
the "Enter Developer Mode" gate on the opening screen, which asks for
confirmation first and lasts for the session: the app reopens on mainnet.
Inside the gate the choice is Mutinynet or Testnet4: live Bitcoin is the
network the gate returns to, not one of its options.
Send All is never preselected; a nonstandard wallet without an established
change branch explains why a smaller payment is unavailable. - Clears old signer/final details whenever a new payment is prepared,
including the network the retired final screen was bound to.
Rechecks selected confirmed outputs before preparation and broadcast;
a lost broadcast response is treated as outcome unknown, never retried. - Broadcasts on the selected network after a separate confirmation. Mainnet
submission needs one explicit confirmation on the final screen and a backend
opt-in that fails closed when omitted. It never asks for a PIN or seed. - Saves an optional unsigned PSBT and an opt-in privacy-limited diagnostic
report. Dependencies are hash-locked; native libusb digest is required.
Downloads — every platform built from this exact commit in one gated run:
Bitcoin-Easy-Signer-v0.7.2-macOS.dmg— macOS, Apple SiliconBitcoin-Easy-Signer-v0.7.2-windows-x64.zip— Windows x64Bitcoin-Easy-Signer-v0.7.2-linux-x86_64.AppImage— Linux x86_64Bitcoin-Easy-Signer-v0.7.2-linux-x86_64.tar.gz— Linux x86_64, unpackagedbitcoin-easy-multisig-signer-v0.7.2.tar.gz— source
Verify any download against SHA256SUMS and its release-key signature
SHA256SUMS.asc (the public key is signing-key.asc in this repository),
and check each file's GitHub Sigstore build attestation.
BUILD-SBOM.json, BUILD-SBOM-windows-x64.json and
BUILD-SBOM-linux-x86_64.json inventory each packaged environment and its
native libusb.
Use at your own risk. Bitcoin Easy Signer is free, open-source software
maintained by Bitseeker LLC, without warranty or guarantee. Real Bitcoin can be
sent from this build: verify the destination, amount and fee on your signing
devices before approving, and treat an unconfirmed payment as unfinished.
Hardware signers commonly hide the change output, so check the change address
in the wallet software that holds the wallet file, not on a device screen.
Bitcoin Easy Signer 0.7.2
This release answers the Color Team cycle-8 audit of the v0.7.1 tree. That cycle
re-checked the conversion gate: the referee deleted three guards the previous cycle
had pinned, watched each named test go red, and confirmed all twenty-one earlier
findings fixed by execution; gui.py was AST-identical with docstrings
stripped and all seven engine files blob-identical at both tags. The grade was held
at CONDITIONAL by one new Low finding, CT-22: the pause that stops a
wallet sending a second payment while the first is unconfirmed was asserted at
preparation and not at the broadcast, so the second payment could be submitted
whenever the explorer stayed silent about the first spend. An honest explorer
refused it at the outspend recheck, which is why the finding is Low and not High,
but the pause exists exactly for the case where the explorer says nothing.
Two hardening margins were reported beside it and are fixed here as well, and two
record-keeping notes are recorded. Each finding this cycle closed is in
releases/PATCH-0.7.2.md row by row, with its closing test and its break-and-watch
result.
This release changes app behaviour, unlike the three before it. It does not
change how an honest payment is prepared, signed, checked or broadcast, or which
networks are offered, or the fee ceilings.
What changed
- The unconfirmed-payment pause now holds at the submit, not only at
prepare._broadcastrefuses when the wallet has a submitted payment waiting
for confirmation, before any explorer is asked, and re-asserts the same refusal
under the lock the submit takes so two requests that both reach the final screen
cannot both submit. The operator sees one fixed sentence on the final screen:
"A payment from this wallet is waiting for one confirmation. Check that it went
through before sending another." Two tests pin it — one that the early refusal
keeps the explorer out of the request, one that arms the pause mid-request so
only the in-lock check can refuse it — and both were break-and-watched. Row
CM-38. - A transaction that names the same Bitcoin output twice is refused. The app
already could not reach this state — the scan dedups, the builder and the
transaction-identity gate refuse it, and consensus relay would too — so this is
hardening rather than a fix to a live path. The refusal now happens before any
explorer is asked, with its own message. RowCM-39. - A network server that is not speaking HTTP is the documented refusal, not a
generic failure. The transport tuples now includehttp.client.HTTPException,
the shape a server produces when it hangs up mid-reply. The settings check, the
explorer read and the broadcaster all name it: on the first two it is the
documented "check its /api URL and availability" or "could not connect" refusal,
and on the broadcast path it remains an unknown outcome, which pauses the wallet
rather than inviting a retry that might double-send. Four socket-level tests pin
all three paths, because the older tests stubbedurlopenand could not produce
the shape. RowsCM-40,CM-41,CM-42. - Two record-keeping notes are recorded rather than left implicit. The audit
noted that the previous plan's line citations had gone stale at the revision it
read (the claims themselves verified true), and that the previous release's
documents named two of the three failure events in its window — the promote run's
failed first attempt was unnamed. Both are recorded inRELEASE-HISTORY.mdand
CURRENT-STATUS.md;CONTROLS.mdkeeps the pinned citations, and its test binds
every range to the marker inside it.
Downloads
Verify every download against SHA256SUMS and its SHA256SUMS.asc. The release
carries one checksum file covering macOS, Windows and Linux, plus
BUILD-SBOM.json. See SIGNING.md for the signature and provenance policy, and
releases/platform-state.json for the platform posture this release was built
under.
v0.7.1
v0.7.1
The macOS download is signed with a Developer ID certificate and notarized by Apple, so it installs with a normal double-click. The Windows and Linux downloads are unsigned: their guarantee is provenance, not a certificate — every asset was built from this exact commit in one gated workflow run, is covered by the CI-generated SHA256SUMS and its release-key signature SHA256SUMS.asc, and carries a GitHub Sigstore build attestation. See SIGNING.md.
Built from main at commit 8923ca0273380a9cb1ea7e7e964c6332dda5a777.
- Opens an existing BSMS native-SegWit multisig wallet with two or three physical keys; the file defines the quorum, and the app checks its public balance.
- Prepares a partial send with a declared change branch or the guarded
standard BIP48 /1/* branch anchored by the BSMS first receive address.
Unsupported layouts can explicitly Send All without change. Shows final outputs and fee. - Refuses inferred change when a bare wildcard matches the first address
directly instead of anchoring the BIP48 /0/0 receiving branch. - Uses bundled HWI 3.2.0 over stdin to request the number of hardware signatures required by the BSMS quorum.
Only signatures verifying against the reviewed PSBT are retained;
signer-returned metadata is discarded before finalization. - Gives each device discovery and authorization check up to three minutes and deliberate on-device signing
up to ten minutes, including Ledger's multiple review screens. - Offers Bitcoin mainnet plus the Testnet4 and Mutinynet practice networks
through one engine. The practice networks are a test bench for developers,
not what this app is for. A custom-Signet checkpoint distinguishes Mutinynet
from ordinary Signet.
A new Mutinynet wallet and practice coins are required; Testnet4 coins
do not transfer across networks. - Opens on Bitcoin mainnet. The practice networks are reached only through
the "Enter Developer Mode" gate on the opening screen, which asks for
confirmation first and lasts for the session: the app reopens on mainnet.
Inside the gate the choice is Mutinynet or Testnet4: live Bitcoin is the
network the gate returns to, not one of its options.
Send All is never preselected; a nonstandard wallet without an established
change branch explains why a smaller payment is unavailable. - Clears old signer/final details whenever a new payment is prepared,
including the network the retired final screen was bound to.
Rechecks selected confirmed outputs before preparation and broadcast;
a lost broadcast response is treated as outcome unknown, never retried. - Broadcasts on the selected network after a separate confirmation. Mainnet
submission needs one explicit confirmation on the final screen and a backend
opt-in that fails closed when omitted. It never asks for a PIN or seed. - Saves an optional unsigned PSBT and an opt-in privacy-limited diagnostic
report. Dependencies are hash-locked; native libusb digest is required.
Downloads — every platform built from this exact commit in one gated run:
Bitcoin-Easy-Signer-v0.7.1-macOS.dmg— macOS, Apple SiliconBitcoin-Easy-Signer-v0.7.1-windows-x64.zip— Windows x64Bitcoin-Easy-Signer-v0.7.1-linux-x86_64.AppImage— Linux x86_64Bitcoin-Easy-Signer-v0.7.1-linux-x86_64.tar.gz— Linux x86_64, unpackagedbitcoin-easy-multisig-signer-v0.7.1.tar.gz— source
Verify any download against SHA256SUMS and its release-key signature
SHA256SUMS.asc (the public key is signing-key.asc in this repository),
and check each file's GitHub Sigstore build attestation.
BUILD-SBOM.json, BUILD-SBOM-windows-x64.json and
BUILD-SBOM-linux-x86_64.json inventory each packaged environment and its
native libusb.
Use at your own risk. Bitcoin Easy Signer is free, open-source software
maintained by Bitseeker LLC, without warranty or guarantee. Real Bitcoin can be
sent from this build: verify the destination, amount and fee on your signing
devices before approving, and treat an unconfirmed payment as unfinished.
Hardware signers commonly hide the change output, so check the change address
in the wallet software that holds the wallet file, not on a device screen.
Bitcoin Easy Signer 0.7.1
This release answers the Color Team cycle-7 audit of the v0.7.0 tree. That
cycle re-checked the previous grade: the panel verified all eighteen earlier
findings fixed by execution — the referee re-broke each fix and watched its
new test go red — and held the grade at CONDITIONAL on two new
Informational findings, both of them in the same pin-accuracy family: a claimed
control whose shipped test could not fail. It also recorded one further
Informational observation, about the connection ceiling's availability trade,
which the owner accepted and asked to have described accurately.
The wallet, transaction, signing and broadcast engine is unchanged: no capability
is added and no refusal message moves. This release also folds in the owner's
terms of use, which are documentation, not behaviour. Each finding this cycle
closed is recorded row by row, with its closing test and its break-and-watch
result, in releases/PATCH-0.7.1.md.
What changed
-
The loopback server's retired-connection guard now has a test that can fail.
When a connection is retired by the fair-admission rule, the server closes it
without answering, so the operator's console sees no broken-pipe traceback. That
guard had no test, so it could have been deleted without anything going red. The
new test drives a retired connection with a malformed request: with the guard in
place the client receives no bytes at all, and without it the server would have
answered with an HTTP 400. The same request on a live connection still gets its
400, which is the half of the behaviour that must not change. -
The control inventory now reads the GitHub workflow files.
CONTROLS.md
parses the code that ships, and it did not parse.github/workflows/, so three
claimed guards in the release workflow were invisible to it: the retired-publisher
pagination guard, the notarisation credential guard, and the checksum-signing
guard. The workflow is now in scope, each of those guards is a tracked row
(CM-33…CM-35) with a marker inside the range it cites, and the two
credential guards each have an executable pin that runs the workflow step and
refuses the exact way the workflow refuses. -
The busy-slot docstring now says what the slot actually requires. The
comment claimed that a busy connection needs the page's access token; the slot
is actually held from the moment a complete request head has arrived, token or
not. The comment now matches the code, and the corrected sentence is pinned by
two tests — one asserting that a tokenless complete head claims the slot (and
is then refused by the route), one asserting that a half-sent head claims
nothing — so the description cannot drift away from the code again. -
The terms of use are updated.
DISCLAIMER.mdis now the project's copy of
the Bitseeker LLC Standard Software Disclaimer & Limitation of Liability
published at cjtsh/software-disclaimer,
with the Bitcoin Easy Signer specifics folded in: the warranty disclaimer, the
limitation of liability, the limited indemnity, the Wyoming governing law and
forum provisions, the assumption of risk, and the statement that this notice is
general information and not legal advice. The README, the user manual, the
download page and the app's About box link to it.A notice alone may not establish contractual assent. The app presents no
acceptance gate, because adding one would change the software; whoever
distributes, hosts or deploys it is responsible for obtaining whatever assent
their distribution and jurisdiction require.
Downloads
Verify every download against SHA256SUMS and its SHA256SUMS.asc. The release
carries one checksum file covering macOS, Windows and Linux, plus
BUILD-SBOM.json. See SIGNING.md for the signature and provenance policy, and
releases/platform-state.json for the platform posture this release was built
under.
v0.7.0
v0.7.0
The macOS download is signed with a Developer ID certificate and notarized by Apple, so it installs with a normal double-click. The Windows and Linux downloads are unsigned: their guarantee is provenance, not a certificate — every asset was built from this exact commit in one gated workflow run, is covered by the CI-generated SHA256SUMS and its release-key signature SHA256SUMS.asc, and carries a GitHub Sigstore build attestation. See SIGNING.md.
Built from main at commit 4fe8f2955e29cae6838e2ba0b8029c9abae9fdeb.
- Opens an existing BSMS native-SegWit multisig wallet with two or three physical keys; the file defines the quorum, and the app checks its public balance.
- Prepares a partial send with a declared change branch or the guarded
standard BIP48 /1/* branch anchored by the BSMS first receive address.
Unsupported layouts can explicitly Send All without change. Shows final outputs and fee. - Refuses inferred change when a bare wildcard matches the first address
directly instead of anchoring the BIP48 /0/0 receiving branch. - Uses bundled HWI 3.2.0 over stdin to request the number of hardware signatures required by the BSMS quorum.
Only signatures verifying against the reviewed PSBT are retained;
signer-returned metadata is discarded before finalization. - Gives each device discovery and authorization check up to three minutes and deliberate on-device signing
up to ten minutes, including Ledger's multiple review screens. - Offers Bitcoin mainnet plus the Testnet4 and Mutinynet practice networks
through one engine. The practice networks are a test bench for developers,
not what this app is for. A custom-Signet checkpoint distinguishes Mutinynet
from ordinary Signet.
A new Mutinynet wallet and practice coins are required; Testnet4 coins
do not transfer across networks. - Opens on Bitcoin mainnet. The practice networks are reached only through
the "Enter Developer Mode" gate on the opening screen, which asks for
confirmation first and lasts for the session: the app reopens on mainnet.
Inside the gate the choice is Mutinynet or Testnet4: live Bitcoin is the
network the gate returns to, not one of its options.
Send All is never preselected; a nonstandard wallet without an established
change branch explains why a smaller payment is unavailable. - Clears old signer/final details whenever a new payment is prepared,
including the network the retired final screen was bound to.
Rechecks selected confirmed outputs before preparation and broadcast;
a lost broadcast response is treated as outcome unknown, never retried. - Broadcasts on the selected network after a separate confirmation. Mainnet
submission needs one explicit confirmation on the final screen and a backend
opt-in that fails closed when omitted. It never asks for a PIN or seed. - Saves an optional unsigned PSBT and an opt-in privacy-limited diagnostic
report. Dependencies are hash-locked; native libusb digest is required.
Downloads — every platform built from this exact commit in one gated run:
Bitcoin-Easy-Signer-v0.7.0-macOS.dmg— macOS, Apple SiliconBitcoin-Easy-Signer-v0.7.0-windows-x64.zip— Windows x64Bitcoin-Easy-Signer-v0.7.0-linux-x86_64.AppImage— Linux x86_64Bitcoin-Easy-Signer-v0.7.0-linux-x86_64.tar.gz— Linux x86_64, unpackagedbitcoin-easy-multisig-signer-v0.7.0.tar.gz— source
Verify any download against SHA256SUMS and its release-key signature
SHA256SUMS.asc (the public key is signing-key.asc in this repository),
and check each file's GitHub Sigstore build attestation.
BUILD-SBOM.json, BUILD-SBOM-windows-x64.json and
BUILD-SBOM-linux-x86_64.json inventory each packaged environment and its
native libusb.
Use at your own risk. Bitcoin Easy Signer is free, open-source software
maintained by Bitseeker LLC, without warranty or guarantee. Real Bitcoin can be
sent from this build: verify the destination, amount and fee on your signing
devices before approving, and treat an unconfirmed payment as unfinished.
Hardware signers commonly hide the change output, so check the change address
in the wallet software that holds the wallet file, not on a device screen.
Bitcoin Easy Signer 0.7.0
This release answers the Color Team cycle-6 audit of the v0.6.9 tree. That
cycle was the conversion re-check of the previous grade: the panel verified all
twelve earlier findings fixed by execution — the referee re-broke each fix
and watched its new test go red — and held the grade at CONDITIONAL on one
new Low in the same pin-accuracy family that held the two cycles before it, plus
one availability trade the new connection ceiling had introduced.
The wallet, transaction, signing and broadcast engine is unchanged: no capability
is added and no refusal message moves. Each finding this cycle closed is recorded
row by row, with its closing test and its break-and-watch result, in
releases/PATCH-0.7.0.md.
What changed
- The build-time prevout match now has a test that can fail for each of its
limbs.wallet_service.pychecks three things about the previous transaction
an explorer serves: that it hashes to the claimed txid, that it pays the claimed
value, and that it pays the wallet's own script. The two tests named for the
value and script limbs were rewriting the transaction — which changes its txid —
so they were really testing the txid limb, and the audit demonstrated it by
deleting each limb and watching the suite stay green. Each limb now has a case
where the served transaction is untouched and the scanned UTXO list is the
liar, so only that limb can refuse it. - The connection ceiling no longer lets a local process freeze the app. The
ceiling from 0.6.9 closed every socket beyond its limit, so a local program
could hold all the slots and lock the operator's own window out. Admission is
now fair: a newcomer is refused only when every admitted connection is busy;
otherwise the oldest idle connection is hung up to make room. Silence and a
half-sent request head are both idle; only a connection actively being served
is protected, and serving one requires the page's access token. A surplus
connection with every slot busy is still refused, exactly as before. - Six protections are now tracked in
CONTROLS.mdasCM-27…CM-32— the
connection ceiling, the constant-time token comparison, the market-read token
gate, the token-history eviction, the bounded startup record, and the
per-connection time budget — each with a marker inside the range it cites and a
closing test the build loads. The inventory's claim-phrase net was widened to
the claim shapes those comments used, so the same omission is caught next time. - The retired-publisher guard fails closed on a partial list. It reads one
page of the platform's workflow registrations; it now refuses when the platform
reports more registrations than that page holds, or when the list it got does
not match the reported count, instead of concluding from a partial view. - The Windows startup dialog shows the same bounded record as the log. A
message box cannot be scrolled, so a very long platform error used to become a
dialog that ran off the screen; the full text is in the file the dialog names. - One sentence in the 0.6.9 record is corrected, in the open. The provenance
row for the vendored libusb DLL described its whole workflow file as differing
only in comments and a runner pin, which omitted the separate lock job's
hardening. The sentence is scoped to the job it is about, the rest of the delta
is enumerated, and the correction is marked inline and dated.
Downloads
Verify every download against SHA256SUMS and its SHA256SUMS.asc. The release
carries one checksum file covering macOS, Windows and Linux, plus
BUILD-SBOM.json. See SIGNING.md for the signature and provenance policy, and
releases/platform-state.json for the platform posture this release was built
under.
v0.6.9
v0.6.9
The macOS download is signed with a Developer ID certificate and notarized by Apple, so it installs with a normal double-click. The Windows and Linux downloads are unsigned: their guarantee is provenance, not a certificate — every asset was built from this exact commit in one gated workflow run, is covered by the CI-generated SHA256SUMS and its release-key signature SHA256SUMS.asc, and carries a GitHub Sigstore build attestation. See SIGNING.md.
Built from main at commit e90e5b93ece284f990ca2b75be1e798baa3efc9c.
- Opens an existing BSMS native-SegWit multisig wallet with two or three physical keys; the file defines the quorum, and the app checks its public balance.
- Prepares a partial send with a declared change branch or the guarded
standard BIP48 /1/* branch anchored by the BSMS first receive address.
Unsupported layouts can explicitly Send All without change. Shows final outputs and fee. - Refuses inferred change when a bare wildcard matches the first address
directly instead of anchoring the BIP48 /0/0 receiving branch. - Uses bundled HWI 3.2.0 over stdin to request the number of hardware signatures required by the BSMS quorum.
Only signatures verifying against the reviewed PSBT are retained;
signer-returned metadata is discarded before finalization. - Gives each device discovery and authorization check up to three minutes and deliberate on-device signing
up to ten minutes, including Ledger's multiple review screens. - Offers Bitcoin mainnet plus the Testnet4 and Mutinynet practice networks
through one engine. The practice networks are a test bench for developers,
not what this app is for. A custom-Signet checkpoint distinguishes Mutinynet
from ordinary Signet.
A new Mutinynet wallet and practice coins are required; Testnet4 coins
do not transfer across networks. - Opens on Bitcoin mainnet. The practice networks are reached only through
the "Enter Developer Mode" gate on the opening screen, which asks for
confirmation first and lasts for the session: the app reopens on mainnet.
Inside the gate the choice is Mutinynet or Testnet4: live Bitcoin is the
network the gate returns to, not one of its options.
Send All is never preselected; a nonstandard wallet without an established
change branch explains why a smaller payment is unavailable. - Clears old signer/final details whenever a new payment is prepared,
including the network the retired final screen was bound to.
Rechecks selected confirmed outputs before preparation and broadcast;
a lost broadcast response is treated as outcome unknown, never retried. - Broadcasts on the selected network after a separate confirmation. Mainnet
submission needs one explicit confirmation on the final screen and a backend
opt-in that fails closed when omitted. It never asks for a PIN or seed. - Saves an optional unsigned PSBT and an opt-in privacy-limited diagnostic
report. Dependencies are hash-locked; native libusb digest is required.
Downloads — every platform built from this exact commit in one gated run:
Bitcoin-Easy-Signer-v0.6.9-macOS.dmg— macOS, Apple SiliconBitcoin-Easy-Signer-v0.6.9-windows-x64.zip— Windows x64Bitcoin-Easy-Signer-v0.6.9-linux-x86_64.AppImage— Linux x86_64Bitcoin-Easy-Signer-v0.6.9-linux-x86_64.tar.gz— Linux x86_64, unpackagedbitcoin-easy-multisig-signer-v0.6.9.tar.gz— source
Verify any download against SHA256SUMS and its release-key signature
SHA256SUMS.asc (the public key is signing-key.asc in this repository),
and check each file's GitHub Sigstore build attestation.
BUILD-SBOM.json, BUILD-SBOM-windows-x64.json and
BUILD-SBOM-linux-x86_64.json inventory each packaged environment and its
native libusb.
Use at your own risk. Bitcoin Easy Signer is free, open-source software
maintained by Bitseeker LLC, without warranty or guarantee. Real Bitcoin can be
sent from this build: verify the destination, amount and fee on your signing
devices before approving, and treat an unconfirmed payment as unfinished.
Hardware signers commonly hide the change output, so check the change address
in the wallet software that holds the wallet file, not on a device screen.
Bitcoin Easy Signer 0.6.9
This release answers the Color Team cycle-5 audit of the v0.6.8 tree. That
cycle held everything the rubric asks a release to hold — the money path, the
devices, the pipeline, and the published bytes — and graded CONDITIONAL on
four Low findings. Each one described a control that was believed rather than
pinned: a branch no test could fail, three first-line guards tested only
through the deeper guard behind them, a download page that was corrected after
the tag instead of before it, and — most importantly — the inventory that is
supposed to catch exactly that class, which could not detect a citation moving
off its subject.
The wallet, transaction, signing, and broadcast engine is unchanged: no
capability is added, and no refusal message moves. Each finding this cycle
closed is recorded row by row, with its closing test, in
releases/PATCH-0.6.9.md.
What changed
CONTROLS.mdcitations are now content bindings, not line numbers that
happen to exist. Every one of the 26 rows carries its ownCONTROL: CM-##
marker inside the range it cites, and the build fails if a row's marker is
not inside its own range. Moving a citation onto an unrelated part of the
file — the referee's own trick against thev0.6.8tree — now fails.- The malformed-broadcast-body branch in
wallet_service.pyis pinned in
both directions: a response that is not a 64-hex transaction id raises
BroadcastOutcomeUnknown, and an upper-case id is accepted and lower-cased. - The three first-line money-path guards are pinned by name and message, so
each refusal keeps the sentence the operator reads, and each is separately
break-and-watchable. docs/index.htmlderives its release version from the same single source as
the app, under a test that refuses any download link, version label,
JSON-LD version or finding-record link naming another version — with one
download link required per platform.- The local access token no longer survives in the browser's session history:
the fragment is read once, kept in per-tab storage, and replaced out of the
address bar. A new page-script suite runs undernodeand is executed by
the Python suite, so the page scripts are evidence the ledger can cite. - A startup failure is logged as one bounded line instead of a traceback, so
the failure record no longer carries the operator's own paths. - The two market reads (
/api/price,/api/fees) require the local token,
like every other endpoint. - Concurrent connections are bounded; when the ceiling is reached the socket
is closed rather than queued. - GitHub immutable releases are enabled and recorded, so a change to that
setting is a visible diff rather than a browser fact. - A re-enabled retired publisher now refuses the run on both the candidate and
the publish path, and a registration read that did not happen also refuses. vendor/libusb-1.0.dllwas re-matched against the pin it ships under, from
the artifact the producing workflow itself had uploaded.
Downloads
Verify every download against SHA256SUMS and its SHA256SUMS.asc. The
release carries one checksum file covering macOS, Windows, and Linux, plus
BUILD-SBOM.json. See SIGNING.md for the signature and provenance
policy, and releases/platform-state.json for the platform posture this
release was built under.
v0.6.8
v0.6.8
The macOS download is signed with a Developer ID certificate and notarized by Apple, so it installs with a normal double-click. The Windows and Linux downloads are unsigned: their guarantee is provenance, not a certificate — every asset was built from this exact commit in one gated workflow run, is covered by the CI-generated SHA256SUMS and its release-key signature SHA256SUMS.asc, and carries a GitHub Sigstore build attestation. See SIGNING.md.
Built from main at commit 0d4e01f60c7695d720099f9d8e9e23b38da63102.
- Opens an existing BSMS native-SegWit multisig wallet with two or three physical keys; the file defines the quorum, and the app checks its public balance.
- Prepares a partial send with a declared change branch or the guarded
standard BIP48 /1/* branch anchored by the BSMS first receive address.
Unsupported layouts can explicitly Send All without change. Shows final outputs and fee. - Refuses inferred change when a bare wildcard matches the first address
directly instead of anchoring the BIP48 /0/0 receiving branch. - Uses bundled HWI 3.2.0 over stdin to request the number of hardware signatures required by the BSMS quorum.
Only signatures verifying against the reviewed PSBT are retained;
signer-returned metadata is discarded before finalization. - Gives each device discovery and authorization check up to three minutes and deliberate on-device signing
up to ten minutes, including Ledger's multiple review screens. - Offers Bitcoin mainnet plus the Testnet4 and Mutinynet practice networks
through one engine. The practice networks are a test bench for developers,
not what this app is for. A custom-Signet checkpoint distinguishes Mutinynet
from ordinary Signet.
A new Mutinynet wallet and practice coins are required; Testnet4 coins
do not transfer across networks. - Opens on Bitcoin mainnet. The practice networks are reached only through
the "Enter Developer Mode" gate on the opening screen, which asks for
confirmation first and lasts for the session: the app reopens on mainnet.
Inside the gate the choice is Mutinynet or Testnet4: live Bitcoin is the
network the gate returns to, not one of its options.
Send All is never preselected; a nonstandard wallet without an established
change branch explains why a smaller payment is unavailable. - Clears old signer/final details whenever a new payment is prepared,
including the network the retired final screen was bound to.
Rechecks selected confirmed outputs before preparation and broadcast;
a lost broadcast response is treated as outcome unknown, never retried. - Broadcasts on the selected network after a separate confirmation. Mainnet
submission needs one explicit confirmation on the final screen and a backend
opt-in that fails closed when omitted. It never asks for a PIN or seed. - Saves an optional unsigned PSBT and an opt-in privacy-limited diagnostic
report. Dependencies are hash-locked; native libusb digest is required.
Downloads — every platform built from this exact commit in one gated run:
Bitcoin-Easy-Signer-v0.6.8-macOS.dmg— macOS, Apple SiliconBitcoin-Easy-Signer-v0.6.8-windows-x64.zip— Windows x64Bitcoin-Easy-Signer-v0.6.8-linux-x86_64.AppImage— Linux x86_64Bitcoin-Easy-Signer-v0.6.8-linux-x86_64.tar.gz— Linux x86_64, unpackagedbitcoin-easy-multisig-signer-v0.6.8.tar.gz— source
Verify any download against SHA256SUMS and its release-key signature
SHA256SUMS.asc (the public key is signing-key.asc in this repository),
and check each file's GitHub Sigstore build attestation.
BUILD-SBOM.json, BUILD-SBOM-windows-x64.json and
BUILD-SBOM-linux-x86_64.json inventory each packaged environment and its
native libusb.
Use at your own risk. Bitcoin Easy Signer is free, open-source software
maintained by Bitseeker LLC, without warranty or guarantee. Real Bitcoin can be
sent from this build: verify the destination, amount and fee on your signing
devices before approving, and treat an unconfirmed payment as unfinished.
Hardware signers commonly hide the change output, so check the change address
in the wallet software that holds the wallet file, not on a device screen.
Bitcoin Easy Signer 0.6.8
This release answers the Color Team cycle-4 audit of the v0.6.7 tree. The
cycle's grade was set on the build process again: what the release
workflows install, and what they leave unchecked. The wallet, transaction,
signing, and broadcast engine is unchanged, and no new payment capability
is added. Each finding this cycle closed is recorded row by row, with its
closing test, in releases/PATCH-0.6.8.md.
What changed
- The audit ledger is a checked record instead of a convention. Every
finding the cycle's plan schedules must have exactly one row in
releases/PATCH-0.6.8.mdwith a severity, a fix, and a closing test the
build actually loads; a row may close without a test only for a deferral
the plan itself makes. The rows that had been closed by silence are
restored. CONTROLS.mdis the checked inventory of the security controls the app
relies on: the claim in plain English, the line that makes it, and the
test that would go red without it. A cited file, line or test that stops
existing, aCONTROL: CM-##marker with no row, or a comment that claims
a control and names no entry now fails the build.- The release process documents how to verify a release asset's
attestation. The API is indexed bysha256:digest rather than by tag,
and the note records the two misleading404shapes a reader can hit. - The launcher installs the device library from a checked lock file, so the
dependency set the source build runs is the one the repository pins. - The source archive ships
CONTROLS.md, and the check that reads the
archive's file list covers it.
Downloads
Verify every download against SHA256SUMS and its SHA256SUMS.asc. The
release carries one checksum file covering macOS, Windows, and Linux, plus
BUILD-SBOM.json. See SIGNING.md for the signature and provenance
policy.
v0.6.7
v0.6.7
The macOS download is signed with a Developer ID certificate and notarized by Apple, so it installs with a normal double-click. The Windows and Linux downloads are unsigned: their guarantee is provenance, not a certificate — every asset was built from this exact commit in one gated workflow run, is covered by the CI-generated SHA256SUMS and its release-key signature SHA256SUMS.asc, and carries a GitHub Sigstore build attestation. See SIGNING.md.
Built from main at commit 81f58ec0dd8c8afa8dcc2c1f69c10057e62dfe7b.
- Opens an existing BSMS native-SegWit multisig wallet with two or three physical keys; the file defines the quorum, and the app checks its public balance.
- Prepares a partial send with a declared change branch or the guarded
standard BIP48 /1/* branch anchored by the BSMS first receive address.
Unsupported layouts can explicitly Send All without change. Shows final outputs and fee. - Refuses inferred change when a bare wildcard matches the first address
directly instead of anchoring the BIP48 /0/0 receiving branch. - Uses bundled HWI 3.2.0 over stdin to request the number of hardware signatures required by the BSMS quorum.
Only signatures verifying against the reviewed PSBT are retained;
signer-returned metadata is discarded before finalization. - Gives each device discovery and authorization check up to three minutes and deliberate on-device signing
up to ten minutes, including Ledger's multiple review screens. - Offers Bitcoin mainnet plus the Testnet4 and Mutinynet practice networks
through one engine. The practice networks are a test bench for developers,
not what this app is for. A custom-Signet checkpoint distinguishes Mutinynet
from ordinary Signet.
A new Mutinynet wallet and practice coins are required; Testnet4 coins
do not transfer across networks. - Opens on Bitcoin mainnet. The practice networks are reached only through
the "Enter Developer Mode" gate on the opening screen, which asks for
confirmation first and lasts for the session: the app reopens on mainnet.
Inside the gate the choice is Mutinynet or Testnet4: live Bitcoin is the
network the gate returns to, not one of its options.
Send All is never preselected; a nonstandard wallet without an established
change branch explains why a smaller payment is unavailable. - Clears old signer/final details whenever a new payment is prepared,
including the network the retired final screen was bound to.
Rechecks selected confirmed outputs before preparation and broadcast;
a lost broadcast response is treated as outcome unknown, never retried. - Broadcasts on the selected network after a separate confirmation. Mainnet
submission needs one explicit confirmation on the final screen and a backend
opt-in that fails closed when omitted. It never asks for a PIN or seed. - Saves an optional unsigned PSBT and an opt-in privacy-limited diagnostic
report. Dependencies are hash-locked; native libusb digest is required.
Downloads — every platform built from this exact commit in one gated run:
Bitcoin-Easy-Signer-v0.6.7-macOS.dmg— macOS, Apple SiliconBitcoin-Easy-Signer-v0.6.7-windows-x64.zip— Windows x64Bitcoin-Easy-Signer-v0.6.7-linux-x86_64.AppImage— Linux x86_64Bitcoin-Easy-Signer-v0.6.7-linux-x86_64.tar.gz— Linux x86_64, unpackagedbitcoin-easy-multisig-signer-v0.6.7.tar.gz— source
Verify any download against SHA256SUMS and its release-key signature
SHA256SUMS.asc (the public key is signing-key.asc in this repository),
and check each file's GitHub Sigstore build attestation.
BUILD-SBOM.json, BUILD-SBOM-windows-x64.json and
BUILD-SBOM-linux-x86_64.json inventory each packaged environment and its
native libusb.
Use at your own risk. Bitcoin Easy Signer is free, open-source software
maintained by Bitseeker LLC, without warranty or guarantee. Real Bitcoin can be
sent from this build: verify the destination, amount and fee on your signing
devices before approving, and treat an unconfirmed payment as unfinished.
Hardware signers commonly hide the change output, so check the change address
in the wallet software that holds the wallet file, not on a device screen.
Bitcoin Easy Signer 0.6.7
This release fixes the repository's release process after the Color Team
audit of v0.6.6 graded it BLOCKED. The audit cleared the app itself. No
wallet, signing, or broadcast policy changed, and no new payment capability
is added.
What changed
- There is now exactly one way to publish this project. The old
per-platform Windows and Linux publish workflows, which were never
deleted and were still able to publish unsigned files, are gone from
every branch. A guard check refuses to start a release if one reappears. - A hardware helper is identified by the bytes it is made of, not by the
version number it reports about itself. A planted program that simply
printed the expected version is refused. The identity is re-checked at
every signing session. - Release builds run on one exact Python patch level instead of "whatever
version each build machine happened to have", so the macOS, Windows,
Linux, and source builds are built by the same interpreter. - The tool that writes the dependency locks is itself hash-locked, and the
Linux build no longer upgrades its own installer before installing a
locked set of packages. - The source download now contains every file needed to rebuild the signed
Mac app from itself. - The app verifies that its broadcast server is actually on the network it
says it is, on every network, before anything is submitted.
Downloads
Verify every download against SHA256SUMS and its SHA256SUMS.asc. The
release carries one checksum file covering macOS, Windows, and Linux, plus
BUILD-SBOM.json. See SIGNING.md for the signature and provenance
policy.
v0.6.6
Superseded — do not use for new deployments. This release predates v0.6.7, the current release and the subject of the current Color Team audit. It is kept for historical reference and for verifying earlier work; it has not been reviewed under the current audit cycle.
v0.6.6
The macOS download is signed with a Developer ID certificate and notarized by Apple, so it installs with a normal double-click. The Windows and Linux downloads are unsigned: their guarantee is provenance, not a certificate — every asset was built from this exact commit in one gated workflow run, is covered by the CI-generated SHA256SUMS and its release-key signature SHA256SUMS.asc, and carries a GitHub Sigstore build attestation. See SIGNING.md.
Built from main at commit 93cf67af63a15aac0912a6fbc270f7e5485e2fc1.
- Opens an existing BSMS native-SegWit multisig wallet with two or three physical keys; the file defines the quorum, and the app checks its public balance.
- Prepares a partial send with a declared change branch or the guarded
standard BIP48 /1/* branch anchored by the BSMS first receive address.
Unsupported layouts can explicitly Send All without change. Shows final outputs and fee. - Refuses inferred change when a bare wildcard matches the first address
directly instead of anchoring the BIP48 /0/0 receiving branch. - Uses bundled HWI 3.2.0 over stdin to request the number of hardware signatures required by the BSMS quorum.
Only signatures verifying against the reviewed PSBT are retained;
signer-returned metadata is discarded before finalization. - Gives each device discovery and authorization check up to three minutes and deliberate on-device signing
up to ten minutes, including Ledger's multiple review screens. - Offers Bitcoin mainnet plus the Testnet4 and Mutinynet practice networks
through one engine. The practice networks are a test bench for developers,
not what this app is for. A custom-Signet checkpoint distinguishes Mutinynet
from ordinary Signet.
A new Mutinynet wallet and practice coins are required; Testnet4 coins
do not transfer across networks. - Opens on Bitcoin mainnet. The practice networks are reached only through
the "Enter Developer Mode" gate on the opening screen, which asks for
confirmation first and lasts for the session: the app reopens on mainnet.
Inside the gate the choice is Mutinynet or Testnet4: live Bitcoin is the
network the gate returns to, not one of its options.
Send All is never preselected; a nonstandard wallet without an established
change branch explains why a smaller payment is unavailable. - Clears old signer/final details whenever a new payment is prepared,
including the network the retired final screen was bound to.
Rechecks selected confirmed outputs before preparation and broadcast;
a lost broadcast response is treated as outcome unknown, never retried. - Broadcasts on the selected network after a separate confirmation. Mainnet
submission needs one explicit confirmation on the final screen and a backend
opt-in that fails closed when omitted. It never asks for a PIN or seed. - Saves an optional unsigned PSBT and an opt-in privacy-limited diagnostic
report. Dependencies are hash-locked; native libusb digest is required.
Downloads — every platform built from this exact commit in one gated run:
Bitcoin-Easy-Signer-v0.6.6-macOS.dmg— macOS, Apple SiliconBitcoin-Easy-Signer-v0.6.6-windows-x64.zip— Windows x64Bitcoin-Easy-Signer-v0.6.6-linux-x86_64.AppImage— Linux x86_64Bitcoin-Easy-Signer-v0.6.6-linux-x86_64.tar.gz— Linux x86_64, unpackagedbitcoin-easy-multisig-signer-v0.6.6.tar.gz— source
Verify any download against SHA256SUMS and its release-key signature
SHA256SUMS.asc (the public key is signing-key.asc in this repository),
and check each file's GitHub Sigstore build attestation.
BUILD-SBOM.json, BUILD-SBOM-windows-x64.json and
BUILD-SBOM-linux-x86_64.json inventory each packaged environment and its
native libusb.
Use at your own risk. Bitcoin Easy Signer is free, open-source software
maintained by Bitseeker LLC, without warranty or guarantee. Real Bitcoin can be
sent from this build: verify the destination, amount and fee on your signing
devices before approving, and treat an unconfirmed payment as unfinished.
Hardware signers commonly hide the change output, so check the change address
in the wallet software that holds the wallet file, not on a device screen.
Bitcoin Easy Signer 0.6.6
This release hardens the signing and release path after the Color Team
audit of 0.6.5. It adds no new payment capability.
What changed
- A hardware device must now prove it holds the wallet key before it
receives a payment. One extra on-device confirmation may appear while
signing. - The large-amount mainnet prompt also fires at 0.04 BTC, so a lying price
feed cannot hide a large payment. Amounts from 0.04 to 0.1 BTC may ask
for that confirmation when they previously did not. - The app no longer freezes during a slow explorer check before broadcast.
- Saved transactions that already carry signatures are named
-signed
rather than-unsigned. - Source mode refuses a hardware helper that does not identify as the
pinned HWI 3.2.0. - Published BIP-143 test vectors guard the signature digest.
- Release builds pin their runner images and lock tooling.
Downloads
Verify every download against SHA256SUMS and its SHA256SUMS.asc. The
release carries one checksum file covering macOS, Windows, and Linux, plus
BUILD-SBOM.json. See SIGNING.md for the signature and provenance
policy.