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.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(seeker): say the app is submitted and in review everywhere it says otherwise
nirholasbd79c17cb499
diff --git a/STRUCTURE.md b/STRUCTURE.mdindex 88465781b..6308f6745 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -231,7 +231,7 @@ bottom.| BNB vault UI (browse/buy/unlock/view) | [pages/vault.html](pages/vault.html) + [src/vault.js](src/vault.js) `→ /vault`, buyer session key [src/bnb/vault-session.js](src/bnb/vault-session.js), buy calldata [src/bnb/vault-buy.js](src/bnb/vault-buy.js), browser ECIES decrypt [src/bnb/vault-crypto-browser.js](src/bnb/vault-crypto-browser.js), pure FSM helpers [src/vault-fsm.js](src/vault-fsm.js) — over the buyer API [api/vault/{list,status,unlock,download,buy-policy-data}.js](api/vault/list.js) and contract [contracts/src/GreenfieldVault.sol](contracts/src/GreenfieldVault.sol) (prompt 12) | In-repo · code+crypto proven on a local anvil-fork deploy, public testnet blocked on the same funded-deployer-key wall as prompts 07/09/10/11/13/14/18 | The buyer-facing face of Track B: a grid of live on-chain listings, a "buy" step that sends a real BSC testnet transaction (gasless via MegaFuel when sponsorable, self-pay fallback), an honest "granting access on Greenfield…" polling state for the async cross-chain permission grant, and an "unlock & view" step that decrypts the GLB entirely client-side (AES-256-GCM + secp256k1 ECIES via Web Crypto + `@noble/curves`, never the server) before rendering it in `<model-viewer>`. Because the vault's ECIES unlock needs the buyer's raw private key — which a browser extension wallet deliberately never exposes — the buyer identity is a local session key (same pattern as `src/agora/onchain-presence.js`); MetaMask's only role is funding that session key with a plain tBNB transfer. A "Sell a model" panel wires the real upload ([api/bnb/vault-upload.js](api/bnb/vault-upload.js)) + `list()` path from a directly-connected wallet. `GET /api/vault/buy-policy-data` builds a real Greenfield `Policy` protobuf for `buy()` when a listing's object has genuinely completed Greenfield upload (`api/_lib/bnb/vault-policy-data.js`); until then `buy()` uses an honestly-labeled deterministic placeholder, matching the prompt-11 anvil proof's own posture. || BNB Chain live block race | [pages/bnb-latency.html](pages/bnb-latency.html) + [src/bnb-latency.js](src/bnb-latency.js) `→ /bnb-latency`, pure helpers [src/bnb-latency-helpers.js](src/bnb-latency-helpers.js), live multi-chain API [api/bnb/latency.js](api/bnb/latency.js) over [api/_lib/bnb/latency-lanes.js](api/_lib/bnb/latency-lanes.js) (reuses `probeBlockTime` from [api/_lib/bnb/chains.js](api/_lib/bnb/chains.js) for BNB, adds Base/Ethereum/Solana lanes) | In-repo · shipped | Standalone, shareable proof page: four lanes (BNB Chain, Base, Ethereum, Solana) polled every 5s, each showing a freshly measured average block/slot time and a rolling sparkline — no hardcoded numbers, a down RPC shows "reconnecting" on just that lane. Headline strip shows BNB's live average plus its honest measured-vs-measured speedup over Base/Ethereum. Linked from the [/bnb](pages/bnb.html) hub's "real-time on-chain world" card, which auto-lights-up now that this route resolves. || BNB Chain payments (MPP, x402↔MPP bridge, gasless) | Accept [api/_lib/bnb/mpp-server.js](api/_lib/bnb/mpp-server.js) (`mppRequirements`/`mppChallenge`/`mppVerify`/`mppSettle`), pay [api/_lib/bnb/mpp-buyer.js](api/_lib/bnb/mpp-buyer.js) (`mppFetch`, re-exported from [api/_lib/x402-buyer-fetch.js](api/_lib/x402-buyer-fetch.js)), gasless rail [api/_lib/bnb/megafuel.js](api/_lib/bnb/megafuel.js), pilot dual-protocol endpoint [api/x402/three-intel.js](api/x402/three-intel.js) | In-repo · shipped, settlement needs merchant creds | three.ws speaks MPP (BNB Chain's Machine Payments Protocol) additively alongside x402: MPP's `b402` layer is x402 v2 byte-for-byte (same `X-PAYMENT`/`X-PAYMENT-RESPONSE`, same EIP-3009 credential), so a dual-protocol endpoint just advertises an extra BNB (`eip155:56`/`97`) accept entry and routes BNB-network payments to the b402 facilitator while Solana/Base traffic stays on the untouched x402 path. Verify (off-chain, free, replay-guarded via Redis `SET NX PX`) always runs before settle; without `B402_*` merchant credentials, settle fails closed with `mpp_not_configured` (503) rather than fabricating a receipt. Guide: [docs/bnb-payments.md](docs/bnb-payments.md). Wire contract: [specs/x402-mpp-bridge.md](specs/x402-mpp-bridge.md). Tests: [tests/bnb-mpp-server.test.js](tests/bnb-mpp-server.test.js), [tests/bnb-mpp-buyer.test.js](tests/bnb-mpp-buyer.test.js). |-| Seeker / Saga dApp Store app | [solana-mobile/](solana-mobile): TWA wrapper [solana-mobile/twa/](solana-mobile/twa), Publisher Portal listing copy [solana-mobile/publish/](solana-mobile/publish), MWA wallet + Seeker detection [solana-mobile/src/](solana-mobile/src) | In-repo · signed APK + assetlinks live · awaiting owner's Publisher Portal submission | Everything needed to package three.ws as a Solana Mobile app and publish it to the on-chain dApp Store. Targets Seeker first; compatible with Saga Gen 1 and Gen 2. Docs: [solana-mobile/README.md](solana-mobile/README.md) |+| Seeker / Saga dApp Store app | [solana-mobile/](solana-mobile): TWA wrapper [solana-mobile/twa/](solana-mobile/twa), Publisher Portal listing copy [solana-mobile/publish/](solana-mobile/publish), MWA wallet + Seeker detection [solana-mobile/src/](solana-mobile/src) | Submitted 2026-08-28 · v1.0.0 in review at the Solana dApp Store | Everything needed to package three.ws as a Solana Mobile app and publish it to the on-chain dApp Store. Targets Seeker first; compatible with Saga Gen 1 and Gen 2. Docs: [solana-mobile/README.md](solana-mobile/README.md) || iOS App Store app | [ios/](ios): Capacitor shell + config [ios/capacitor.config.ts](ios/capacitor.config.ts), Xcode project [ios/native/App/](ios/native/App), web-side native bridge [ios/src/native-bridge.js](ios/src/native-bridge.js), offline shell [ios/shell/](ios/shell), listing copy [ios/publish/](ios/publish), app association handler in [api/wk.js](api/wk.js) | In-repo · project builds and the web half ships on every deploy · awaiting an Apple Developer organization account | three.ws as a native iOS app (`ws.three.app`). A Capacitor 8 shell whose WKWebView runs the live `https://three.ws`, so the app is never a version behind the site; what makes it an app is the native layer around it. `ios/src/native-bridge.js` ships with the SITE, not the .ipa (Capacitor injects its bridge into the remote page, so `window.Capacitor` exists on three.ws only inside the app): it supplies the `navigator.share` WKWebView does not have, routes off-site links to an in-app Safari sheet instead of stranding the app's only WebView, handles universal links and `threews://` wallet returns, holds the launch screen until the first real frame, and marks `html.ios-app`. The `three-ws-ios-native-bridge` plugin in [vite.config.js](vite.config.js) copies it into `dist/` content-hashed and injects it into every built page except the third-party embed entries (671 pages, `/viewer` and `/ar` included, which a `transformIndexHtml` could not reach because they are copied verbatim from `public/`). `GET /.well-known/apple-app-site-association` is served from the API rather than a static file because Apple demands an exact path, a JSON content type and no redirect; it answers `503 not_configured` until `APPLE_TEAM_ID` is set rather than publishing an association that would fail silently on device. Docs: [ios/README.md](ios/README.md), [docs/ios-app.md](docs/ios-app.md), App Review posture [ios/docs/REVIEW-RISK.md](ios/docs/REVIEW-RISK.md), submission [ios/docs/SUBMISSION.md](ios/docs/SUBMISSION.md). || Walk Avatar browser extension | [extensions/walk-avatar/](extensions/walk-avatar) — MV3 `manifest.json`, `background.js` | In-repo · Chrome Web Store release checklist staged ([RELEASE.md](extensions/walk-avatar/RELEASE.md)) | Walks your three.ws avatar across any site and reads pages aloud — a browsing companion built on the same rig as the [walk-sdk](walk-sdk). Ships its own store-required [PRIVACY.md](extensions/walk-avatar/PRIVACY.md), [PERMISSIONS.md](extensions/walk-avatar/PERMISSIONS.md), and [TERMS.md](extensions/walk-avatar/TERMS.md). || Checkout companion browser extension | [extensions/checkout-companion/](extensions/checkout-companion) (MV3: [extract.js](extensions/checkout-companion/extract.js), [content.js](extensions/checkout-companion/content.js), [panel.js](extensions/checkout-companion/panel.js), [background.js](extensions/checkout-companion/background.js)), analysis [api/_lib/companion/checkout.js](api/_lib/companion/checkout.js), endpoint [api/companion/checkout.js](api/companion/checkout.js) | In-repo | The companion at the moment money moves: on a checkout page it reports the total against the price you were shown, money the page did not itemise, fees named and summed, whether the charge repeats, and the cancellation terms. **Arithmetic is never the model's job** (integer minor units, computed server-side) and **no finding is ever a legal verdict** (`sanitizeModelFindings()` drops any that claims an amount or calls something illegal). With no model reachable the arithmetic findings still stand. The extension **never reads an input**: `collectText`/`collectAmounts` refuse form fields, iframes and editable regions structurally, and redaction runs in the browser before anything is sent; only the hostname travels and nothing about the page is stored. Docs: [docs/checkout-companion.md](docs/checkout-companion.md). Tests: [tests/companion-checkout.test.js](tests/companion-checkout.test.js), [tests/checkout-extract.test.js](tests/checkout-extract.test.js) |diff --git a/docs/seeker-app.md b/docs/seeker-app.mdindex 5fa6a0a11..26e7c0f32 100644--- a/docs/seeker-app.md+++ b/docs/seeker-app.md@@ -2,6 +2,8 @@three.ws ships as a native Android app for the Solana Seeker (and Saga) through the Solana dApp Store. It is a Trusted Web Activity: the signed APK (`ws.three.app`) opens `https://three.ws/seeker` full-screen in Chrome's rendering engine with no browser chrome, and every wallet interaction is routed to the phone's Seed Vault through Mobile Wallet Adapter. For a WebGL product that is the right shape (it is what Solana Mobile recommends for web apps); what makes it feel like an app is everything around that shell. This page is the user-facing map of those pieces. The packaging and code layout live in [solana-mobile/README.md](../solana-mobile/README.md); how a release reaches the store is [Publishing to the Solana dApp Store](./seeker-publishing.md).+**Status: v1.0.0 was submitted to the Solana dApp Store on 2026-08-28 and is in review** (release `#331044442814`). Until it is approved the app is installable from the [v1.0.0 GitHub release](https://github.com/nirholas/three.ws/releases/tag/v1.0.0); everything described below is live on the web at [/seeker](/seeker) today.+## What the app does differently from the website| Surface | On Seeker | Where it lives |diff --git a/docs/seeker-publishing.md b/docs/seeker-publishing.mdindex 993db43fa..efcce54cd 100644--- a/docs/seeker-publishing.md+++ b/docs/seeker-publishing.md@@ -2,6 +2,8 @@How a release of the three.ws Seeker app gets from this repo onto the Solana dApp Store. This is the runbook; the app itself and what it adds over the website are described in [three.ws on Solana Seeker](./seeker-app.md), and the box-by-box submission gate lives in [solana-mobile/docs/CHECKLIST.md](../solana-mobile/docs/CHECKLIST.md). If you are the owner sitting down to actually submit, follow [Submission day](./seeker-submission-day.md) instead: it inlines every field and value so you never open a file.+**Status: v1.0.0 submitted 2026-08-28, in review** (release `#331044442814`, versionCode 1, package `ws.three.app`). What the portal recorded, including the release NFT mint and app collection, is in [Submission day](./seeker-submission-day.md).+Publishing changed shape in May 2026. `dapp-store-cli` 1.0 is **Publisher Portal backed**: the publisher identity, KYC, the App NFT, and all listing copy live in <https://publish.solanamobile.com>, and the CLI only uploads one signed APK per release. The old `dapp-store create publisher` / `create app` / `publish submit` chain is gone. Anything that still describes that flow is out of date.## Who does what@@ -10,7 +12,8 @@ Publishing changed shape in May 2026. `dapp-store-cli` 1.0 is **Publisher Portal|---|---|---|| Publisher profile, KYC/KYB, App NFT, API key | Owner, once | Publisher Portal (browser) || Screenshots on a physical Seeker | Owner, per listing change | Real device |-| Keystore restore, APK build, submission | Any agent, per release | This repo |+| Keystore restore and APK build | Any agent, per release | This repo |+| Uploading the release | Owner, per release | Publisher Portal, or the CLI |Everything scriptable is in [solana-mobile/scripts/](../solana-mobile/scripts/). The parts that need a human need an identity, a funded wallet, or a phone.@@ -31,6 +34,10 @@ Everything scriptable is in [solana-mobile/scripts/](../solana-mobile/scripts/).The release keystore is gitignored and lives in Secret Manager. The 2026-08-10 key was lost with the codespace that generated it, so a new one was created on 2026-08-27 and backed up properly. **Never generate a second key while this one exists**: the dApp Store identifies the app by its signing certificate, and losing it means the app can never be updated.+**Two ways to upload the release, and the browser one is preferable.** The portal's **New Version** page accepts the APK as a file or as a public URL and signs the release NFT with the wallet already connected in the browser. The CLI path below does the same thing but needs the publisher wallet's private key exported to a keypair file on disk, which is a real risk for no gain on a normal release. v1.0.0 went in through the browser, by URL, from the `v1.0.0` GitHub release.++Either way the APK has to exist and be signed first:+```bashcd solana-mobilediff --git a/solana-mobile/README.md b/solana-mobile/README.mdindex d310724c8..26e525500 100644--- a/solana-mobile/README.md+++ b/solana-mobile/README.md@@ -2,6 +2,8 @@Everything needed to package three.ws as an Android app and publish it: the Mobile Wallet Adapter (MWA) wallet that signs through the on-device Seed Vault, the Trusted Web Activity (TWA) wrapper, the release pipeline, and the listing copy for both stores.+**Status: v1.0.0 submitted to the Solana dApp Store on 2026-08-28 and in review** (release `#331044442814`, versionCode 1). The reviewed bytes are the `v1.0.0` GitHub release. Identifiers and what the portal recorded: [../docs/seeker-submission-day.md](../docs/seeker-submission-day.md).+**One package id, two channels.** `ws.three.app` ships to the Solana dApp Store (Seeker and Saga, listing copy in `publish/`) and to Google Play (every Android phone, listing copy and submission runbook in [`publish-play/`](publish-play/README.md)). Same build, same app, two store listings that must describe the same product. The Play path has one trap with no local symptom, and it is documented in `publish-play/README.md` step 6: Play re-signs the bundle with Google's own key, so Google's certificate fingerprint has to be added to `twa/extra-fingerprints.json` or every Play install loses full-screen mode.## Layout@@ -131,7 +133,8 @@ Until the commit that adds `/seeker` and the share handler is deployed, the emul## What still needs a physical Seeker-- **Screenshots** (`publish/media/screen-1..5.png`, 1080x1920): reviewers reject emulator or desktop captures, so none are checked in. `icon.png`, `banner.png`, and `feature.png` ARE checked in and regenerate with `node scripts/make-media.mjs` (the feature graphic is a live Playwright capture of a real agent page).+Listing media is no longer on that list. Everything the portal asks for is generated and checked in under `publish/media/`: `npm run build:dapp-store-media` writes the icon, banner, feature graphic, and the 1200x1200 Editor's Choice card, and `npm run build:dapp-store-previews` builds the five 1080x1920 previews as one carousel (see `docs/ASSETS.md`). Real Seeker captures dropped into `publish/media/device/` replace the browser ones and the carousel rebuilds around them.+- **Device smoke** (install, Seed Vault sheet, suspend/resume, deep links): section 3, 4, and 9 of `docs/CHECKLIST.md`.- **Promo video**: optional; `publish/media/video.mp4` if ever added.