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.

docs(seeker): write the dApp Store release runbook and record what the live deploy verified

nirholas6b13359c59e4
diff --git a/CHANGELOG.md b/CHANGELOG.md
index c96fc0b9d..5ad854550 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -8,12 +8,16 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Companion** (`/companion`): A 3D companion that delivers your important messages in person. Connect your own Telegram bot, calendar, inbox, or phone, give each contact their own avatar and voice, and hear only what clears your bar.
- **Docs · Feedback** (`/docs/feedback`): Telling the corner companion what broke: the proactive ask at the moment of failure, the route, build SHA, and console errors captured for you, the severity and clustering rules, the report API, and the boundary that keeps untrusted visitor text from ever reaching anything with write access.
+- **Publishing to the Solana dApp Store** (`/docs/seeker-publishing`): The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.
+- **three.ws on iOS** (`/docs/ios-app`): What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission prompts, and an offline screen that recovers on its own.
- **Agent history catches up on fast chains in days instead of weeks**: The cross-chain index read one window of blocks per chain every 15 minutes. That is enough to keep pace with a slow chain but not to close a gap on a fast one: Arbitrum was 18.4 million blocks behind and would have taken about six weeks to catch up, while most runs finished early with most of their time budget unused. Runs now spend that spare time on whichever chain is furthest behind, and do nothing extra when every chain is current. `[improvement]`
- **Agent history on Base, Ethereum and Gnosis is moving again**: The cross-chain agent index had stopped advancing on three networks. A single unprintable byte inside an on-chain metadata string was rejected by the database, and because the index only records its position after a successful write, every following run re-read the same block and hit the same byte. Base had been frozen for 13 days, Gnosis for 15 and Ethereum for 4. Those bytes are now stripped on the way in, so the event is kept and the crawl moves past it. Registrations, ownership transfers, metadata edits and reputation attestations on those chains flow into agent profiles again. `[fix]`
- **Agent payments now stop themselves when the fee wallet runs dry**: The platform sponsors the network fee on every agent payment. When that wallet ran down to the point where it could not cover a single fee, the check meant to pause payments could not run, because it depended on a balance lookup and the network providers were rate-limited at the same moment. Payments kept being attempted for three hours and none of them could complete. The pause now reads its answer from the failure itself, which costs nothing and works exactly when the network is too busy to answer questions. The status page also names the real cause now, a wallet that needs funding, instead of pointing at the payment rail. `[fix, infra]`
- **Next on the roadmap: your agent on your home screen**: A fifth phase has been added to the public roadmap: native widgets. Right now three.ws is something you open. The plan is for the agent you own to sit on your home screen and your desktop, showing itself and one live number about it, refreshed by the system without you opening anything, with a tap that drops you back into the right screen. Android is first, because the Android app is already built and signed: three.ws ships as a real app for Solana Seeker, and as of today Google confirms the app's release key against the site, so a three.ws link opens inside the app instead of a browser tab. Windows 11 follows through the installed web app, which needs no separate store submission, then macOS and iOS through a shared widget extension. None of it is shipped yet. It is written down, scoped and public so you can hold us to it, and the phase is on the roadmap in the repo along with the work order behind it. `[docs]`
- **Photo uploads, avatar saves, launches and team tasks fail fast instead of hanging**: A handful of steps still had no time limit on the outside service they called. When that service accepted the connection and then went quiet, the request sat there until the platform killed it, and you got a spinner that ended in nothing: a photo-to-avatar upload that never came back, a saved model that never finished downloading, a coin launch stuck fetching its own thumbnail, an ordinals order whose status never loaded, a team task where one hired agent held up the whole run. Each of those now has a deadline and a clear answer when it is missed, and the ones that are safe to repeat retry once first. Anything that spends money or starts a generation is never repeated: it is bounded and then reported, so no upload is billed twice and no hire is paid twice. Saving a model from a link is also checked more tightly now, against the address it actually connects to and with the size limit applied while it downloads. `[improvement, fix, infra]`
- **Tell the agent in the corner what is broken**: The companion that walks your pages now listens. When a page actually fails, it turns and asks what you were doing, and the report it sends carries what you should never have to type: the page, the exact build it happened on, your screen size, and the errors the browser recorded at that moment. You can also open it any time from the control beside the avatar, and dictate instead of typing. Reports are grouped so that twenty people hitting one problem read as one problem, and every one of them is read by a person before anything changes. (`/docs/feedback`) `[feature, improvement]`
+- **The iOS app now exists in the repo, and the web half of it ships today**: three.ws is being packaged for the App Store as a native iOS app. The container and its Xcode project are in the repo, and the part that runs inside the website went live with this deploy: on iPhone the app will get a working share sheet, links that open the app instead of Safari, wallet sign-ins that return to the exact page you left, and a real offline screen. Nothing changes on the web. What is still outstanding is an Apple Developer organization account, app icons, and push notifications. (`/docs/ios-app`) `[feature, infra]`
+- **The Seeker app now runs full-screen, and its release process is written down**: The three.ws app on Solana Seeker verifies against the site and opens full-screen on its own home screen, with no browser address bar. Two bugs found while testing it on a real Android build are fixed: the app only recognised your Seed Vault wallet on the first page you opened, so signing in from the login page said no wallet was found, and the login page never loaded the wallet at all. A new guide documents exactly how a release reaches the Solana dApp Store, from the publisher account through building and submitting the app. (`/docs/seeker-publishing`) `[fix, docs]`
- **Your agent now tells you the important things in person**: Notifications no longer wait behind a badge. When something worth stopping for lands while you are on the site (a sale, money in, a 3D generation finishing, anything touching your account), your corner companion turns to you, plays a gesture, and says it out loud with a link straight to it. If the companion is switched off it is summoned for that one message and walks off again, without turning itself back on. It is a real delivery channel next to in-app, push, email and Telegram: toggle it per category in Settings, and there is a Turn off control in the bubble that silences it in that browser instantly. It only ever announces unread notifications under fifteen minutes old, says each one exactly once, caps itself at two per visit, and never speaks into a background tab. Nothing is spoken aloud unless you already turned on the companion's voice; otherwise it is text in the bubble, which screen readers announce too. (`/notifications`) `[feature]`
## 2026-08-27
diff --git a/data/changelog.json b/data/changelog.json
index 69de16fc6..69af97fc2 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,16 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-08-28",
+ "title": "The Seeker app now runs full-screen, and its release process is written down",
+ "summary": "The three.ws app on Solana Seeker verifies against the site and opens full-screen on its own home screen, with no browser address bar. Two bugs found while testing it on a real Android build are fixed: the app only recognised your Seed Vault wallet on the first page you opened, so signing in from the login page said no wallet was found, and the login page never loaded the wallet at all. A new guide documents exactly how a release reaches the Solana dApp Store, from the publisher account through building and submitting the app.",
+ "tags": [
+ "fix",
+ "docs"
+ ],
+ "link": "/docs/seeker-publishing"
+ },
{
"date": "2026-08-28",
"title": "Tell the agent in the corner what is broken",
@@ -25128,6 +25138,16 @@
"docs"
],
"link": "/docs/open-source-ecosystem"
+ },
+ {
+ "date": "2026-08-28",
+ "title": "The iOS app now exists in the repo, and the web half of it ships today",
+ "summary": "three.ws is being packaged for the App Store as a native iOS app. The container and its Xcode project are in the repo, and the part that runs inside the website went live with this deploy: on iPhone the app will get a working share sheet, links that open the app instead of Safari, wallet sign-ins that return to the exact page you left, and a real offline screen. Nothing changes on the web. What is still outstanding is an Apple Developer organization account, app icons, and push notifications.",
+ "tags": [
+ "feature",
+ "infra"
+ ],
+ "link": "/docs/ios-app"
}
]
}
diff --git a/data/pages.json b/data/pages.json
index cb4841ced..d481b1c8f 100644
--- a/data/pages.json
+++ b/data/pages.json
@@ -3174,6 +3174,18 @@
"description": "What the Seeker app adds on top of the website: Seed Vault sign-in, share-sheet capture, an offline shell, home-screen shortcuts, and Seeker Genesis Token verification.",
"added": "2026-08-27"
},
+ {
+ "path": "/docs/seeker-publishing",
+ "title": "Publishing to the Solana dApp Store",
+ "description": "The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.",
+ "added": "2026-08-28"
+ },
+ {
+ "path": "/docs/ios-app",
+ "title": "three.ws on iOS",
+ "description": "What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission prompts, and an offline screen that recovers on its own.",
+ "added": "2026-08-28"
+ },
{
"path": "/docs/money-flow-map",
"title": "Docs · Money Flow Map",
diff --git a/docs/seeker-app.md b/docs/seeker-app.md
index 548eee323..5fa6a0a11 100644
--- a/docs/seeker-app.md
+++ b/docs/seeker-app.md
@@ -1,6 +1,6 @@
# three.ws on Solana Seeker
-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, release pipeline, and store checklist live in [solana-mobile/README.md](../solana-mobile/README.md).
+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).
## What the app does differently from the website
diff --git a/docs/seeker-publishing.md b/docs/seeker-publishing.md
new file mode 100644
index 000000000..402c3c2c0
--- /dev/null
+++ b/docs/seeker-publishing.md
@@ -0,0 +1,93 @@
+# Publishing three.ws to the Solana dApp Store
+
+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).
+
+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
+
+| Step | Who | Where |
+|---|---|---|
+| 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 |
+
+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.
+
+## One-time setup (owner, in the portal)
+
+1. Create the publisher profile at <https://publish.solanamobile.com> and submit KYC/KYB. Approval gates everything below.
+2. Connect the publisher wallet (Phantom, Solflare, or Backpack extension). Fund it with **at least 0.2 SOL** to cover the App NFT, each release NFT, and ArDrive upload fees.
+3. Choose a storage provider. ArDrive is the recommended default.
+4. **Add a dApp**, filling every field from the repo rather than from memory, so the portal and git never drift:
+ - identity and URLs: [solana-mobile/publish/config.yaml](../solana-mobile/publish/config.yaml)
+ - listing text: [solana-mobile/publish/listing/](../solana-mobile/publish/listing/) (long description, short description, what's-new, Seeker features)
+ - media: [solana-mobile/publish/media/](../solana-mobile/publish/media/) (icon, banner, and feature graphic are committed; screenshots are not, see below)
+
+ Completing this mints the **App NFT**. The portal matches later uploads to this app by Android package name, `ws.three.app`.
+5. Settings → API keys → create one. Store it in the owner's password manager; it never goes in the repo.
+
+## Per release (in this repo)
+
+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.
+
+```bash
+cd solana-mobile
+
+# 1. Restore the keystore and its password.
+gcloud secrets versions access latest --secret three-ws-seeker-release-keystore \
+ --project aerial-vehicle-466722-p5 | base64 -d > android.keystore
+export SOLANA_MOBILE_KEYSTORE_PASSWORD="$(gcloud secrets versions access latest \
+ --secret three-ws-seeker-keystore-password --project aerial-vehicle-466722-p5)"
+
+# 2. On a machine with no Android toolchain (a fresh codespace), stage one.
+./scripts/setup-android-sdk.sh
+
+# 3. Build the signed APK. Also rewrites /public/.well-known/assetlinks.json
+# with this keystore's SHA-256 fingerprint.
+KEYSTORE_PASSWORD="$SOLANA_MOBILE_KEYSTORE_PASSWORD" ACCEPT_ANDROID_SDK_LICENSES=1 \
+ ./scripts/build-apk.sh
+
+# 4. Deploy three.ws so the assetlinks file is live for this key, then confirm
+# Google can see it (deploy runbook: CLAUDE.md, or docs/ops/gcp-production.md).
+curl -fsSL https://three.ws/.well-known/assetlinks.json | jq .
+curl -fsSL 'https://digitalassetlinks.googleapis.com/v1/statements:list?source.web.site=https://three.ws&relation=delegate_permission/common.handle_all_urls'
+
+# 5. Submit.
+SOLANA_KEYPAIR=~/.config/solana/publisher.json \
+DAPP_STORE_API_KEY='<portal API key>' \
+./scripts/publish.sh
+```
+
+[scripts/publish.sh](../solana-mobile/scripts/publish.sh) checks that assetlinks is reachable, refuses a `versionCode` it already shipped from this machine, passes the API key over stdin so it never appears in a process listing, uploads the APK, mints the release NFT, and submits for review. If the upload dies part way through, resume it with `npx --no-install dapp-store resume --release-id <id>` rather than starting over.
+
+For a later release, bump `appVersionCode` and `appVersion` in [solana-mobile/twa/twa-manifest.json](../solana-mobile/twa/twa-manifest.json) (or pass `VERSION_CODE` / `VERSION_NAME`), then repeat steps 3 and 5. The store rejects a reused `versionCode`.
+
+Releases are run locally by the owner. This repo does not use GitHub Actions.
+
+## Step 4 is not optional
+
+Digital Asset Links are what make the app run full-screen. Until `https://three.ws/.well-known/assetlinks.json` serves the fingerprint of the key that signed the APK, Chrome cannot verify the Trusted Web Activity and falls back to a custom tab with a visible address bar, which reviewers see as an unfinished app.
+
+Two traps, both observed on 2026-08-28:
+
+- **The header must be short-lived.** `.well-known/*` is served with `max-age=3600`. A day-long TTL means a rotated key stays unverified for up to a day after the deploy.
+- **Chrome caches a failed verification.** After the correct assetlinks goes live, an already-installed app can keep showing the address bar until Chrome's cache clears. Force it with `adb shell pm clear com.android.chrome`, or `adb shell pm verify-app-links --re-verify ws.three.app` followed by `adb shell pm get-app-links ws.three.app`, which should print `three.ws: verified`.
+
+## Screenshots
+
+`publish/media/` carries `icon.png`, `banner.png`, and `feature.png`, all regenerable with `node scripts/make-media.mjs` (the feature graphic is a live Playwright capture of a real agent page). The five 1080x1920 screenshots are deliberately absent: reviewers reject emulator and desktop captures, and a placeholder is worse than a missing file. Capture them on a real Seeker following [solana-mobile/docs/ASSETS.md](../solana-mobile/docs/ASSETS.md), which lists the exact frame each one should show.
+
+## Verifying a build before submitting
+
+Most of the app can be checked in a stock Android emulator; the recipe is in [solana-mobile/README.md](../solana-mobile/README.md#emulator-qa). What the emulator does prove: install, full-screen launch, home-screen shortcuts, app-link verification state, the service worker registering, the MWA association reaching a wallet (with Solana Mobile's reference wallet sideloaded), and that the share target is registered with the right MIME types.
+
+What it cannot prove, and therefore what a physical Seeker is still for:
+
+- **The Seed Vault sheet itself**, and a completed one-tap SIWS sign-in. The emulator's Chrome shows an unverified-intent interstitial that interrupts the MWA handshake; a verified TWA on current Chrome does not.
+- **A real share.** `adb shell am start --grant-read-uri-permission` cannot confer a MediaStore URI grant, so the receiving app throws `SecurityException` before any web code runs. A genuine share from Photos grants the URI first. The web half of that flow is covered by `tests/share-target.test.js` and by the live `POST /create/share` fallback.
+- **A mainnet transaction** approved in the secure element.
+
+## After submitting
+
+Review results arrive by email from `[email protected]` within 3 to 5 business days; the portal dashboard shows status in the meantime. On approval, check that the public listing renders all five screenshots and the feature graphic, then add a [data/changelog.json](../data/changelog.json) entry announcing it.
diff --git a/docs/start-here.md b/docs/start-here.md
index 8612647cb..5a599f0f3 100644
--- a/docs/start-here.md
+++ b/docs/start-here.md
@@ -165,6 +165,8 @@ Deeper references that don't fit a track above but answer real questions:
- [NVIDIA models on three.ws](./nvidia-models.md): the free hosted inference layer model by model, one key behind text-to-3D, chat, vision, embeddings, safety, and speech
- [Run an inference node](./inference-node-operator.md): join the supply side of the open inference network with your own hardware, from clone to a signed, verified result, on CPU or an NVIDIA GPU
- [three.ws on Solana Seeker](./seeker-app.md): the Android app for Seeker and Saga, and what it adds on top of the website (Seed Vault sign-in, share-sheet capture, offline shell, Seeker verification)
+- [Publishing to the Solana dApp Store](./seeker-publishing.md): the release runbook for the Seeker app, from the Publisher Portal setup and the release keystore through building, verifying, and submitting a signed APK
+- [three.ws on iOS](./ios-app.md): the App Store app, what it adds on top of the website (native share sheet, universal links, wallet deep links, offline shell), and how the web half of it ships on every deploy
- [Free LLM providers](./free-llm-providers.md): the failover chain of a dozen free AI providers behind every text completion, what each free tier gives, and how to add the next rung
- [Tokens API on three.ws](./tokens-xyz.md): the Solana Foundation asset layer that tells us which mints are the same asset, why it sits second in the market-data cascade, and the one env var that turns it on
- [NVIDIA Inception membership](./nvidia-inception.md): what the platform already runs on NVIDIA silicon and what the program adds on top
diff --git a/public/changelog.json b/public/changelog.json
index 906e85176..0a20832f4 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-28T02:37:00.919Z",
+ "generated_at": "2026-08-28T03:09:16.869Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -26,6 +26,26 @@
"launch"
]
},
+ {
+ "date": "2026-08-28",
+ "type": "launch",
+ "title": "Publishing to the Solana dApp Store",
+ "summary": "The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.",
+ "link": "/docs/seeker-publishing",
+ "tags": [
+ "launch"
+ ]
+ },
+ {
+ "date": "2026-08-28",
+ "type": "launch",
+ "title": "three.ws on iOS",
+ "summary": "What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission prompts, and an offline screen that recovers on its own.",
+ "link": "/docs/ios-app",
+ "tags": [
+ "launch"
+ ]
+ },
{
"date": "2026-08-28",
"type": "update",
@@ -90,6 +110,28 @@
"improvement"
]
},
+ {
+ "date": "2026-08-28",
+ "type": "update",
+ "title": "The iOS app now exists in the repo, and the web half of it ships today",
+ "summary": "three.ws is being packaged for the App Store as a native iOS app. The container and its Xcode project are in the repo, and the part that runs inside the website went live with this deploy: on iPhone the app will get a working share sheet, links that open the app instead of Safari, wallet sign-ins that return to the exact page you left, and a real offline screen. Nothing changes on the web. What is still outstanding is an Apple Developer organization account, app icons, and push notifications.",
+ "link": "/docs/ios-app",
+ "tags": [
+ "feature",
+ "infra"
+ ]
+ },
+ {
+ "date": "2026-08-28",
+ "type": "update",
+ "title": "The Seeker app now runs full-screen, and its release process is written down",
+ "summary": "The three.ws app on Solana Seeker verifies against the site and opens full-screen on its own home screen, with no browser address bar. Two bugs found while testing it on a real Android build are fixed: the app only recognised your Seed Vault wallet on the first page you opened, so signing in from the login page said no wallet was found, and the login page never loaded the wallet at all. A new guide documents exactly how a release reaches the Solana dApp Store, from the publisher account through building and submitting the app.",
+ "link": "/docs/seeker-publishing",
+ "tags": [
+ "fix",
+ "docs"
+ ]
+ },
{
"date": "2026-08-28",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 41201698c..ed713b2f8 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -22,6 +22,22 @@
<category>launch</category>
<description>Telling the corner companion what broke: the proactive ask at the moment of failure, the route, build SHA, and console errors captured for you, the severity and clustering rules, the report API, and the boundary that keeps untrusted visitor text from ever reaching anything with write access.</description>
</item>
+ <item>
+ <title>Publishing to the Solana dApp Store</title>
+ <link>https://three.ws/docs/seeker-publishing</link>
+ <guid isPermaLink="false">2026-08-28:Publishing to the Solana dApp Store</guid>
+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
+ <category>launch</category>
+ <description>The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.</description>
+ </item>
+ <item>
+ <title>three.ws on iOS</title>
+ <link>https://three.ws/docs/ios-app</link>
+ <guid isPermaLink="false">2026-08-28:three.ws on iOS</guid>
+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
+ <category>launch</category>
+ <description>What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission prompts, and an offline screen that recovers on its own.</description>
+ </item>
<item>
<title>Agent history catches up on fast chains in days instead of weeks</title>
<link>https://three.ws/changelog</link>
@@ -70,6 +86,22 @@
<category>feature</category>
<description>The companion that walks your pages now listens. When a page actually fails, it turns and asks what you were doing, and the report it sends carries what you should never have to type: the page, the exact build it happened on, your screen size, and the errors the browser recorded at that moment. You can also open it any time from the control beside the avatar, and dictate instead of typing. Reports are grouped so that twenty people hitting one problem read as one problem, and every one of them is read by a person before anything changes.</description>
</item>
+ <item>
+ <title>The iOS app now exists in the repo, and the web half of it ships today</title>
+ <link>https://three.ws/docs/ios-app</link>
+ <guid isPermaLink="false">2026-08-28:The iOS app now exists in the repo, and the web half of it ships today</guid>
+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>three.ws is being packaged for the App Store as a native iOS app. The container and its Xcode project are in the repo, and the part that runs inside the website went live with this deploy: on iPhone the app will get a working share sheet, links that open the app instead of Safari, wallet sign-ins that return to the exact page you left, and a real offline screen. Nothing changes on the web. What is still outstanding is an Apple Developer organization account, app icons, and push notifications.</description>
+ </item>
+ <item>
+ <title>The Seeker app now runs full-screen, and its release process is written down</title>
+ <link>https://three.ws/docs/seeker-publishing</link>
+ <guid isPermaLink="false">2026-08-28:The Seeker app now runs full-screen, and its release process is written down</guid>
+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The three.ws app on Solana Seeker verifies against the site and opens full-screen on its own home screen, with no browser address bar. Two bugs found while testing it on a real Android build are fixed: the app only recognised your Seed Vault wallet on the first page you opened, so signing in from the login page said no wallet was found, and the login page never loaded the wallet at all. A new guide documents exactly how a release reaches the Solana dApp Store, from the publisher account through building and submitting the app.</description>
+ </item>
<item>
<title>Your agent now tells you the important things in person</title>
<link>https://three.ws/notifications</link>
diff --git a/public/features.json b/public/features.json
index ea5aca5bb..45a498ff4 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-28T02:37:00.902Z",
+ "generated_at": "2026-08-28T03:09:16.844Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
@@ -3937,6 +3937,26 @@
"tags": [],
"showcase": false
},
+ {
+ "path": "/docs/seeker-publishing",
+ "title": "Publishing to the Solana dApp Store",
+ "description": "The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.",
+ "added": "2026-08-28",
+ "auth": null,
+ "indexable": true,
+ "tags": [],
+ "showcase": false
+ },
+ {
+ "path": "/docs/ios-app",
+ "title": "three.ws on iOS",
+ "description": "What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission prompts, and an offline screen that recovers on its own.",
+ "added": "2026-08-28",
+ "auth": null,
+ "indexable": true,
+ "tags": [],
+ "showcase": false
+ },
{
"path": "/docs/money-flow-map",
"title": "Docs · Money Flow Map",
diff --git a/public/llms-full.txt b/public/llms-full.txt
index 7e3f7a49a..a543aab3d 100644
--- a/public/llms-full.txt
+++ b/public/llms-full.txt
@@ -2391,6 +2391,18 @@ URL: https://three.ws/docs/seeker-app
What the Seeker app adds on top of the website: Seed Vault sign-in, share-sheet capture, an offline shell, home-screen shortcuts, and Seeker Genesis Token verification.
+### Publishing to the Solana dApp Store
+
+URL: https://three.ws/docs/seeker-publishing
+
+The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.
+
+### three.ws on iOS
+
+URL: https://three.ws/docs/ios-app
+
+What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission prompts, and an offline screen that recovers on its own.
+
### Docs · Money Flow Map
URL: https://three.ws/docs/money-flow-map
diff --git a/public/llms.txt b/public/llms.txt
index ca7f614db..a138b0a78 100644
--- a/public/llms.txt
+++ b/public/llms.txt
@@ -434,6 +434,8 @@ Docs, tutorials, and reference.
- [Docs · Circulation Engine](https://three.ws/docs/circulation-engine): The autonomous agent-to-agent activity loop: a pool of real platform agents tipping, paying, trading, and launching with one another.
- [Docs · Agent Monitor](https://three.ws/docs/monitor): What each panel on /monitor reads and how often, every control on the board, how a failed panel degrades alone, and how to add a panel of your own.
- [three.ws on Solana Seeker](https://three.ws/docs/seeker-app): What the Seeker app adds on top of the website: Seed Vault sign-in, share-sheet capture, an offline shell, home-screen shortcuts, and Seeker Genesis Token verification.
+- [Publishing to the Solana dApp Store](https://three.ws/docs/seeker-publishing): The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.
+- [three.ws on iOS](https://three.ws/docs/ios-app): What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission prompts, and an offline screen that recovers on its own.
- [Docs · Money Flow Map](https://three.ws/docs/money-flow-map): How /flow builds the agent economy topology from settled on-chain transfers: the two edge sources, the privacy gate on counterparties, what source/hub/relay/sink mean, and how the stuck-capital number is computed.
- [Docs · Money Feed](https://three.ws/docs/money-feed): The surfaces that show real value moving through three.ws: the live ticker, the custody-spend ledger, and the economy volume dashboard.
- [Docs · Reputation System](https://three.ws/docs/reputation): Leave and read permanent, on-chain reviews for any registered agent via the UI, SDK, or contract.
diff --git a/public/sitemap/index.html b/public/sitemap/index.html
index 321a4f800..3c02797b8 100644
--- a/public/sitemap/index.html
+++ b/public/sitemap/index.html
@@ -83,7 +83,7 @@
<main class="sm-wrap">
<div class="sm-hero">
<h1>Sitemap</h1>
- <p>All 840 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>
+ <p>All 842 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>
<div class="sm-formats">
<a href="/sitemap.xml"><code>sitemap.xml</code> · for search engines</a>
<a href="/llms.txt"><code>llms.txt</code> · for AI agents</a>
@@ -95,7 +95,7 @@
</div>
<div class="sm-filter">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m21 21-4.3-4.3"/></svg>
- <input id="sm-filter-input" type="search" placeholder="Filter 840 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />
+ <input id="sm-filter-input" type="search" placeholder="Filter 842 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />
<kbd aria-hidden="true">/</kbd>
</div>
<p class="sm-filter-count" id="sm-filter-count" role="status" aria-live="polite"></p>
@@ -111,6 +111,22 @@
<span class="sm-desc">A 3D companion that delivers your important messages in person. Connect your own Telegram bot, calendar, inbox, or phone, give each contact their own avatar and voice, and hear only what clears your bar.</span>
</a>
</li>
+ <li>
+ <a href="/docs/seeker-publishing">
+ <span class="sm-new-date">Aug 28, 2026</span>
+ <span class="sm-title">Publishing to the Solana dApp Store</span>
+ <span class="sm-path">/docs/seeker-publishing</span>
+ <span class="sm-desc">The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.</span>
+ </a>
+ </li>
+ <li>
+ <a href="/docs/ios-app">
+ <span class="sm-new-date">Aug 28, 2026</span>
+ <span class="sm-title">three.ws on iOS</span>
+ <span class="sm-path">/docs/ios-app</span>
+ <span class="sm-desc">What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission prompts, and an offline screen that recovers on its own.</span>
+ </a>
+ </li>
<li>
<a href="/docs/feedback">
<span class="sm-new-date">Aug 28, 2026</span>
@@ -159,22 +175,6 @@
<span class="sm-desc">The founding three.ws roundup: a week-by-week record of everything shipped from the first commit on 2026-04-14 through 2026-08-25, with every launch, partnership, announcement, and where $THREE fits.</span>
</a>
</li>
- <li>
- <a href="/docs/three-thesis">
- <span class="sm-new-date">Aug 25, 2026</span>
- <span class="sm-title">Docs · The $THREE thesis</span>
- <span class="sm-path">/docs/three-thesis</span>
- <span class="sm-desc">The long-form case for $THREE: what three.ws is, every utility and sink the token has, how platform revenue routes into buybacks, where it trades and is verified, the ecosystem footprint, the roadmap, and every risk the platform documents about itself.</span>
- </a>
- </li>
- <li>
- <a href="/pill">
- <span class="sm-new-date">Aug 24, 2026</span>
- <span class="sm-title">The pump.fun Pill, Rigged</span>
- <span class="sm-path">/pill</span>
- <span class="sm-desc">three.ws is verified on pump.fun. Their pill mascot, rigged with a 52-bone skeleton and six hand-built clips, on a stage you can walk it around in the browser.</span>
- </a>
- </li>
</ul>
</section>
<nav class="sm-toc" aria-label="Sections">
@@ -2283,7 +2283,7 @@
<section class="sm-section" id="learn">
<header>
- <h2>Learn<span class="sm-count" data-count>378</span></h2>
+ <h2>Learn<span class="sm-count" data-count>380</span></h2>
<p class="sm-section-desc">Docs, tutorials, and reference.</p>
</header>
<ul class="sm-list">
@@ -2966,6 +2966,20 @@
<span class="sm-desc">What the Seeker app adds on top of the website: Seed Vault sign-in, share-sheet capture, an offline shell, home-screen shortcuts, and Seeker Genesis Token verification.</span>
</a>
</li>
+ <li>
+ <a href="/docs/seeker-publishing">
+ <span class="sm-title">Publishing to the Solana dApp Store</span>
+ <span class="sm-path">/docs/seeker-publishing</span>
+ <span class="sm-desc">The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.</span>
+ </a>
+ </li>
+ <li>
+ <a href="/docs/ios-app">
+ <span class="sm-title">three.ws on iOS</span>
+ <span class="sm-path">/docs/ios-app</span>
+ <span class="sm-desc">What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission prompts, and an offline screen that recovers on its own.</span>
+ </a>
+ </li>
<li>
<a href="/docs/money-flow-map">
<span class="sm-title">Docs · Money Flow Map</span>
diff --git a/solana-mobile/README.md b/solana-mobile/README.md
index 63ef2b87e..d310724c8 100644
--- a/solana-mobile/README.md
+++ b/solana-mobile/README.md
@@ -61,6 +61,9 @@ Details: `docs/INTEGRATION.md`.
## Release pipeline
+The full runbook, including the Publisher Portal steps the owner does once, is [docs/seeker-publishing.md](../docs/seeker-publishing.md). The short version:
+
+
Publishing is Publisher Portal backed (dapp-store-cli 1.0, May 2026). The publisher profile, KYC, the App NFT, and the listing live in <https://publish.solanamobile.com>; the CLI only uploads one signed APK per release and the portal matches it to the app by package name (`ws.three.app`).
```bash
diff --git a/solana-mobile/docs/CHECKLIST.md b/solana-mobile/docs/CHECKLIST.md
index 257265400..f27de15c1 100644
--- a/solana-mobile/docs/CHECKLIST.md
+++ b/solana-mobile/docs/CHECKLIST.md
@@ -8,9 +8,9 @@ Work top-to-bottom. Do not submit until every box is checked. A date after a box
- [x] `/pwa-192x192.png`, `/pwa-512x512.png`, and `/pwa-icon.svg` return 200 with the right image type. (verified 2026-08-27)
- [x] The three TWA shortcuts resolve: `/create`, `/marketplace`, `/my-agents` all return 200. (verified 2026-08-27; `/my-agents` replaced the public `/agents` index)
- [x] 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)
-- [x] Service worker registered (`vite-plugin-pwa` emits `/registerSW.js`). (verified 2026-08-10)
+- [x] 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` (`/?utm_source=seeker_app`) renders without console errors on the device.
+- [x] `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)
@@ -18,24 +18,25 @@ Work top-to-bottom. Do not submit until every box is checked. A date after a box
- [x] `public/.well-known/assetlinks.json` contains the real fingerprint (no `{{RELEASE_SHA256}}` placeholder) and is on `main`. (2026-08-10)
- [x] `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)
- [x] 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 site still read `max-age=86400` on 2026-08-28 even though the server default is `max-age=3600`: the `/.well-known/(.*)` route in `vercel.json` sets its own header, and `server/index.mjs` only applies its default when no earlier layer set one. That route was changed to `max-age=3600` on 2026-08-28; confirm on the live site after the next deploy.
+- [x] `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
- [x] 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.
- [x] `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)
- [x] `apksigner verify --print-certs` prints the SHA-256 that is in `assetlinks.json`. (verified 2026-08-27: `98:0A:1A:AB:...:11:13:D7`)
-- [x] APK installs and launches on Android 14 (Pixel 7 emulator, 2026-08-27). Full-screen without the address bar needs Digital Asset Links for the NEW fingerprint, which go live with the next deploy; until then Chrome shows a custom-tab bar, by design.
+- [x] 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).
- [x] 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.
-- [x] The Android share sheet target is registered (`shareTarget`, MIME types only) and an `ACTION_SEND` image intent opens the app (2026-08-27, emulator).
+- [x] 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
- [x] 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)
- [x] `solana-mobile/src/index.js` is imported from the app entry points (`src/wallet.js`, `src/game/play-auth.js`). (verified 2026-08-27)
- [x] 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)
-- [ ] On a real Seeker, `window.threeWsWallet` is defined and `isSolanaMobileTwa()` returns `true` inside the TWA.
+- [x] `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.
+- [x] 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.
@@ -82,7 +83,8 @@ Work top-to-bottom. Do not submit until every box is checked. A date after a box
- [ ] 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.
+- [ ] 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 screenshots captured per `docs/ASSETS.md` and dropped into `publish/media/`.
## 10. Post-submission