七麦数据

Bug fixes and minor improvements.

Improvements in 1.6

UI Best Practices

• BIP39/ByteWords Entry: Shows validity of individual words
• Hex Entry: More accessible entry cuts out spaces, other non-hex entries
• Seed Printing: Elides some info if necessary to print out a backup of a seed
• Fingerprint Info: Seed views now display master fingerprint & Lifehash

Resilience Best Practices

• Output Descriptor: Output Descriptor can be saved as seed metadata

Other Chain Expansions

• Tezos Support: Generates tz1 addresses & private keys
• Ethereum & Tezos Improvements: Better shows necessary data for chains

Specification Updates

• Envelope is now prime output type for seeds, SSKR, requests, responses
• Envelope attachments are supported
• Update to Envelope v2, based on IETF feedback
• Update to Account Descriptor v2, Output Descriptor v3, based on community feedback
• Update to IANA registered CBOR numbers (with backward compatibility as needed)

General bug fixes and improvements.

NFC Improvements

• Write crypto-seeds to NFC Tags.
• Write crypto-hdkeys to NFC Tags.
• Write crypto-requests to NFC Tags (developers only).
• Read crypto-requests from NFC Tags.
• Write crypto-responses to NFC Tags.

SSKR Improvements

• Write individual SSKR shares to NFC Tags.
• Print individual SSKR shares.
• Save individual SSKR shares as PDFs (using printing).

General bug fixes and improvements.

I/O Improvements in Seed Tool 1.4:

• NFC Import: Allows import from NFC Tags.
• UR Import: Imports and processes "ur:" scheme strings.
• Clipboard Erasure: Erases clipboard in 1 minute when used for export (iOS only).
• File Saving: Exports to files, including MicroSDs and iCloud.
• SSKR Split: Allows individual export of SSKR shares, such as to different MicroSD cards.

New Data Details in Seed Tool 1.4:

• Descriptor Checksums: All output descriptors now include their checksum.
• Seed Fingerprints: All seed OIBs now display the fingerprint for their master HD key.
• Request Details: All crypto-requests now show notes and known key derivations.

Other Updates & Fixes in Seed Tool 1.4:

• Seed Request Fix: Parses crypto-requests for seeds using the latest spec.
• Other: Various UX improvements, interface standardizations, and small bug fixes.

Bug fixes related to printing.

Changes in this release:

• Key Export: Fixed a bug where changing the network wouldn't always update the derived ur:crypto-account to reflect the change.
• QR code display: Reduced the threshold for a QR code to be animated from 800 to 600 bytes per segment.

Changes in version 1.3:

This release features signing Partially-Signed Bitcoin Transactions (PSBTs) and export of output descriptors for interacting with other wallets!

• OS Support: This release supports iOS 15 or later and introduces support for macOS 12 (Monterey) or later.
• Scan view: A camera selector button has been added for front/back cameras (iOS) and built-in/desktop webcam (macOS).
• PSBT Signing: When a `ur:crypto-request` for PSBT signing is scanned, Seed Tool will attempt to find seeds that it is managing from which it can derive keys to sign the transaction's inputs. A confirmation screen is then displayed showing the details of the transaction. If the user approves, a ur:crypto-response is displayed. A "bare" PSBT may
• Bare PSBT Signing: For compatibility with third-party wallets that have already implemented this, a bare `ur:crypto-psbt` may now be scanned and signed. Using `ur:crypto-request` is Blockchain Commons' recommended method for requesting PSBT signing, so when a bare `ur:crypto-psbt` is scanned, users are notified of this, thus this capability should be used only by wallet developers, and they are encourage to adopt `ur:crypto-request` as soon as possible.
• PSBT import formats: Importing a PSBT for signing may be done from the camera for `ur:crypto-request` and `ur:crypto-psbt`, or the clipboard for Base64-encoded PSBTs, or from a file for binary or Base64-encoded `.psbt` files.
• PSBT export formats: Exporting a signed PSBT may be done in several formats: `ur:crypto-response`, `ur:crypto-psbt`, Base64-encoded PSBT, or binary `.psbt` file. All of these formats may use the share sheet, allowing (for example) Copy to Clipboard, *except* for binary `.psbt` files, which must be saved to the file system. The two UR formats can be displayed as (possibly animating) QR codes.
• Key Export via Output Descriptors: Master keys derived from seeds can now be exported to Output Descriptors (`ur:crypto-output` or text) or Account Descriptors (`ur:crypto-account`). To see this new feature:

1. choose a seed from the Seed List
2. In the Encrypted Data section, tap "Authenticate"
3. Tap "Derive Key" and then "Other Key Derivations"
4. In the "Parameters" area, make sure "Bitcoin" and "Master Key" are selected
5. Scroll down to the "Secondary Derivation" section and choose "Output Descriptor" or "Account Descriptor".
6. Edit the "Account Number" field if desired.
7. If you chose "Output Descriptor", then choose an "Output Type".
8. Scroll down to the bottom to export your Output Descriptor or Account Descriptor.

• QR Code Display: To increase compatibility with certain QR code readers, QR codes are now displayed as black modules (pixels) on a white background, even in dark mode.
• Other bug fixes and minor enhancements.

