Implementation Blueprint

Developer Architecture

The browser wallet signs Sui Mainnet anchors, digest-only results remain visibly pending, and read-only Tatum RPC reports full success only after the complete proof bundle matches.

Architecture layers

Walrus SDK Relay Storage

Canonical Mainnet blob storage through the official SDK Upload Relay with wallet-paid storage and gas.

Direct Walrus

Aggregator read, availability, replay, and trace-hash comparison using Blob ID and Object ID.

Sui Proof Registry

Owned proof object with wallet signing, explicit pending-object state, and mainnet-ready anchor status.

Tatum Sui RPC

Read-only, allowlisted proof object, transaction, and event verification through Tatum RPC.

Server Boundary

API routes

POST /api/agent/run

POST /api/agent/prepare

POST /api/storage/upload

GET /api/storage/relay-status

GET /api/storage/status/[uploadJobId]

GET /api/storage/list

POST /api/storage/cancel-renewal

POST /api/storage/delete

GET /api/storage/read/[blobId]

POST /api/storage/verify/[blobId]

GET /api/walrus/read/[blobId]

POST /api/walrus/verify/[blobId]

POST /api/tatum/rpc

POST /api/sui/verify-proof

POST /api/sessions/[id]/proof-anchor

Tatum Sui RPC Diagnostics

Proof-read readiness

Ready

Status: Ready
Network: Sui Mainnet
RPC host: sui-mainnet.gateway.tatum.io
API key present: Yes
Read allowlist: sui_getObject, sui_getTransactionBlock, suix_queryEvents

Session Storage Diagnostics

Archive durability

Supabase

Storage backend: Supabase
Durable on Vercel: Yes
Supabase URL present: Yes
Service role present: Yes
Anon key present: Yes

Contract Plan

Sui AgentSessionProof object

The Move package stores lightweight proof metadata only: owner, session ID, mode, hashes, Walrus references, upload references, timestamp, and anchor status.

POST /api/sessions/[id]/storage-finalize

GET /api/verify/[id]

Operational Readiness

Integration checklist

1Walrus Mainnet storage uses the official SDK Upload Relay.
2Live Walrus Blob ID and available Object ID references are persisted.
3Direct aggregator reads and trace hashes are verified as the canonical storage proof path.
4Tatum Sui RPC is exposed through a read-only allowlisted server route.
5Sui proof anchors are signed in the browser by the connected wallet.
6Digest-only anchors remain pending until object or event verification succeeds.
7Proof verification compares session ID, owner, hashes, Walrus Blob ID, object, transaction, and event fields.
8Sui wallet analysis uses public Sui JSON-RPC balance, object, and transaction reads.

2026-06-15T06:17:59.797Z

Last result

Tatum RPC is reachable.

Walrus Proof Storage

Blob-read readiness

Configured

Storage method: Walrus SDK Upload Relay
Network: Walrus Mainnet
Upload relay: https://upload-relay.mainnet.walrus.space
Aggregator: https://aggregator.walrus-mainnet.walrus.space
Relay reachable: Reachable
Relay tip: Available
Last check: 2026-06-15T06:17:59.807Z

ghzvlakyufwfyxzfwigi.supabase.co

agent_sessions reachable

Last storage check

2026-06-15T06:17:59.823Z

Last storage error

TypeError: fetch failed

Real sessions loaded

Sample fallback

Active

Current behavior

Dashboard shows curated sample traces until a real session is recorded.

Production recommendation

Check the agent_sessions table, service role key, and Supabase project URL.

Data Model

AgentSession evidence bundle

Session metadata, input files, deterministic AgentTrace, StorageReference, WalrusVerification, ProofMetadata, TatumRpcVerification, and VerificationResult are kept as typed boundaries. Local JSON session storage is intended for controlled evaluation and is not serverless-safe.

Sui Analyzer Scope

Sui-native data reads

The active onchain analyzer accepts Sui wallets, transaction digests, object IDs, and package IDs. It reads balances, coin metadata, owned objects, recent transaction blocks, and object/package details through Sui JSON-RPC without non-Sui provider fallbacks.