Repository navigation
0.5.0
Device-held keys, hardware-verified at every tier.
New: canton-wallet-android
AndroidKeystoreSigningDriver — P-256 keys generated inside the Android Keystore, non-exportable, alias-addressed for reuse across launches. Attempts StrongBox first and falls back to the TEE-backed keystore, reporting the achieved security level honestly via KeyInfo (STRONGBOX / TRUSTED_ENVIRONMENT / SOFTWARE); pass requireStrongBox = true to fail instead of falling back. Maven Central: io.github.vsima.canton:canton-wallet-android:0.5.0 (minSdk 23).
Hardware verification, all on physical devices:
- StrongBox dedicated secure element — Samsung Galaxy Z Flip5 (4/4 instrumentation tests, no-silent-fallback contract asserted)
- TEE keystore fallback — OnePlus Open (the path most Android devices take)
- Secure Enclave — iPhone XR (0.4.0), continuously exercised in CI on Apple Silicon
Also since 0.4.0
- Transfer preapprovals: receiver-signed proposal → validator accepts → one-step ("direct") transfers with no inbox round-trip; scan lookup included. Live-verified against a real Amulet registry.
- Custody hook (
DelegatingSigningDriver) andWalletStore(in-memory both platforms, Keychain on Apple). - Migration map from
@canton-network/wallet-sdk(docs/migrating-from-wallet-sdk.md).
Lockstep: Swift via this tag (SPM), Kotlin on Maven Central (canton-wallet-sdk, canton-wallet-android, canton-sdk, canton-ledger-api, all 0.5.0). Targets Canton 3.5.11–3.5.12. Pre-1.0: expect breaking changes.
🤖 Generated with Claude Code