Add optional message authentication, encryption, key registry, and device transfer support#9
Draft
Copilot wants to merge 3 commits into
Draft
Add optional message authentication, encryption, key registry, and device transfer support#9Copilot wants to merge 3 commits into
Copilot wants to merge 3 commits into
Conversation
Copilot
AI
changed the title
[WIP] Add cryptographic authentication functionality with messaging support
Add optional message authentication, encryption, key registry, and device transfer support
May 30, 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.
TaiiNet did not have a concrete authentication model despite the issue requiring signed/encrypted messages, public-key-based filtering, username/key registration, cross-device auth transfer, React accessors, and auth coverage. This change adds an opt-in auth layer around existing message flow without changing unauthenticated usage.
Auth primitives
TaiiNetAuthwith:Identity + registry
registerUsername(...)lookupUsernameByPublicKey(...)lookupPublicKeysByUsername(...)Cross-device auth transfer
Subscription integration
Subscriptionnow supports auth-aware receive/send paths:sendSecure(...)for sealed messagesauth-data/auth-errorevents alongside existingdatabehaviorTaiiNet integration
TaiiNetaccepts an optional auth manager and exposes helpers for sealing/opening authenticated messages.React access
createTaiiNetAuthHooks(React, auth)inTaiiNetAuthReact.js.useTaiiNetAuth()with live auth state plus auth actions for app integration.Docs + auth coverage