This release features signing Partially-Signed Bitcoin Transactions (PSBTs) and export of output descriptors for interacting with other wallets!

• OS Support: This release supports iOS 15 or later and introduces support for macOS 12 (Monterey) or later.
• Scan view: A camera selector button has been added for front/back cameras (iOS) and built-in/desktop webcam (macOS).
• PSBT Signing: When a `ur:crypto-request` for PSBT signing is scanned, Seed Tool will attempt to find seeds that it is managing from which it can derive keys to sign the transaction's inputs. A confirmation screen is then displayed showing the details of the transaction. If the user approves, a ur:crypto-response is displayed. A "bare" PSBT may
• Bare PSBT Signing: For compatibility with third-party wallets that have already implemented this, a bare `ur:crypto-psbt` may now be scanned and signed. Using `ur:crypto-request` is Blockchain Commons' recommended method for requesting PSBT signing, so when a bare `ur:crypto-psbt` is scanned, users are notified of this, thus this capability should be used only by wallet developers, and they are encourage to adopt `ur:crypto-request` as soon as possible.
• PSBT import formats: Importing a PSBT for signing may be done from the camera for `ur:crypto-request` and `ur:crypto-psbt`, or the clipboard for Base64-encoded PSBTs, or from a file for binary or Base64-encoded `.psbt` files.
• PSBT export formats: Exporting a signed PSBT may be done in several formats: `ur:crypto-response`, `ur:crypto-psbt`, Base64-encoded PSBT, or binary `.psbt` file. All of these formats may use the share sheet, allowing (for example) Copy to Clipboard, *except* for binary `.psbt` files, which must be saved to the file system. The two UR formats can be displayed as (possibly animating) QR codes.
• Key Export via Output Descriptors: Master keys derived from seeds can now be exported to Output Descriptors (`ur:crypto-output` or text) or Account Descriptors (`ur:crypto-account`). To see this new feature:

1. choose a seed from the Seed List
2. In the Encrypted Data section, tap "Authenticate"
3. Tap "Derive Key" and then "Other Key Derivations"
4. In the "Parameters" area, make sure "Bitcoin" and "Master Key" are selected
5. Scroll down to the "Secondary Derivation" section and choose "Output Descriptor" or "Account Descriptor".
6. Edit the "Account Number" field if desired.
7. If you chose "Output Descriptor", then choose an "Output Type".
8. Scroll down to the bottom to export your Output Descriptor or Account Descriptor.

• QR Code Display: To increase compatibility with certain QR code readers, QR codes are now displayed as black modules (pixels) on a white background, even in dark mode.
• Other bug fixes and minor enhancements.

This release features better support for Ethereum!

• The Settings View now has a "Primary Asset" switch that can be changed between Bitcoin and Ethereum.

• When Ethereum is selected, the following changes apply:

1. In the Seed Detail view, the green "Cosigner Public Key" changes to "Ethereum Address" for quick export of the Ethereum Address derived from the seed.
2. After clicking "Authenticate," the "Derive Key" popup has an item that changes from "Cosigner Private Key" to "Ethereum Private Key."
3. In the "Other Key Derivations" view, the default derivation path for Ethereum is now `44'/60'/0'/0/0` which is compatible with most Ethereum wallets.
4. The bottom of the "Other Key Derivations" view now contains an "Address" box for exporting the Bitcoin or Ethereum address.
5. In the "Other Key Derivations" view, when deriving Ethereum, a new "Private Key" box appears that can be used to export the Ethereum private key. When printed, this page also includes the Ethereum address.
6. All visual hashes (identicons) associated with Ethereum keys or addresses now use "Blockies", which is widely recognized in the Ethereum world, instead of the usual LifeHash algorithm.

• You can now navigate from various places of the app to specific pages of the built-in user's guide via the ⓘ buttons.
• The Settings panel now contains a Show Developer Functions switch that shows the "Show Request/Response for this Seed/Key" options at appropriate places in the app.
• All functions that copied data to the clipboard, including long presses on QR codes, life hashes, and other static fields now invoke the system share sheet instead.
• In the Seed Detail view, the "Data" section has been renamed "Encrypted Data", and the "Decrypt" button is now called "Authenticate". It now reveals several buttons: Backup, Share, and Derive Key, which are menus that lead to futher functionality. There are also links to the documentation.
• The SSKR export view now includes a "preset selector" that lets users choose among comon sharding configurations. Users can still choose any configuration they like and this will be reflected in the preset selector as "custom".
• In the Settings panel, the default network is now "mainnet". This will only apply to users who have not manually changed this setting.
• In the Derive Key view, both the private and public keys are now simulatenously derived, and appear in separate sections at the bottom of the view.
• Other minor bug fixes and improvements.

• More detailed diagnostic messages when pasting SSKR shares fails to reconstruct the seed.
• The Scan view can now pick image(s) from document picker or photos picker and detect QR codes in them, just as if you'd scanned then with the camera.
• Printed pages for Seeds, HDKeys and SSKR shares now include the textual UR along with the QR code containing the UR.