Package lol.trq.alts.vault
package lol.trq.alts.vault
-
ClassDescriptionOne host of a repository as the latest verified manifest state lists it (AVP SPEC 4.2): its key, the host's identity, and its locator, where it is reached.The token a joiner gives the owner (AVP SPEC 11.3): the joiner's two public keys, its home host (key and locator), and the home host's signed acceptance to carry the repository for that member.The read-only importer for a repository of the 0.4 shared vault, which 1.0 no longer speaks: given the repository's manifest and envelope, as the 0.4 host wrote them (the JSON is parsed strictly), and the member's own
VaultIdentity(restored from itsWrappedIdentitywith the passphrase or the recovery code), it returns the accounts.The answer of an existing owner device to aLinkRequest(AVP SPEC 11.6): the owner's mnemonic entropy, wrapped to the request's ephemeral key underavp/owner-link/v1.The request a new owner device shows (AVP SPEC 11.6): its ephemeral public key.Owner device linking (AVP SPEC 11.6): how a second owner device gets theOwnerIdentitywithout the phrase being typed.The owner of a repository (AVP SPEC 3.1): the keys derived from a 24-word BIP39 phrase.Offline recovery codes for aVaultIdentity.The token the owner gives a joiner (AVP SPEC 11.2): the repository id, the owner's home host (its key and its locator) and the fingerprint of the owner key.One member device's copy of one AVP 0.5 shared alt repository.What one sync with the home host found and did (AVP SPEC 5, 6.4, 6.5, 7.5, 8.4), and what the owner may have to act on: pending leave requests, a diverged owner chain, and a policy that started sharing refresh tokens.A connection to one AVP host, matched by its host key (AVP SPEC 3.3, 11.7), on the runtime's transport.The runtime's way to AVP hosts:alts.vault().A member's cryptographic identity: an Ed25519 key pair (the member key, which signs the member's AVP 0.5 commits and leave requests and authenticates it to hosts) plus an X25519 key pair (used only to unwrap repository data keys wrapped to this member).One member of a repository as the latest verified manifest state lists it (AVP SPEC 4.2): a view of the roster, not an identity.What one member device keeps of a repository between runs, for the host to persist and pass back toSharedVault.resume(VaultHost, OwnerIdentity, VaultSnapshot): the verified chain as its state hashes, whose last is the pin a rollback must not go below (AVP SPEC 6.4); every data key this device has held, by epoch, so old-epoch heads stay readable; the clock (SPEC 5); the merged payload; whether this member left; the member it belongs to; and its home host, key and locator, soVaultHosts.connect(VaultSnapshot)reaches it by key.The server-storable, passphrase-protected form of aVaultIdentity.