Skip to content

Smartable Wallet Core v2.0.0

Latest

Choose a tag to compare

@github-actions github-actions released this 17 Nov 10:18
· 1 commit to main since this release

Exported from Smartable Wallet 3.0.0 (build 23).

The recovery phrase's seed and every key derived from it now live in the key
core, a Rust library published here for the first time: once a wallet is
open, the Dart code holds a session with the core, not the phrase. This is
the same move from one implementation to another that a wallet core makes
when it rewrites its key handling in a lower-level language, and it is why
this is a major version. 1.0.0 and 1.0.1 are superseded by 2.0.0. Every
record they wrote — a sealed phrase, a PIN, a device-key record, a split
backup's shares — is read and opened by this version; new work should build
on 2.0.0, and 1.0.x receives no further changes.

Added

  • The key core, native/key_core/: the Rust crate that holds the recovery
    phrase's seed and every key derived from it, opens the sealed phrase, and
    signs a transaction or a message only after reading it itself; its C
    interface (include/key_core.h), its Dart binding over dart:ffi
    (dart/), whose build hook compiles the crate offline at the pinned
    toolchain, and its tests against published vectors (THIRD_PARTY_NOTICES.md
    names each source).
  • The split backup in the key core: SLIP-39 split, checked and recombined
    there, each share sealed with Argon2id (argon2 0.5.3) and AES-256-GCM in
    the same format the Dart code writes; a restore opens a wallet in the core
    from the shares, so the phrase is never text on the way.
  • A phrase made or typed into the app is sealed in the core
    (kc_seal_phrase), and an imported private key is opened there from its
    record.
  • Zcash's transparent keys, addresses and ZIP-244 signatures, held to six
    mainnet version 5 transactions and ZIP-320's reference addresses.
  • CI runs the key core's cargo test, debug and release.

Changed

  • BREAKING: VaultKeeper.loadSeed, unlockWithPin and
    unlockWithDeviceKey open the wallet and return nothing; they used to
    return the recovery phrase. A caller that shows the words — for a backup —
    asks revealPhrase(password), which reads them from the stored record
    behind the password.
  • BREAKING: VaultHost.opened and VaultHost.switched receive the vault
    key, from which the host opens its key-core session, instead of the phrase.
  • The lib/core/, test/ and native/ files are those of the app's
    current source. Among them: the password's PBKDF2 runs off the main
    isolate and writes over the typed secret's bytes when done
    (crypto_utils.dart); the vault keeper stores a phrase the key core
    sealed, for a first wallet and one added beside others, under a vault key
    it draws (vault_keeper.dart); the share-sealing parameters
    are read in one place, which the key core is handed
    (sealed_share.dart).
  • The GitHub address in the README and the workflows is
    github.com/getsmartableapp/core; the repository's home stays
    gitlab.com/getsmartable-app/core.

Security

  • After an unlock the phrase is no longer kept in the app's memory as text:
    the seed is derived and every key used inside the key core, which signs a
    transaction or a message only after reading it itself. What remains of a
    typed secret is the text the platform's keyboard and text field held.
  • The password's PBKDF2 runs off the main isolate and overwrites the bytes of
    the typed secret when it is done.

Checking this release — see docs/releasing.md:

sha256sum -c SHA256SUMS
gh attestation verify smartable-wallet-core-v2.0.0.tar.gz --repo getsmartableapp/core