Sui Overflow 2026PTB Atomic PaymentsAES 256

Pay, chat, and settle
in rooms that self-destruct

Encrypted
Client-side only

AES-GCM 256. The key is forged in your browser, never uploaded, and dies with the room.

Programmable
PTB-atomic payments

Tip, paid DM, subscription, or invoice — every Sui transfer is bundled atomically with its encrypted message.

Ephemeral
Self-destruct

Closing the room emits an on-chain event. Every client wipes its key. Only undecryptable bytes remain.

How It Works

Encrypt
Transact
Expire

Stripe meets Signal, on Sui. Tip, subscribe, negotiate, or invoice inside an encrypted room — every Sui transfer is PTB-atomic with its encrypted message. Close the room and the key is gone forever. Even if the ciphertext survives on IPFS, no one can decrypt it. No decrypt.

Why Now

Sui just clicked the missing pieces into place. Seal shipped to mainnet — native onchain encryption. Paired with USDsui, the consumer surface is finally here.

Seal — encryption native to Sui

Identity-based encryption with threshold cryptography. Define a policy on-chain; ciphertext only opens when the policy passes. SoSui sits at the intersection — Seal upgrades the invite envelope into a consumer-facing surface.

USDsui — gasless stablecoin

Stripe-issued stablecoin with protocol-level gas abstraction. Tip, subscribe, and settle in dollars without ever holding SUI. Phase 3 makes this the default settlement rail in SoSui.

SoSui
SoSui
00C$0ADFEDA$EE1EEF$ED1E*0C*A0F1AEE$01**C1ACD

SOSUI:ENCRYPTED.EPHEMERAL.IMMUTABLE.

Scroll to follow a payment room from creation to self-destruct.

Key Generation

Zoom into the browser's cryptographic library. Forges a 256-bit AES key.

WebCrypto API256-bit AES

Immutable Audit

Sui transaction hash is immutable.

Sui transaction hash
Sui transaction hash is immutable
Step 01
Encrypted from byte one

A room is born on Sui. Encrypted from the first byte.

53@*78f$

Encrypted Index

object_id53@*78f$$*815
dataciphered
indemnitysigned
checkpoint1ME-431
DraftRead

Pay the SUI fee. A shared object materializes on-chain — a room ready to hold secrets it can never read.

Step 02
Key Generated

Your browser forges a key no one else holds.

AES-256 Key
Client-Side Local StorageBrowser Web Crypto API

A 256-bit AES key is generated inside your tab. Never uploaded, never logged, never persisted to disk. Sovereignty you control — and only you.

Tip — drag across the key

Step 03
AES-GCM-256 Encryption

Messages travel as ciphertext. The network sees noise.

User View
@ryulis
53@ *78f$$
53@*7 8f
53@*78f $$*815
53@* 7 8f$$*8152#
Network View
0f29436d87a1cb
e50f29436d87a1
cbe50f29436d87
a1cbe50f29436d
87a1cbe50f2943
6d87a1cbe50f29
436d87a1cbe50f
29436d87a1cbe5
0f29436d87a1cb

Ciphertext Noise

Every line is sealed with AES-GCM in the browser, pushed to PTB, and anchored on Sui by content hash. Servers carry bytes they can't decode.

Step 04
Key Destroyed

Close the room. The key dies. The bytes stay locked.

ROOM · CC033DDestroyed

Room Closed

key wiped

local storage cleared

ciphertext remains · undecryptable

A close-event broadcasts. Every client wipes its copy of the key. The ciphertext lingers forever as PFS — and forever undecryptable.

SOSUI: Zero-Knowledge & Ephemeral Chat Journey.