Authentication
Wallet proof establishes identity. It is not permission to spend or sign a transaction.
Stele is Monolythium's standalone web-marketplace product for services offered by people, businesses, and agents. The intended flow allows public browsing, browser-wallet authentication only when needed, and signing authority outside the hosted service. Application publication is independently release-gated.
A preview, a merged implementation, and an activated settlement capability are different states. Development-network RPC was reachable but stale at height 74,907 on 16 July 2026, so Stele does not use it as liveness or settlement evidence.
Wallet proof establishes identity. It is not permission to spend or sign a transaction.
OAuth-scoped search and non-economic draft preparation; no wallet custody or signing.
Listing writes, escrow, settlement, disputes, reviews, E2EE rooms, and mainnet remain disabled.
The canonical web application passed its explicit publication gate.
Stele owns discovery and workflow. The browser wallet remains a generic, independent trust boundary for identity and future transaction approval. Desktop embedding is being retired; older or unreconciled desktop builds may still show a disabled legacy surface until removal ships.
The intended public catalog is readable without an account, email address, tracking identity, or wallet session. Records are never presented as finalized on-chain listings without release evidence.
A Monolythium browser wallet authenticates private web sessions. Future economic actions return to the wallet for exact review, simulation, and approval.
Participant-controlled encrypted rooms, files, deliverables, and dispute evidence are product targets. The preview does not claim that E2EE collaboration is live.
Hosted MCP is keyless and limited to exactly two non-economic tools. A separately installed local MCP may later use a dedicated policy wallet only after SDK and protocol activation.
The full workflow is the product direction. Only steps whose capability gates have passed become actionable in the public interface.
Inspect public scope, price terms, coverage, and provenance without a wallet.
A person or hosted agent prepares an exact, expiring, wallet-owned request draft.
The wallet independently reconstructs and displays the exact transaction before signing.
Release, refund, or dispute results become finalized records only after canonical network evidence.
The trust models are deliberately separate. An OAuth token for hosted Stele can never become a signing key.
A user approves narrow OAuth scopes in a clean browser consent flow. Hosted Stele exposes exactly two tools: stele_search_services and stele_create_booking_draft. It can prepare a draft for later human review, but cannot hold funds, construct arbitrary calls, sign, or submit economic transactions.
A future local profile may use a separately created encrypted agent wallet under typed action, amount, asset, counterparty, network, and time limits. Current Stele tools expose only connection, public search, and dedicated-wallet status.
No wallet is required for public discovery. Economic actions and mainnet remain independently gated.