Package-level declarations
Types
A safe identifier for a backup; it carries no signing secret or authorization.
Destination evidence, verified against the original public key before recording custody.
A public reference to an additional private-key custodian; not a recovery record.
An explicitly trusted destination that receives a copy of the private signing key. This is key custody, not portable identity recovery or remote signing.
A trusted integration's structured failure; never includes record bytes or provider credentials.
Actionable provider failures. Unknown integration errors remain retryable without exposing their messages.
Secret bytes crossing the trusted provider boundary. Never log or include them in UI/analytics.
Trusted recovery integration. Implementations must protect secret records in transit and at rest, scope access to the intended user/application, and make repeated writes of the same ID idempotent. A local write must not be reported as verified cloud delivery.
Current status of one configured provider, including providers that cannot offer a backup.
Does not erase an operational software signing key; it controls the additional recovery record only.
Current provider prerequisites. Availability is rechecked when executing an option.
Minimum evidence required before backup-dependent activation or local-record disposal.
Protection of the recovery record, independent of signing-key hardware protection.
Evidence returned by a backup operation; OS submission is not proof of remote durability.
Delivery scope supported by a registered integration.
Public identity details. Never contains a seed, private key or database encryption key.
Attestation is a creation-time request, so challenges are never baked into wallet defaults.
Makes inheritance explicit without a nullable authorization policy.
SDK-issued backup choice using retained recovery material or an exportable signing key.
Identity configuration. Native recovery integrations are opt-in dependencies and registrations.
Complete SDK-issued creation option. It cannot be constructed, copied or deserialized by callers.
Complete creation choices, or explicit reasons why the current requirements cannot be met.
SDK-issued choice whose export policy and local key are rechecked before transfer.
Key-custody outcome. The local signing key is retained and recovery status is unaffected.
Stable failure categories; callers do not need native error-message parsing.
Requested lifecycle. Only compatible complete options can be passed to creation.
Constraints retained with the identity and applied to creation, backup and restoration.
Execution backend selected by a validated option. NativeStorage does not promise hardware.
Owns one wallet's active signing identity. Creation and recovery use complete SDK-issued options. Native/backup prerequisites are revalidated at execution. The encrypted database journals interrupted operations; a failed backup submission does not activate the new identity. Successful activation and initialization refresh the wallet's platform credential registration.
Creation and restore share one lifecycle result. Pending operations are resumable.
A record discovered through a configured provider; executable recovery options require validation.
One recovery discovery attempt, including routes that failed without hiding healthy candidates.
Redacted provider failure; no private record or native diagnostic is exposed.
Backup status says what is known, separately from native signing-key protection.
SDK-issued restoration option tied to a validated record and current destination policy.
Identity availability is distinct from whether credential data exists in the wallet.