Latch — deployment and integration handoff

Updated: 26 October 2026. Product: Latch / $LATCH. All product-facing text is English.

1. What is being shipped

A static browser application, not a backend service or deployed privacy protocol. The interactive Three.js room mounts a shared application inside its monitor. Swap, Send, Bridge and Vault are isolated tabs; MCP and Mesh are marked Coming soon.

Important: the bridge currently subtracts a fixed 0.50 USDC reference fee. This is not a live bridge quote. Local vault units are test SOL and hold no deposited assets. Deploying the frontend does not activate swaps, transfers, bridging or private custody.

2. Local startup

No package installation or application build is required. There is no package.json. Serve the contents of dist/ over HTTP for visual development:

python3 -m http.server 8080 --directory dist

Open http://localhost:8080/. Localhost is a secure context for browser cryptography. Use HTTPS on a public hostname; public plain HTTP does not provide the secure context needed by the vault/clipboard features. Modern browsers with WebGL, ES modules, import maps, BigInt and Web Crypto are required.

Every fresh load starts at the first monitor scene. Enter Latch leads to the press-and-hold OS upgrade before the application. Product tabs are selected inside the active workspace.

3. Static deployment

Upload dist/ as the web root. Preserve its file structure and query strings. There is no Node process, database, backend secret, server wallet or runtime environment file in this frontend.

Serve JavaScript as JavaScript, CSS as CSS, and keep binary GLB/font/audio files intact. Return 404 for missing assets instead of rewriting every request to index.html. /work/ is a real documentation directory. Keep index.html and application JS/CSS revalidatable; assets use existing filenames and module query-version suffixes.

The current server deployment uses Nginx, release directories under /var/www/latch/releases/ and a current symlink. The selected web root is /var/www/latch/current. Validate Nginx configuration before reloading. Roll back by repointing current to the previous release. Keep at least one previous release.

The root .openai/hosting.json belongs to the existing Sites publication; it is not required by Nginx and must not be copied into the public web root.

4. LATCH configuration

Edit dist/latch-tokens.js:

LATCH: { mint: null, decimals: null }

Replace both nulls with the verified Solana mint string and its actual on-chain decimal count. Do not guess decimals or select another token by ticker. A mint alone does not guarantee a Raydium route; confirm liquidity for both directions and intended trade sizes. Missing configuration currently displays a configuration-pending state and never invents a price.

SOL uses the wrapped SOL routing mint with 9 decimals; USDC uses its configured mainnet mint with 6 decimals. atomicAmount() converts input with BigInt and rejects excess fractional precision. Review supported assets in the agent parser and Send selector when changing token support.

5. Quotes and external dependencies

The browser calls Raydium's public Trade API directly:

GET https://transaction-v1.raydium.io/compute/swap-base-in

Parameters: inputMint, outputMint, integer atomic amount, slippageBps and txVersion=V0. No wallet address or secret is sent by quote requests. Raydium receives the selected pair, amount, slippage and normal network metadata. There is no API key. The frontend validates the returned pair, input amount and positive output; errors and missing routes do not fall back to fixed rates.

Input changes are debounced by 450 ms and cancel previous requests. Timeout: 12 seconds. Quote lifetime: 25 seconds. Successful quotes refresh approximately every 20–22 seconds while the swap tab and document are active. Failed or expired quotes require retry. Review is blocked without a fresh quote. Downloaded route plans are not signed transactions or receipts.

Dependencies loaded externally include Three.js 0.170.0 and addons from jsDelivr, Google Fonts, and Raydium quotes. Preserve their access in any CSP/network policy or vendor them before locking down outbound resources. If adding an authenticated API/model provider, keep server keys on a backend; do not place them in dist or browser storage.

Official quote integration reference: https://github.com/raydium-io/raydium-sdk-V2-demo/blob/master/src/api/swap.ts

6. Agent contract

parseCommand(text, previousDraft) in dist/latch-intents.js returns an error code or a draft with kind, parameters and a needs array. English and Russian input recognition exists; the interface and generated replies are English. The local parser validates preparation commands returned by the live server-backed agent. Conversation is sent for server-side inference; do not share secrets.

