ol.trixnity.verification

This namespace maps to Trixnity’s VerificationService.

The public wrappers here cover:

Use ol.trixnity.key for trust and key-management APIs that often accompany verification workflows.

Returns the current active device verification, or nil when none is active.

Returns a relieved Missionary flow of the current active device verification.

Returns the current active user verifications as a vector.

Returns active device and user verification snapshots as a vector.

Device verification, when present, appears first, followed by active user verifications in Trixnity order. Each snapshot contains a stable ::mx/verification-id suitable for ready!, start-sas!, accept-sas!, confirm!, no-match!, and cancel!.

Returns active verification snapshots.

Alias for active-verification-snapshots.

Returns a relieved Missionary flow of the current active user verifications.

Creates a device verification request and returns a Missionary task.

user-id is the target Matrix user id. device-id is the target Matrix device id. The task resolves to a normalized active-verification snapshot.

Maps to Trixnity VerificationService.createDeviceVerificationRequest.

Creates a user verification request and returns a Missionary task.

The task resolves to a normalized active-verification snapshot. Maps to Trixnity VerificationService.createUserVerificationRequest.

Gets or creates an active user verification for a room request event.

room-id and event-id identify a Matrix verification request event. The task resolves to a normalized active-verification snapshot or nil. Maps to Trixnity VerificationService.getActiveUserVerification.

Sends m.key.verification.ready for an incoming verification request.

verification-id must come from an active-verification snapshot. The task resolves to the updated snapshot. Maps to Trixnity ActiveVerificationState.TheirRequest.ready.

Starts SAS verification for a ready verification request.

verification-id must come from an active-verification snapshot. The task resolves to the updated snapshot. Maps to Trixnity ActiveVerificationState.Ready.start(VerificationMethod.Sas).

Accepts an incoming SAS start event.

verification-id must come from an active-verification snapshot. The task resolves to the updated snapshot. Maps to Trixnity ActiveSasVerificationState.TheirSasStart.accept.

Accepts the current incoming verification step.

verification-id must come from an active-verification snapshot. This maps to Trixnity’s available incoming action for the current state: request ready or SAS accept. Prefer ready! or accept-sas! when the caller already knows the state.

Confirms that the SAS comparison matches.

verification-id must come from an active-verification snapshot. The task resolves to the updated snapshot. Maps to Trixnity ActiveSasVerificationState.ComparisonByUser.match.

Rejects the SAS comparison as a mismatch.

verification-id must come from an active-verification snapshot. The task resolves to the updated snapshot. Maps to Trixnity ActiveSasVerificationState.ComparisonByUser.noMatch.

Cancels an active verification and returns a Missionary task.

verification-id must come from an active-verification snapshot. With reason, passes that Matrix cancellation reason through to Trixnity.

Returns a Missionary flow of available self-verification methods.

Upstream models this as a state machine that distinguishes unmet preconditions, no-cross-signing-yet, already-cross-signed, and available self-verification methods.