Repository navigation
feat(chat-app): message recovery from Walrus archives - #77
Open
ioannischtz wants to merge 2 commits into
Open
ioannischtz wants to merge 2 commits into
ioannischtz wants to merge 2 commits into
Conversation
- WalrusRecoveryTransport (adapted from the SDK example): indexer patch list -> aggregator content -> SDK decryption; normalizes the archived Vec<u8> signature fields until the SDK fix ships in a release - wired via the factory's recovery option when indexer + aggregator URLs are configured (devstack defaults the indexer to localhost:3001) - Restore button in the chat header merges recovered messages into the open conversation Validated live: 2 archived messages recovered relayer-independently, decrypted + sender-verified. Co-Authored-By: Claude Fable 5 <[email protected]>
The dev-wallet server allowlists only the routed app origin; on 127.0.0.1:5173 the wallet shows no accounts (forbidden origin). Co-Authored-By: Claude Fable 5 <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Stacked on #76 (which stacks on #75). Closes the SEW-1004 recovery loop: the chat-app can restore a group's archived messages from Walrus without the relayer.
WalrusRecoveryTransport(chat-app/src/lib/walrus-recovery-transport.ts, adapted from the SDK's non-exported example): indexer patch list → aggregator content → SDK decryption. Wired via the factory'srecoveryoption when indexer + aggregator URLs are configured (VITE_INDEXER_URL, defaults tolocalhost:3001under devstack).signature/public_keybyte arrays to hex before mapping — the published SDK (0.0.2) passes them through raw, which silently kills sender verification on recovery. The SDK-side fix is deliberately NOT in this stack (avoids coupling to a release); it is parked onfix-sdk-walrus-message-signature-fieldsfor its own PR.127.0.0.1:5173is a forbidden origin for the dev-wallet server — no accounts show).Validated headless (2 archived messages recovered relayer-independently, decrypted + sender-verified) and manually in the UI (relayer restarted with empty store → member-check error on fetch → Restore brings history back).
Known reference-relayer limitation surfaced by the demo, out of scope: no checkpoint backfill, so a restarted relayer rejects fetches/sends for pre-existing groups (
develop-relayerlists backfill as the fork exercise).🤖 Generated with Claude Code