Session state
BlockedWallet missing
Install a wallet first so bidding, claims, and seller actions can unlock in one place.
Governance
Transparency first. Protocol depth only when it helps.
This route explains protocol health, fallback policy, and session guidance in plain language before it asks anyone to think about operator mechanics.
At a glance
Signals worth trusting
SettlementStable
Confidential until completion
Winner selection stays hidden until the auction is fully resolved.
Fallback protectionGuarded
Refunds remain explicit
If settlement takes too long, the interface guides users toward refunds and the next safe step.
Network policyStable
Single-network release
Keeping one supported network makes wallet guidance simpler and reduces avoidable mistakes.
Claim flowContext
One place for outcomes
Claims, refunds, and seller proceeds stay grouped in the portfolio instead of scattering across screens.
Protocol windows
How the lot moves when settlement slows
Within delay budget
Monitor, do not panicAuction is resolving longer than expected
The most common case is simply that the proof round-trip is still in flight. Funds and claims remain locked by design during this window.
Stay on the lot or portfolio view and wait for the proof-backed transition.
Short post-proof lag
Allow indexing to settleProof returned, claims not yet surfaced
The chain may already be finalized while the interface is still catching up to the new state. This is a refresh/read-model issue, not a custody issue.
Refresh the route or reopen the portfolio surface before retrying the action.
Outside safe budget
Refund route becomes explicitFallback void executed
If the acceptable settlement window is exceeded, the lot can move into a deterministic fallback path that exposes refunds and seller-side slashing clearly.
Move to Portfolio and use the claim surface rather than retrying bid-side actions.
User guardrails
What the interface should say next
Wallet provider missing
BlockedNo wallet detected
Sensitive actions should pause immediately and the next step should stay obvious.
Install a wallet and reopen the session
Connected off-Sepolia
GuideWrong network selected
The interface should correct the network mismatch without making the user hunt for the right setting.
Offer one-click switch to Sepolia
User sees a prolonged resolving state
ContextSettlement took too long
Recovery language should tell the user exactly whether to wait, refresh, or move to claims.
Explain the delay budget and show the next safe action
Small-screen behavior
Reliability should stay readable everywhere
Thumb-safe actions
Primary actions stay large, isolated, and readable even when the user is mid-session on a smaller screen.
Recovery before complexity
On constrained screens, the user sees what to do next before they see implementation detail.
Compact guidance
The user should understand their next safe step without scrolling through extra technical panels.