This commit is contained in:
Peter D. Gray 2025-04-10 09:48:44 -04:00
parent 9ba8aeaaad
commit efd5a4ff45
No known key found for this signature in database
GPG Key ID: A2DCD558C2BE5D7C

View File

@ -13,44 +13,49 @@ This lists the new changes that have not yet been published in a normal release.
- 2FA authentication using phone app ([RFC 6238](https://www.rfc-editor.org/rfc/rfc6238))
- but will sign its part of a transaction automatically if those condition are met,
giving you 2 keys of the multisig and control over the funds
- spending policy can be exceed with help of the other co-signer (3rd key), when needed
- spending policy can be exceeded with help of the other co-signer (3rd key), when needed
- cannot view or change the CCC spending policy once set, policy violations are not explained
- existing multisig wallets can be used by importing the spending-policy-controlled key
- New Feature: Multisig transaction finalization. Allows to use [PushTX](https://pushtx.org/) with multisig wallets.
Read more [here](https://github.com/Coldcard/firmware/blob/master/docs/limitations.md#p2sh--multisig)
- New Feature: Signing artifacts re-export. Press (0) at the end of signing to re-export with different medium
- New Feature: Signed multisig exports. Read more [here](https://github.com/Coldcard/firmware/blob/master/docs/msg-signing.md#signed-exports)
- Enhancement: NFC export usability upgrade. NFC keeps exporting until CANCEL/X is pressed
- New Feature: Multisig transactions are finalized. Allows use of [PushTX](https://pushtx.org/)
with multisig wallets. Read more [here](https://github.com/Coldcard/firmware/blob/master/docs/limitations.md#p2sh--multisig)
- New Feature: Signing artifacts re-export to various media. Now you have the option of
exporting the signing products (transaction/PSBT) to different media than the original source.
Incoming PSBT over QR can be signed and saved to SD card if desired.
- New Feature: Multisig export files are signed now. Read more [here](https://github.com/Coldcard/firmware/blob/master/docs/msg-signing.md#signed-exports)
- Enhancement: NFC export usability upgrade: NFC keeps exporting until CANCEL/X is pressed
- Enhancement: Add `Bitcoin Safe` option to `Export Wallet`
- Enhancement: 10% performance improvement in USB upload speed for large files
- Bugfix: Fix stuck progress bar under `Receiving...` after a USB communications failure
- Bugfix: Showing derivation path in Address Explorer for root key (m) showed double slash (//)
- Bugfix: Enable to restore dev backup with custom password other than 12 words format
- Bugfix: Can restore developer backup with custom password other than 12 words format
- Bugfix: Virtual Disk auto mode ignore already signed PSBTs (with "-signed" in file name)
- Bugfix: Virtual Disk auto mode stuck on "Reading..." screen
- Bugfix: Do not allow to change Main PIN to value already used as Trick PIN even if Trick PIN is hidden
- Change: `Destroy Seed` also removes all Trick PINs from SE2
- Bugfix: Do not allow to change Main PIN to value already used as Trick PIN even if
Trick PIN is hidden.
- Change: `Destroy Seed` also removes all Trick PINs from SE2.
# Mk4 Specific Changes
## 5.4.2 - 2025-03-??
## 5.4.2 - 2025-04-??
- tbd
# Q Specific Changes
## 1.3.2Q - 2025-03-??
## 1.3.2Q - 2025-04-??
- Feature: Key Teleport -- Easily and securely move seed phrases, secure notes/passwords and PSBT
between two Q using QR codes and/or NFC with helper website. See protocol spec in
- Feature: Key Teleport -- Easily and securely move seed phrases, secure notes/passwords,
multisig PSBT files, and even full Coldcard backups, between two Q using QR codes
and/or NFC with helper website. See protocol spec in
[docs/key-teleport.md][https://github.com/Coldcard/firmware/blob/master/docs/key-teleport.md]
- can send master seed (words, xprv), anything held in seed vault, secure notes/passwords
(singular, or all) and PSBT involved in a multisig
(singular, or all) and PSBT involved in a multisig to the other co-signers
- full COLDCARD backup is possible as well, but receiver must be "unseeded" Q for best result
- ECDH to create session key for AES-256-CTR, with another layer of AES-256-CTR using a
short password (stretched by PBKDF2-SHA512) inside
- receiver shows sender a QR and a numeric code; sender replies with a QR and 8-char
password
- receiver shows sender a (simple) QR and a numeric code; sender replies with larger BBQr
and 8-char password
- Enhancement: Always choose the biggest possible display size for QR