What this library will say about this account's signing identity right
now. Reads only: it asks the server nothing and creates nothing.
See IdentityStatus for why two of the five fields have to be read
together, and why a third exists. Four calls change them:
createCrossSigningIdentity creates the account's first identity,
bootstrapCrossSigning publishes the one this device already holds,
requestSelfVerification joins one the account already has, and
recoverIdentity restores the private half from server-side
storage. This said bootstrapCrossSigning created it, which was true
while creating and publishing were one call.
This is the durable answer the signal channel sends you to. Nothing
returns to a caller when a join's seeds arrive; what happens instead is a
'trust_changed' for your own user id on onCryptoSignal, and reading
privateKeysHeld here is what that signal means. It is the same variant a
completed comparison produces, so read this rather than counting signals.
What this library will say about this account's signing identity right now. Reads only: it asks the server nothing and creates nothing.
See IdentityStatus for why two of the five fields have to be read together, and why a third exists. Four calls change them: createCrossSigningIdentity creates the account's first identity, bootstrapCrossSigning publishes the one this device already holds, requestSelfVerification joins one the account already has, and recoverIdentity restores the private half from server-side storage. This said
bootstrapCrossSigningcreated it, which was true while creating and publishing were one call.This is the durable answer the signal channel sends you to. Nothing returns to a caller when a join's seeds arrive; what happens instead is a
'trust_changed'for your own user id ononCryptoSignal, and readingprivateKeysHeldhere is what that signal means. It is the same variant a completed comparison produces, so read this rather than counting signals.