A Keystore is responsible for holding the user's XMTP private keys and using them to encrypt/decrypt/sign messages.
Keystores are instantiated using a KeystoreProvider
Create an XMTP auth token to be used as a header on XMTP API requests
Parameters
req: CreateAuthTokenRequest
Returns Promise<Token>
createInvite
createInvite(req): Promise<CreateInviteResponse>
Create a sealed/encrypted invite and store the Topic keys in the Keystore for later use.
The returned invite payload must be sent to the network for the other party to be able to communicate.
Parameters
req: CreateInviteRequest
Returns Promise<CreateInviteResponse>
decryptV1
decryptV1(req): Promise<DecryptResponse>
Decrypt a batch of V1 messages
Parameters
req: DecryptV1Request
Returns Promise<DecryptResponse>
decryptV2
decryptV2(req): Promise<DecryptResponse>
Decrypt a batch of V2 messages
Parameters
req: DecryptV2Request
Returns Promise<DecryptResponse>
encryptV1
encryptV1(req): Promise<EncryptResponse>
Encrypt a batch of V1 messages
Parameters
req: EncryptV1Request
Returns Promise<EncryptResponse>
encryptV2
encryptV2(req): Promise<EncryptResponse>
Encrypt a batch of V2 messages
Parameters
req: EncryptV2Request
Returns Promise<EncryptResponse>
getAccountAddress
getAccountAddress(): Promise<string>
Get the account address of the wallet used to create the Keystore
A Keystore is responsible for holding the user's XMTP private keys and using them to encrypt/decrypt/sign messages. Keystores are instantiated using a
KeystoreProvider
Deprecated
Use
KeystoreInterface
instead