Walrus Sessions · Round 2

Forms that can't be gaslit.

Every submission is a Walrus blob. Every form is a Sui object. Every viewer can independently audit the chain of custody.

Create a form Verify a form

Sessions feedback (shareable myfeedback.html?id=…) · Mainnet publisher HTTP — 502 notes

Loading latest activity…

The problem

Every other form tool has a conflict of interest.

Silent deletion

Survey vendors can silently delete bad reviews. You have no proof of what was actually submitted versus what they chose to display.

Co-located permissions

Form data lives in the same database as the form admin's permissions. The admin and the data store are the same actor.

No proof of record

Critics have no way to prove what was submitted versus what was shown. Any dispute becomes a he-said-she-said.

How it works

The integrity manifest you can check yourself.

When you close a form, WalForms computes a Merkle root over every submission blob ID and writes it to Sui.

Anyone can fetch all submissions from Walrus, recompute the Merkle root independently, and compare it to the on-chain value.

If a submission was deleted or altered, the computed root will not match the chain. The verifier will catch it.

The form admin cannot retroactively change the on-chain root. Immutability is enforced by the Sui object model.

For Walrus Sessions

Built for the case where the foundation runs its own feedback.

Walrus Foundation needs a feedback tool to run future Sessions. Here is why this one works for the case where the Foundation itself is the form admin: the Foundation cannot tamper with submissions, and participants can independently verify that. WalForms is the only feedback tool a foundation can run on itself without conflict of interest.

Cryptographic integrity Merkle-auditable Sui-native objects Walrus-native blobs

Try it live

Fill out the Walrus Sessions feedback form.

Tell us what you thought of Round 2. Your response goes directly to Walrus — we cannot edit it after submission.

Submit feedback

Open the shareable entrypoint (myfeedback.html), then enter your published WalForm ID if prompted. Mainnet HTTP publishers may return 502 — see publisher issue report & mitigations.