Orb independent client - Monad TESTNET 10143

This public package contains no user keys, account database or environment files.
Extract it, run "node verify-client.mjs", then "node serve.mjs" (Node >=22.13).
Open http://127.0.0.1:8080. For sharing, serve the entire directory from ANY folder
on an HTTPS static host, with JavaScript/WASM MIME types and worker support.
Do not open index.html as file://. Use a browser wallet on testnet 10143.

Community membership, ownership, scoped Arena moves and native-MON mission escrow
use the bundled verified contracts directly through Monad RPC. Capsules carry public
channel blueprints, an EOA owner's signature and an IPFS content ID. Import a saved
JSON to verify the signature/CID; RPC is needed to check the CURRENT onchain owner
and metadata. Ownership transfer or a metadata update can invalidate current status.
No transaction is signed without the connected wallet's action.

ORB contributions is the regular ORB-funded mission product; MON escrow is separate.
The read-only verifier checks mission/token bytecode, a selected wallet's contribution
and optional withdrawal receipt without Orb login/API. Links bind the expected
contract. A payout must match the wallet, withdraw() call and successful Withdrawn
event at the stated block. It may combine mission rewards and refunds; sponsor
approval is not objective work-quality proof. RPC responses are still trusted.
Normal Orb community profiles can associate an independent public identity after
both hosted-owner and current onchain-owner checks. This imports no chat history,
memberships, roles or private channel permissions into the independent registry.

Portable chat is a separate TESTNET inbox and encrypted personal archive. Reconnect
the SAME wallet, enable/recover its chat key and read confirmed history from Monad
without Orb API. Only the public key and sealed backup are published; the private
recovery signature stays on the device. Ciphertext remains permanent, and wallet
traffic is public. Names/text copies are historical, not current memberships or
proof of someone else's authorship. Attachments/calls and unreadable legacy texts
are not copied. Existing hosted chat keys remain unchanged.

In Orb, explicit consent permits preparation of accessible text for your wallet.
Only ciphertext and chat-scoped signatures enter the authenticated outbox. Pending
parts need confirmed receipts. Six-hour preparation runs only while the panel is
visible and unlocked with an active session; a configured keeper can publish signed
parts later. Delegates cannot spend wallet funds. Sessions expire within 24 hours
and can be revoked. DMs need both registered keys; the independent encrypted group
channel requires current members' keys (20-member pilot). No cryptographic audit
or forward-secrecy guarantee is claimed.

Optional lazy Privy recovery uses the ORIGINAL Orb app on an authorized origin.
Configure allowed origins/app clients; an unrelated app/email login does not give
the same embedded wallet. Privy authentication, wallet recovery and MFA still apply.
Global-wallet access for arbitrary clients is not configured. A browser wallet may
connect the same exported wallet. Read docs/orb-portable-chat.md in the source repo
for the protocol, receipt evidence, keeper setup and limits.

IPFS files must be imported/pinned by independent operators; a CID alone does not
keep a file online. XMTP messages use its separate DEV network and require wallet
identity signing; its browser database is not encrypted at rest. Production XMTP
needs its own gateway/fee configuration. Hosted live permissions/media are not migrated.
Optional Orb IPFS pinning needs an Orb session and its configured API. It is not
needed to export CARs or use any core independent feature.

Integrity: bundle-manifest.json lists SHA-256 for each packaged file. client.sha256
on the download page checks the ZIP. Checksums detect changes relative to a trusted
copy; they do not establish publisher identity or replace a source/security review.
The artifacts and deployment record are PUBLIC configuration, never private keys.
Tokens have no promised value. No mainnet transactions are enabled.

Scalable archive (October 4): the Backup panel now prefers replicated encrypted
raw CID blocks and small paged Monad references. The original recovery key is
preserved. Open the archive catalog, choose a conversation, and read four blocks
at a time; switching pages replaces the decrypted page. Configure trusted HTTPS
gateway templates with {cid} or {digest}. Invalid/missing replicas are rejected.
The bundled configuration includes localhost for the development preview: it
does not claim public IPFS pins exist. Production requires independent live pins
and public read gateways; a recovery key cannot recreate lost files.
Shared independent community archives use epoch-specific per-wallet grants and
one shared content block. Hosted private channel permissions/history are not
silently imported into that public registry. Consult docs/orb-chat-scale.md.
