# Orb: product promise and acceptance evidence Reviewed October 2, 2026. This describes the current source checkout; it does not declare the new journey deployed or the public testnet trading rehearsal complete. ## Suggested submission description Orb is a social, gaming and trading workspace for communities on Monad. Members can connect in chat and voice, prepare trades with an AI assistant, review and execute with their own wallet, and share selected ideas and verified receipts. Wallet-linked contribution proofs and onchain community records make part of their identity portable and independently verifiable. Orb currently runs on Monad testnet; its social and media services remain hosted. The founder's origin story can follow this paragraph. It is not evidence of execution, adoption or a unique technical advantage. ## What the claims actually mean | Claim | Implemented mechanism | Boundary / evidence still required | | --- | --- | --- | | Simplifies onchain interactions | Privy onboarding; embedded wallet; natural-language Perpl/Spot drafts; in-chat review; bounded approvals; current quotes; receipt links | AI does not sign. Initial venue authorization, collateral, gas and liquidity remain prerequisites. A real funded public testnet trade/fill is still an acceptance gate. | | Digital identity | Verified account-wallet binding, signed chat-key attestations, selected wallet-linked Passport evidence, anchored proofs and community role gates | A wallet is not a unique human. Passport proves an issuer's commitment, not objective truth or trading skill. Login/recovery still depend on Privy. | | Digital ownership | User wallet export/withdrawal, contract-held assets and claims, independently readable registered community owner, portable proof bundles, ownership-checked ERC-721 profile avatars; new local owner-signed public capsules, community-profile association and downloadable independent client | The public registry remains separate from hosted chat, membership, moderation, feed and media. Linking requires current hosted ownership and verified wallet ownership onchain; it does not migrate the private database or grant roles. Files need actual IPFS retention. NFT ownership is checked when the avatar is applied, not continuously; automatic listing needs an indexer. | | Trading bots | Trading assistant and scoped community bot API exist | No autonomous AI execution or unrestricted server signer. Use “AI-assisted trading” unless demonstrating an actual user-authorized bot integration. | | Fast Monad coordination | Testnet contracts for games, contribution budgets, tokens, council and proof commitments | Measure actual public action-to-receipt time. Two browser clients or batched evidence do not establish 10,000 TPS. | | Complete / production ready | Reproducible automated checks and explicit release gates | No independent security audit, two-real-Privy-account acceptance or exhaustive device testing has been established. | ## Improvements in this local iteration - The ordinary community profile can create/link an independent public identity. Current hosted-owner and Privy-bound onchain wallet checks authorize the link; role administrators and other members cannot replace it. Only manually selected public templates go into the owner-signed capsule. - Funded missions can prefill an organizer's session plan; participants return to that session from the mission panel and explicitly claim approved credits there. The independent client checks the configured ORB mission/token runtimes, current contribution state and exact withdrawal receipts without Orb API or login. A withdrawal can aggregate rewards and refunds; it is not a per-mission receipt. - Home offers Connect / Trade / Play with a concrete next action, including an authorized community trade-room shortcut. Communities come before the quieter Explore section; no microphone, signature or trade starts from those shortcuts. - Arena's default is practice, without a wallet requirement. Explicit community, contract and Sprint links retain their separate modes. - The private assistant conversation survives navigation within the tab. Personal and room workspaces remain separate. Account changes destroy the cache; wallet changes reset the affected conversation. Transcripts never go to localStorage. - My activity lists drafts and last observed outcomes in the current workspace. It is not full exchange history or onchain proof of a Perpl fill. - Perpl attempts are recorded synchronously before the request. Closing the workspace during submission leaves a non-resendable unknown result. Inspect the venue before creating any new order. Venue protections remain separate. - Slow AI replies can be cancelled; late responses are discarded. Reading earlier assistant messages no longer forces the scroll to the bottom on each update. - `/proofs` explains wallet control, Passport and community records, provides a safe Spot-verifier shortcut and links public testnet deployment manifests. Its manifest records are not displayed as a fresh RPC verification. - Passport reads reject obsolete community responses, clear stale proof links, avoid overlapping polls and distinguish loading from a missing wallet. The community identity viewer selects legacy/v4 artifacts from configuration. - NFT application now checks the verified Privy session against the Orb profile, then the NFT owner onchain. Other wallets linked to the same authorized Privy account remain supported; NFT selection cannot silently create a spending link. IPFS images use the validated gateway and untrusted display names are bounded. ## Questions to answer with users 1. Can a new member join a community and find its activity without a guided call? 2. Does a community trade card produce useful discussion, rather than just more market noise? Would members voluntarily share it a second time? 3. Does a recipient understand that their margin, wallet and review are their own? 4. Can someone explain what their Passport proves after reading its screen? 5. Would an organizer schedule a second session or fund another useful mission? 6. Which specific reason brings a member back without promising token appreciation? ## Flagship recording and acceptance Use two real Privy accounts, two distinct embedded wallets and public Monad testnet funds. User A enters a community, asks the assistant for a trade, supplies margin, edits it and shares only the idea. User B reviews with their own amount. Complete a supported venue trade; distinguish acknowledgement from actual fill. Share a successful supported Spot receipt with explicit consent and verify it independently. Show the exact onchain record and its scope, not a fabricated badge. Record click / send / acknowledgement / venue-update / chain-receipt times separately. They measure different systems. Save redacted hashes and screenshots, not tokens, keys, private transcripts or third-party personal information. Then test wallet/account switching, cancellation, insufficient balance, liquidity failure, reload and navigation during submission. For communication, use actual microphones/live playback on physical Windows, Android and iOS devices. Run the Oracle backup restore, rollback and capacity drill. Independent wallet, contract and E2EE review remains necessary before accepting real value. ## Hackathon package The supplied Metropolis terms (version 3.0, September 3, 2026) require public GitHub source with an OSI-approved license, setup/architecture documentation, attribution, commit history, disclosure of AI coding tools, a working Monad mainnet/testnet prototype, and an actual-operation demo no longer than three minutes. Choose one main track. Sponsors have separate requirements. Disclose the reused Orbita foundation and the new work in the build window; do not imply every line was newly written. Prepare the public repository only after reviewing third-party rights and scanning tracked files and full history for secrets/personal data. Rotate disclosed credentials. Making a private repository public is a separate publishing action, not performed by this iteration. Preserve the real history rather than rewriting timestamps. The official page could not be retrieved by the research tool in this iteration. The checklist above comes from the supplied terms, not a claim that their current live version was verified. Check the submission dashboard for amendments. For the current product, **Social, Attention & Culture** is the strongest main-track fit: trading, games and contribution records support the community experience. That is a product judgment, not an eligibility ruling or a guarantee of winning. ## What makes the submission convincing The distinguishing loop is community conversation → privately reviewed action → user-chosen shared evidence → a portable record. A customer should be able to use that loop without an operator coaching them through every screen. Demonstrate one complete flow, then show an independent verifier with the Orb API unavailable. The trade receipt establishes the supported transaction's recorded outcome; Passport establishes issuer commitments. Neither establishes future profit, objective contribution quality, unique humans or a fully decentralized social app. Before adding another feature, interview a member and an organizer: what task did Orb save them from doing elsewhere, what made them return, and what would the organizer pay for? Existing mission fees and organizer tools are a revenue pilot, not evidence of willingness to pay or token appreciation.