Examples: Swap 1 SOL to USDC, Swap 1 SOL to LATCH, Send 0.1 SOL to [public address], Bridge 100 USDC from Ethereum to Solana to [public address], Create a 0.1 SOL note, balance.

The UI uses window.LatchWorkspace to select tabs, populate forms, review plans and generate local notes. Each action still requires its relevant explicit review/action button. The balance command reports local notes only, not a wallet or private on-chain balance. Commands containing explicit seed/private-key terminology are refused; this is not a general secret-detection guarantee. Conversation state is in memory and is shared across tabs.

7. Wallet and vault boundaries

Wallet connection requests a public address from an installed Phantom/Solflare-compatible provider. No transaction signing or broadcasting code is connected.

dist/sola-core.js generates a 256-bit random secret with crypto.getRandomValues and computes a SHA-256 commitment. The commitment tag remains sola-local-v1 for file compatibility. Newly generated notes use network: solana-local; imports also accept older solana-devnet note files. Those legacy internal identifiers are not network connectivity or current branding.

Local notes are not zero-knowledge proofs and carry no deposited assets. There is no pool program, prover, custody account or durable nullifier set. The in-memory note/spent registry resets on reload. Importing a note verifies its JSON/commitment and can mark it redeemed for the current session; it does not transfer assets or import a persistent balance. Secrets are masked until revealed and leave the browser only through explicit copy/export. No security audit is claimed.

8. Code map

main.js / os.js / crt-screen.js: scene, monitor transitions and mount lifecycle. Preserve gate/camera events when integrating the app.

sola-products.js: shared application shell, forms, review, wallet address and local note UI.

latch-tokens.js: mint configuration, exact input units and live quote transport.

latch-intents.js / latch-agent.js: command planner and shared panel.

latch-avatar.js / latch-processes.js / latch-ascii.js: decorative ASCII avatar, separate process diagrams and backdrop.

latch-mesh.js: conceptual network globe and Mesh tab.

sola-monochrome.css / latch-agent.css: final workspace styling overrides.

assets/: scene models, textures, fonts, audio and brand files. Do not rename dependency paths casually.

work/index.html: public technical documentation.

Animation states and Mesh nodes are visualizations, not transaction progress or live infrastructure telemetry. Social icons are intentionally non-navigating until official GitHub/X URLs are supplied. The production symbol is assets/brand/latch-symbol.svg: a connected keyhole-shaped agent, white body and cyan eyes.

9. Checks and release acceptance

Use a current Node runtime (tested with the bundled current runtime):

node test-sola.mjs
node test-latch-intents.mjs
node --check dist/sola-products.js
node --check dist/latch-agent.js
node --check dist/latch-tokens.js

Browser release checks: load / and /#swap; verify scene/monitor transitions, all six tabs, live SOL/USDC quotes and pair reversal, missing LATCH configuration, expired/failed quote behavior, local note export/import and masked secrets, English agent replies, distinct process animations, social icon placeholders and /work/. Check narrow/mobile layouts on the deployment host. A successful quote is not an end-to-end swap test.

Before enabling real asset movement, developers must implement and test transaction review, simulation, user signing, submission, confirmation, error recovery, provider-specific fees and privacy guarantees against actual receipts. Select and verify the privacy architecture before making protocol/security claims.

10. Production operations

Primary host: latchprotocol.fun. Nginx serves /var/www/latch/current through /etc/nginx/sites-available/latch. Certificate renewal uses Certbot webroot validation and the existing certbot.timer, with a validated Nginx reload hook.

The www hostname has separate DNS pointing elsewhere and is not included in this deployment. See the downloadable handoff for exact release, certificate, verification and rollback paths.

Live agent service

Latch Agent now uses a server-side inference gateway. Conversation is sent for processing; the browser never receives the API key. Commands are validated locally and can only prepare forms. Signing and transaction execution remain unconnected.

A persistent server ledger reserves request costs against an overall $20 application budget. It survives restarts. This is a spending cap, not a provider-account top-up. See the downloadable handoff for service, key storage, budget, rate limits and operations.