Optional transactionId: stringOptional deviceId: stringPrivate Readonly clientOptional devicePrivate Readonly devicesOptional requestOptional transactionReadonly userAdd all the fields to content needed for sending it over this channel. This is public so verification methods (SAS uses this) can get the exact content that will be sent independent of the used channel, as they need to calculate the hash of it.
the event type
the (incomplete) content
the complete content, as it will be sent.
See completedContentFromEvent for why this is needed.
the received event
the content object
the event to get the timestamp of
the timestamp when the event was sent
Changes the state of the channel, request, and verifier in response to a key verification event.
to handle
the request to forward handling to
whether this is an even received through sync or not
a promise that resolves when any requests as an answer to the passed-in event are sent.
Private sendStatic canStatic getStatic getExtract the transaction id used by a given key verification event, if any
the event
the transaction id
Static makeStatic validateChecks whether this event is a well-formed key verification event.
This only does checks that don't rely on the current state of a potentially already channel
so we can prevent channels being created by invalid events.
handleEvent can do more checks and choose to ignore invalid events.
the event to validate
the client to get the current user and device id from
whether the event is valid and should be passed to handleEvent
Generated using TypeDoc
A key verification channel that sends verification events over to_device messages. Generates its own transaction ids.