Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

13.0 KB
Raw Blame

Seeker dApp Store submission checklist

Work top-to-bottom. Do not submit until every box is checked. A date after a box is when it was last verified against production; re-verify anything older than the current release.

1. Web app readiness (three.ws itself)

  • https://three.ws/manifest.webmanifest returns 200 with Content-Type: application/manifest+json. (verified 2026-08-27)
  • /pwa-192x192.png, /pwa-512x512.png, and /pwa-icon.svg return 200 with the right image type. (verified 2026-08-27)
  • The three TWA shortcuts resolve: /create, /marketplace, /my-agents all return 200. (verified 2026-08-27; /my-agents replaced the public /agents index)
  • Nothing blocks a TWA: the root sends no X-Frame-Options, and CSP frame-ancestors is irrelevant to a TWA (it is not an iframe). (verified 2026-08-27)
  • Service worker registered and ACTIVE inside the app (navigator.serviceWorker.getRegistration() reports an active worker scoped to https://three.ws/, read over Chrome DevTools inside the running TWA, 2026-08-28).
  • Chrome on Android offers "Add to Home screen" and the result opens standalone (device check).
  • start_url is /seeker?utm_source=seeker_app and renders inside the app with no console errors (emulator, 2026-08-28; profiled cold at Pixel 5 / slow 4G: LCP 1.5 s, CLS 0.003, 546 KB).

2. Digital Asset Links (DAL)

  • scripts/build-apk.sh has been run so the SHA-256 fingerprint is known. (2026-08-10; keystore at solana-mobile/android.keystore, password in .env SOLANA_MOBILE_KEYSTORE_PASSWORD; on a fresh headless machine run scripts/setup-android-sdk.sh first)
  • public/.well-known/assetlinks.json contains the real fingerprint (no {{RELEASE_SHA256}} placeholder) and is on main. (2026-08-10)
  • https://three.ws/.well-known/assetlinks.json returns 200 as application/json AND carries the 2026-08-27 fingerprint 98:0A:...:13:D7. (verified live 2026-08-28)
  • Google's statement list confirms the new key: https://digitalassetlinks.googleapis.com/v1/statements:list?source.web.site=https://three.ws&relation=delegate_permission/common.handle_all_urls returns 98:0A:...:13:D7 and nothing else. (verified 2026-08-28) On a device, follow with adb shell pm verify-app-links --re-verify ws.three.app.
  • cache-control on assetlinks.json is at most one hour: the live response reads max-age=3600, public. (re-verified against the live site 2026-08-28, after the deploy and CDN purge)

3. APK build

  • Release keystore is backed up offsite. The 2026-08-10 keystore was lost with its codespace (never backed up), so a NEW key was generated 2026-08-27 and stored in Secret Manager (three-ws-seeker-release-keystore, base64, and three-ws-seeker-keystore-password, project aerial-vehicle-466722-p5; round trip verified by sha256). Nothing was ever published under the old key. Never generate another.
  • build/three-ws-release.apk was produced by scripts/build-apk.sh and is signed. (2026-08-27, 4.1 MB, versionCode 1, targetSdk 36; build/ is gitignored, so rebuild on the release machine)
  • apksigner verify --print-certs prints the SHA-256 that is in assetlinks.json. (verified 2026-08-27: 98:0A:1A:AB:...:11:13:D7)
  • APK installs and launches FULL-SCREEN on Android 14 (Pixel 7 emulator, 2026-08-28): once the deploy carried the new assetlinks and Chrome's cached verification was cleared (pm clear com.android.chrome), the app opens straight onto /seeker with no address bar and no custom-tab chrome.
  • App icon, name, and splash colors match brand on a real launcher (three.ws, #080814 background, #000000 theme).
  • Long-press shortcuts Create / Discover / My agents are registered in the installed APK (dumpsys shortcut, 2026-08-27); each opens inside the app once DAL verifies.
  • The Android share sheet target is registered and baked into the APK: LauncherActivity carries the SEND/SEND_MULTIPLE filter for text/plain, image/jpeg, image/png, image/webp, model/gltf-binary, and the METADATA_SHARE_TARGET resource holds the /create/share POST config. (read back from the installed package, 2026-08-28. Bubblewrap rejects a file extension in accept, so .glb was dropped and model/gltf-binary carries GLB.)

4. MWA integration

  • Wrapper logic is unit-tested against a fake transport (npx vitest run tests/solana-mobile-mwa-*.test.js tests/solana-mobile-seeker-detect.test.js): authorize/resume, one-tap signIn, sign/send, error normalization, disconnect, session persistence across process death, revoked-token reset, detection boundaries. (49 tests green 2026-08-27)
  • solana-mobile/src/index.js is imported from the app entry points (src/wallet.js, src/game/play-auth.js). (verified 2026-08-27)
  • Emulator run against Solana Mobile's reference wallet: connect returns a real public key through the on-device flow; icon format and sign/send response shapes fixed. (2026-08, see the changelog)
  • window.threeWsWallet is defined and isSolanaMobileTwa() is true inside the app, INCLUDING on later in-app navigations (the detector now remembers the app entry signal; before that fix /login inside the app reported "No Solana wallet detected"). Verified over DevTools in the emulator, 2026-08-28.
  • The MWA association reaches a wallet: with Solana Mobile's reference wallet (fakewallet) installed, tapping Solana sign-in launches solana-wallet: and the wallet reports "Session active, awaiting requests from dApp". (emulator, 2026-08-28. The handshake does not finish there because Chrome 113's unverified-intent interstitial pops the tab back one history entry; that interstitial does not appear for a verified TWA on current Chrome, so completing it needs the device.)
  • First sign-in triggers the Seed Vault sheet (no Phantom/Solflare prompts).
  • One-tap SIWS: wallet linking shows a SINGLE Seed Vault sheet, and /api/auth/siws/verify accepts the wallet-built message.
  • signMessage (two-step fallback) produces a signature /api/auth/siws/verify accepts.
  • signAndSendTransaction lands on mainnet (test with a 0-lamport memo tx before any deploy flow).
  • Session survives suspend/resume AND a forced stop of the app (Settings > Apps > three.ws > Force stop, relaunch, sign again: no second prompt). The token now lives in localStorage.
  • A cancelled Seed Vault sheet surfaces as a clean "cancelled" state (code 4001 / reason USER_REJECTED), not a generic failure.
  • disconnect() removes the linked wallet from local state.

5. Listing copy (entered in the Publisher Portal)

  • publish/listing/description.md describes only features that exist in the app: selfie (one frontal + two optional angles) to rigged avatar, text and GLB creation, chat, marketplace, Metaplex Core deploy, USDC skills/tips, embeds, Seed Vault SIWS. (rewritten 2026-08-27)
  • publish/listing/new-in-version.txt reflects this exact build, no "coming soon". (2026-08-27)
  • publish/listing/saga-features.md cites Seed Vault signing, camera capture, and deep links / shortcuts, each verifiable in the APK. The earlier Web Share Target claim was removed: the live manifest declares none. (2026-08-27)
  • No third-party vendor names in the copy or media. (2026-08-27)
  • The text in the portal matches the files in publish/listing/ byte for byte (copy from git, not from memory).

6. Publisher Portal (owner, one-time)

  • Publisher profile created at https://publish.solanamobile.com as an Organization, KYB submitted 2026-08-27 and Approved (name three.ws, website https://three.ws). Confirmed in the portal 2026-08-28.
  • Publisher wallet connected (Phantom/Solflare/Backpack extension) and funded with at least 0.2 SOL for the App NFT, release NFT, and Arweave uploads.
  • Storage provider chosen (ArDrive recommended).
  • "Add a dApp" completed with publish/config.yaml values, publish/listing/, and publish/media/ (all eight images); App NFT minted.
  • API key created under Settings > API keys and stored in the owner's password manager (never in the repo).
  • The publisher wallet's keypair file is available to scripts/publish.sh as SOLANA_KEYPAIR and backed up offsite.

7. Policy compliance

  • Privacy policy is live at https://three.ws/legal/privacy and EULA at https://three.ws/legal/eula. (both 200 on 2026-08-27)
  • Privacy policy discloses wallet address collection (re-read before submitting).
  • No US-restricted activities (gambling, securities offerings, derivatives) in the copy. (2026-08-27)
  • Payment flows use SOL/USDC on-chain; no fiat onramp is surfaced inside the app. (2026-08-27)
  • Camera permission shows a visible justification at first prompt (device check on /create/selfie).
  • A wallet rejection (USER_REJECTED) is handled without crashing: src/wallet.js swallows it with no toast, everything else gets a retry toast. (unit + code review 2026-08-27)

7b. Home screen widget (1.1+)

  • build-apk.sh printed [apply-overlay] overlay applied before bubblewrap build (2026-08-29, versionCode 2, 1.1.0, 4.4 MB, same release key 98:0A:1A:AB:…:11:13:D7); a build without that line has no widget and must not ship.
  • aapt dump badging build/three-ws-release.apk lists ws.three.app.glance.GlanceWidget as a receiver and uses-permission: android.permission.INTERNET (2026-08-29, read back from the R8-minified release APK).
  • Emulator (Pixel 7, Android 14, 2026-08-29): the release APK registers Agent glance with the launcher (dumpsys appwidget), the link intent opens the pin dialog and places a 3x2 instance, and WorkManager runs the refresh with no app UI open. The debug variant against a local API with a real token then passed all five checks: card downloaded and painted (content description "My First Agent, 0 Moves today"), refreshed without opening the app, kept after am force-stop, back after adb reboot, and held with a "From 5:38 AM (offline). Tap to retry." footer in airplane mode, refreshing again once it was off. Recipe: README.md#the-home-screen-widget.
  • /api/glance/mine?format=png and /api/glance/token are deployed before the APK is published; the widget shows "Fetching your agent" until they are. (Live in production as of 2026-09-03: mine?format=png answers 200 image/png with x-glance-state: signed-out unauthenticated, token answers 401 without a session, and a real mint against the QA account returned a working token that fetched every card size.)

8. Repeat builds

  • KEYSTORE_PASSWORD=... ./scripts/build-apk.sh runs end-to-end unattended on the release machine (no interactive prompts).
  • Keystore path and password live in the owner's password manager, not in the repo.
  • appVersionCode was bumped in twa/twa-manifest.json (or via VERSION_CODE); the dApp Store rejects a re-used versionCode, and scripts/publish.sh refuses one it already shipped.
  • scripts/publish.sh completes with the publisher wallet's keypair and the portal API key.

9. Pre-submit smoke (real Seeker)

  • Fresh install: onboarding to a deployed agent takes under 3 minutes.
  • Camera capture under poor lighting degrades gracefully (the quality gates in src/selfie-gates.js explain what to fix; no infinite spinner).
  • Airplane mode: the app shows a clear network error, not a broken white page.
  • Deep links (https://three.ws/agents/...) open inside the app, not in Chrome. (App-link state is verified on the emulator, so this should hold; confirm on the device.)
  • Share a photo from the device's Photos app into three.ws and confirm it lands in /create/selfie already attached, then share a .glb and confirm it lands in /create. This CANNOT be verified over adb: am start --grant-read-uri-permission cannot confer a MediaStore URI grant, so android-browser-helper's re-grant to Chrome throws SecurityException: UID does not have permission to content://media/... before the web layer runs (observed 2026-08-28). A real sharing app grants the URI first. The web half is covered by tests/share-target.test.js and by the live POST /create/share fallback answering 303 to /create?shared=nosw.
  • Five 1080x1920 previews built and committed to publish/media/ (2026-08-28). They are one 5400x1920 carousel sliced into five, so upload them in numbered order; see docs/ASSETS.md. Optional upgrade: drop real Seeker captures into publish/media/device/ and rerun npm run build:dapp-store-previews.

10. Post-submission

  • Submitted 2026-08-28: v1.0.0 (versionCode 1), release #331044442814, In Review. Release NFT 25YeiFrv…khvcDDhQ in app collection GHJv3tR6…LUJSzTnD, mint tx 3aCYSrDe…1gxSDdZj, APK uploaded by URL from the v1.0.0 GitHub release. Full record: docs/seeker-submission-day.md.

  • Review results arrive by email from [email protected] within 3-5 business days; watch the portal dashboard.

  • On approval, verify the store listing renders all five screenshots and the feature graphic.

  • Add a data/changelog.json entry announcing the store listing with its link.