While building a Walrus Session 5 Prompt Jam submission, the proof requirements
were hard to map to the MemWal UI/MCP flow.
The form asks for MEMWAL_AGENT_ID and an explorer link showing the MemWal account
object/memories, but first-time users may not know whether MEMWAL_AGENT_ID means:
- the dashboard delegate key public key
- the MemWal account ID
- a Sui object ID
- a wallet address
- a blob ID from a memory write
It was also unclear how to confidently prove blob count from the MCP workflow. The
MCP tools return blob IDs after writes, but a beginner still has to infer which ID/
count/link belongs in the final form.
Suggested improvement:
Add a Prompt Jam proof section to the MemWal docs or dashboard that shows:
- the exact MEMWAL_AGENT_ID value to submit
- the exact explorer/account-object link to submit
- total memory blob count for the active agent/account
- recent blob IDs with Walruscan links
- a copy button for all submission proof fields
This would make the prompt-jam proof flow much easier for non-expert users.
While building a Walrus Session 5 Prompt Jam submission, the proof requirements
were hard to map to the MemWal UI/MCP flow.
The form asks for MEMWAL_AGENT_ID and an explorer link showing the MemWal account
object/memories, but first-time users may not know whether MEMWAL_AGENT_ID means:
It was also unclear how to confidently prove blob count from the MCP workflow. The
MCP tools return blob IDs after writes, but a beginner still has to infer which ID/
count/link belongs in the final form.
Suggested improvement:
Add a Prompt Jam proof section to the MemWal docs or dashboard that shows:
This would make the prompt-jam proof flow much easier for non-expert users.