feat: add SSO encryption pubkey support (Mobile SSO spec v0.2.2)#202
Merged
Conversation
johnthecat
added a commit
that referenced
this pull request
Jun 12, 2026
Main (0.8.7) had independently absorbed nearly all of this branch's work via PRs #178/#202/#205/#206/#212/#215/#216, with newer/cleaner versions. Conflict resolution (38 files): - package.json (x14), package-lock.json, CHANGELOG.md, migration doc: took main (newer versions, canonical release history). Dropped the unused `verifiablejs` dep. - All SSO V2, statement-store, handoff-service, and host-chat *impl* files: took main — strictly newer (ECDH session-key derivation #206, RFC-7 entropy #205, statement-store fix #215). The branch's parallel May implementations are superseded. - watchIdentity series: already identical in main (no real conflict). - Kept BRANCH version for two files where it is genuinely ahead: * identity/rpcAdapter.ts — defensive snake_case/camelCase Resources decode (fixes "Unknown user" regression on V2 runtime); a clean superset of main's version. * host-chat/codec/attachment.spec.ts — extra blurhash-thumbnail and NodeEndpoint round-trip tests against a byte-identical codec impl. Verified: build, typecheck, lint (0 errors), 679/679 tests pass.
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.
Multi-device SSO support, chat attachment improvements, and a file-transfer fix
This branch brings the SDKs in line with the latest Polkadot Mobile protocol and fixes a file-download bug.
Multi-device SSO handshake
The pairing handshake now carries an extra key (
ssoEncPubKey) from the mobile app. The host stores it and hands it to youronAuthSuccesscallback, so it can set up an encrypted SSO session with the app. Older app versions that don't send it keep working — the field is justnull.Explicit session key
createSessionnow takes asessionKey— the value used to derive a session's address. Existing behavior is unchanged: pass the peer's key as before. New multi-device callers can pass the shared secret instead.Chat attachments and messages
File transfer fix
File downloads were signing the wrong payload, which the server rejected and reported as "Data not found". Downloads now sign the correct payload and succeed.