Standardize the pairing token format - #125
Open
maximmaxim345 wants to merge 5 commits into
Open
Conversation
arturpragacz
requested changes
Jul 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Defines the pairing token: the single
SP:-prefixed, versioned, base32 string that distributes a client's static key and its Sendspin Pairing PSK together for the Pairing PSK flow. This standardizes the format that aiosendspin'spairing_token.pyalready produces and consumes, so tokens interoperate across implementations.Also, I defined the scheme for the QR code, which we previously mentioned but never elaborated: it's the token string carried verbatim, with no URI wrapper, so a scan and a copy/paste yield identical input.
The wire format matches aiosendspin exactly. What the spec adds on top:
SP:prefix). While aiosendspin already behaves this way, this requires it.MUSTthat the server confirm the decodedclient_keymatches the connection'sclient_idbefore pairing, which the library doesn't state.