Endpoint InviteToken exchange.

[MartinSchmidt]

Currently we create a WalletEndpoint on the request from the user, which the user then forwards to the sender, where they insert it, this must only be sent to a single individual.

An alternative approach could be a that an owner of a wallet could create a InviteToken which would be single use.
This token could then be forwarded to the sender, and their wallet can then exchange it for a publicKey and other information necessary, this would ensure that they are not shared with multiple other systems, and the creation of a WalletEndpoint would become lazy until the InviteToken is exchanged.

This also ensures that the receiver endpoint exists.

old flow

sequenceDiagram
    activate ReceiverUser
    ReceiverUser->>+ReceiverWallet: CreateWalletEndpoint
    ReceiverWallet-->>-ReceiverUser: EndpointInfo
    ReceiverUser->>+SenderUser: Send EndpointInfo
    deactivate ReceiverUser
    SenderUser->>+SenderWallet: CreateOutboxEndpoint(EndpointInfo)
    SenderWallet-->>-SenderUser: OutboxEndpointId
    deactivate SenderUser

Loading

proposed flow

sequenceDiagram
    activate ReceiverUser
    ReceiverUser->>+ReceiverWallet: CreateWalletInvite
    ReceiverWallet-->>-ReceiverUser: InviteToken
    ReceiverUser->>+SenderUser: Send InviteToken
    deactivate ReceiverUser
    SenderUser->>+SenderWallet: AddOutboxEndpoint(InviteToken)
    SenderWallet->>+ReceiverWallet: ExchangeToken(InviteToke)
    ReceiverWallet-->>-SenderWallet: EndpointInfo
    SenderWallet-->>-SenderUser: OutboxEndpointId
    deactivate SenderUser

Loading