@ducat-unit/wallet-snap 0.1.5 → 0.1.9

package/README.md

@@ -6,13 +6,13 @@ The Ducat web app remains the user action surface. Users create, deposit, borrow
 
 ## Release Candidate Status
 
-- Package candidate: `@ducat-unit/wallet-snap@0.1.5`
+- Package candidate: `@ducat-unit/wallet-snap@0.1.9`
 - Snap ID: `npm:@ducat-unit/wallet-snap`
 - Proposed Snap name: `Ducat`
-- Audit candidate tag: `audit-candidate-0.1.5-20260615-audit-confirmation-hardening`
-- Audit candidate commit: tag target for `audit-candidate-0.1.5-20260615-audit-confirmation-hardening`
+- Audit candidate tag: `audit-candidate-0.1.9-20260617-release-0.1.9`
+- Audit candidate commit: tag target for `audit-candidate-0.1.9-20260617-release-0.1.9`
 - GitHub verification: `Verify Ducat Snap`
-- Manifest source shasum: `RE0s+LP6Soq0Xn0R8P+DA2ChhPOB2pasPp9BsJng5/Y=`
+- Manifest source shasum: `u1SC4s8yatFtFEE1IbLPvx2irYCtR/WOm0PtAx81qUs=`
 - Package candidate digest evidence: `RELEASE_EVIDENCE.md`
 
 Launch scope:
@@ -77,7 +77,7 @@ For the published Snap:
 
 ```bash
 NEXT_PUBLIC_DUCAT_SNAP_ID="npm:@ducat-unit/wallet-snap"
-NEXT_PUBLIC_DUCAT_SNAP_VERSION="^0.1.5"
+NEXT_PUBLIC_DUCAT_SNAP_VERSION="^0.1.9"
 ```
 
 Allowed HTTPS Ducat origins in the published mainnet manifest:

package/RELEASE_CHECKLIST.md

@@ -1,9 +1,9 @@
 # Ducat Snap Release Checklist
 
-## Completed For `0.1.5`
+## Completed For `0.1.9`
 
 - [x] Public repository contains the audit-candidate source tag.
-- [x] Audit candidate tag exists after the final handoff commit: `audit-candidate-0.1.5-20260615-audit-confirmation-hardening`.
+- [x] Audit candidate tag exists after the final handoff commit: `audit-candidate-0.1.9-20260617-release-0.1.9`.
 - [ ] `.github/workflows/verify.yml` succeeds on the current audit candidate.
 - [x] `npm run verify:release` succeeds locally.
 - [x] `npm run pack:dry-run` output reviewed.
@@ -14,8 +14,8 @@
 - [x] Legacy Taproot script-path compatibility behavior removed and replaced with committed tapleaf verification.
 - [x] Deterministic MetaMask simulation harness covers account derivation and owned P2WPKH PSBT signing.
 - [x] Mainnet derivation, network parsing, endpoint selection, and release metadata added to the audit candidate.
-- [x] `@ducat-unit/wallet-snap@0.1.5` release metadata prepared for audit handoff.
-- [ ] Frontend PR #675 default Snap version range updated to `^0.1.5`.
+- [x] `@ducat-unit/wallet-snap@0.1.9` release metadata prepared for audit handoff.
+- [ ] Frontend default Snap version range updated to `^0.1.9`.
 
 ## Required Before MetaMask Submission
 

package/SNAPPER_REVIEW.md

@@ -6,9 +6,9 @@ Last local command:
 npx --yes @sayfer_io/snapper --path . --output snapper-report.json
 ```
 
-Local result: 221 findings across the `ESLinting`, `ExcessiveComments`, and `HardcodedSecrets` categories.
+Local result: 235 findings across the `ESLinting`, `ExcessiveComments`, and `HardcodedSecrets` categories.
 
-The three `HardcodedSecrets` findings are the Ducat guardian x-only **public** key (`ef8e6d84…ca2e`) hardcoded per network in `src/networks.ts`. It is a public key that is intended to be embedded so the Snap can pin the vault cosigner identity; it is not a secret. The remaining findings are style/comment-density scanner policy, not signing, key-export, origin-authorization, confirmation-bypass, or network-scope findings.
+The four `HardcodedSecrets` findings are Ducat guardian x-only **public** keys hardcoded per network in `src/networks.ts`: the shared guardian key (`ef8e6d84…ca2e`, flagged once per network) and the mutinynet BitVM FROST group key (`23586495…2321`). They are public keys intended to be embedded so the Snap can pin the vault cosigner identity; they are not secrets. The remaining findings are style/comment-density scanner policy, not signing, key-export, origin-authorization, confirmation-bypass, or network-scope findings.
 
 ## Addressed Findings