Skip to content

docs: Thunder design spec — Seal-encrypt SuiNS messaging#8

Open
arbuthnot-eth wants to merge 2 commits into
masterfrom
feat/thunder-spec
Open

docs: Thunder design spec — Seal-encrypt SuiNS messaging#8
arbuthnot-eth wants to merge 2 commits into
masterfrom
feat/thunder-spec

Conversation

@arbuthnot-eth

Copy link
Copy Markdown
Owner

Summary

  • Design spec for Thunder: Seal-encrypt messages between SuiNS identities
  • Ciphertext stored on Walrus, on-chain inbox pointers in ThunderMailbox shared object
  • Fully opaque until recipient decrypts — no sender identity leaked
  • Built on forked Sui Stack Messaging SDK (mainnet-deployed)
  • UI: THUNDER button when viewing someone else's taken name, ⚡ badge on roster for incoming

Test plan

  • Review spec at docs/superpowers/specs/2026-03-28-thunder-design.md
  • Validate Move contract design (ThunderMailbox, seal_approve policy)
  • Validate Seal encrypt/decrypt flow
  • Validate UI integration points

Seal-encrypted messages between SuiNS identities with ciphertext on
Walrus and on-chain inbox pointers in a shared ThunderMailbox object.
Fully opaque until recipient decrypts — no sender identity leaked.
Built on the forked Sui Stack Messaging SDK deployed to mainnet.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant