Conversation
Implements the TrUAPI PeerTransport service in the browser over
WebTransport, directly to JAM validators, for PolkaVM apps whose App
manifest v2 declares capabilities.network.jam = { genesis }.
The grant is derived only from the resolved, verified manifest, covers
exactly that genesis, is execution-local and is closed when the app
stops, fails or relaunches. Trait-21 frames are answered by the local
session; every other frame, including the handshake reply the guest
sees, still comes from the authenticated host port. Without the
capability nothing changes. The in-app menu lists the grant and its
limits.
Vendors @parity/truapi and @parity/truapi-host 0.20.0 from
host-rust-core feat/pvm-peer-transport fc2df9d3 (#1010), the host layer
on top of #540; the web wasm keeps wasm-signing-host as before.
Picks up PeerTransport's move to wire trait 23 (clear of Contacts, Game and Profile).
# Conflicts: # vendor/truapi-host.lock.json # vendor/truapi-host/dist/wasm/web/truapi_server.d.ts # vendor/truapi-host/dist/wasm/web/truapi_server.js # vendor/truapi-host/dist/wasm/web/truapi_server_bg.wasm # vendor/truapi-host/dist/wasm/web/truapi_server_bg.wasm.br # vendor/truapi-host/dist/wasm/web/truapi_server_bg.wasm.d.ts # vendor/truapi-host/dist/wasm/web/truapi_server_bg.wasm.gz # vendor/truapi/dist/generated/client.d.ts # vendor/truapi/dist/generated/client.js # vendor/truapi/dist/generated/internal-client.d.ts # vendor/truapi/dist/generated/internal-client.js # vendor/truapi/dist/generated/wire-decode.js # vendor/truapi/dist/generated/wire-table.d.ts # vendor/truapi/dist/generated/wire-table.js # vendor/truapi/dist/playground/codegen/truapi-dts.d.ts # vendor/truapi/dist/playground/codegen/truapi-dts.js
Contributor
Bundle Size ReportWarning Bundle budget exceeded — not a blocker, but please confirm the regression is intentional.
Eager path (module entry + modulepreloaded chunks):
Chunks over 500 KB:
All files
Commit: 4f2b6f1 |
replghost
had a problem deploying
to
paseo.fyi
September 26, 2026 23:11 — with 
GitHub Actions
Failure
GitHub Actions
Failure
Contributor
⚡ Performance ReportCold StartOverall: ⚪ unchanged | p50: 11.30s → 10.92s (-3.3%) | p95: 14.48s → 12.12s (-16.3%) | Mann-Whitney: z=0.29 not significant Phase breakdown
Warm StartOverall: 🔴 regressed | p50: 477ms → 7.65s (+1502.9%) | p95: 518ms → 7.92s (+1429.0%) | Mann-Whitney: z=4.40 ✅ significant Phase breakdown
Lukewarm Start (different site, same session)Overall: 🔴 regressed | p50: 11.87s → 14.11s (+18.8%) | p95: 19.36s → 20.06s (+3.6%) | Mann-Whitney: z=2.51 ✅ significant Phase breakdown
Commit: 4f2b6f1 | Outliers (>2x best) discarded before stats |
PeerTransport access is now RemotePermission::JamPeers { genesis }, a
runtime permission like ChainSubmit, instead of an App-manifest
capability. capabilities.network is no longer parsed and no grant is
derived from the manifest.
Every PolkaVM application gets an execution-local PeerTransport
session. Its first dial of a JAM network sends
permissions.request_remote_permission(JamPeers { genesis }) over the
authenticated host port with a random request id of the sandbox's own,
and the sandbox consumes the reply; the guest never sees it. The core
checks the product's stored decision, prompts while it is undetermined
and persists the answer per product and genesis. The session asks once
per genesis; a refusal answers NotGranted and opens no WebTransport. An
app that never dials is never asked. Frame routing reads the wire
header only.
The host prompt asks "Allow <product> to connect to JAM network
0x…… (read-only peer access, no accounts or signing)?" with Deny,
Always allow and Allow once. The in-app "Network access" menu lists the
networks granted to the running session.
Vendors @parity/truapi and @parity/truapi-host 0.20.0 from
host-rust-core feat/pvm-peer-transport 4f5a7504 (#1010).
Picks up the bounded 10 s dial (prompt included) and CANCEL handling in the browser PeerTransport session. The web wasm is byte-identical.
replghost
had a problem deploying
to
paseo.fyi
September 27, 2026 14:17 — with
GitHub Actions
Failure
GitHub Actions
Failure
Follows paritytech/trinity-user-agents#1010 at 50284f97, which renames the TrUAPI service to JamPeerTransport because it is JAM-specific (JamPeers permission, jamnp-s ALPN, JAMNP-S identity and framing). Wire-identical: trait 23, methods 0..6, same SCALE layout, same JamPeers permission. The sandbox now imports @parity/truapi/jam-peer-transport (createJamPeerTransportSession, JamPeerTransportSession, JAM_PEER_TRANSPORT_*), and the vendored @parity/truapi and @parity/truapi-host are rebuilt from that commit.
Brings in the JamPeerTransport rename (#290 at 8980057). Only vendor/ conflicted; it is rebuilt from paritytech/trinity-user-agents#1011 (feat/jam-peer-transport-on-seity) at c85c26b6, the --no-ff merge of the renamed #1010. Wire-identical: trait 23, methods 0..6, JamPeers.
replghost
changed the title
…ce metrics for framebuffer apps
# Conflicts: # vendor/truapi-host.lock.json
# Conflicts: # vendor/truapi-host.lock.json # vendor/truapi-host/dist/wasm/testing/truapi_server.d.ts # vendor/truapi-host/dist/wasm/testing/truapi_server.js # vendor/truapi-host/dist/wasm/testing/truapi_server_bg.wasm # vendor/truapi-host/dist/wasm/testing/truapi_server_bg.wasm.d.ts # vendor/truapi-host/dist/wasm/web/truapi_server.d.ts # vendor/truapi-host/dist/wasm/web/truapi_server.js # vendor/truapi-host/dist/wasm/web/truapi_server_bg.wasm # vendor/truapi-host/dist/wasm/web/truapi_server_bg.wasm.d.ts # vendor/truapi/dist/generated/client.d.ts # vendor/truapi/dist/generated/client.js # vendor/truapi/dist/generated/internal-client.d.ts # vendor/truapi/dist/generated/internal-client.js # vendor/truapi/dist/playground/codegen/truapi-dts.d.ts # vendor/truapi/dist/playground/codegen/truapi-dts.js
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Current repair qualification — 2026-10-02
0efd81fdf91163b240a4e34a41d9b2349d3c9ffd. Prior main baseline:f4012c50c3400d1186c332ad2ae50298cefd153d.95d0c3242f173b22578d34f1fea03abfd3754789(jam). Complete matching SDK/host packages remain 0.23.0; no mixed or hand-patched Wasm bundle. Generated client bytes are unchanged. Production:wasm-signing-host; separate testing bundle:wasm-signing-host,test-host.1103910932941a1d57deb4b7278b40c22c1489bbd11c609e398dd4418922d850dist/generated/client.js79d8b4a1ec6c94af558cd7ad59e52aa4c8fb3c3634bb8dd3c0cb46126b4fab78c9e03bf25117f8ed6783bca1c52b624dd8c0e3306006ce82758b7874381e3a6c1d632066a6f170216925472c920c002efb9150413facd5b65b7fd57c51b7e044581737d50b36a0b86fc12406686ad007d1ea5ebce02c2d07e82d5be8469ed97bNative correction and causal limits
Bulletin mortal signatures now anchor to a finalized checkpoint, while nonce/runtime state comes from the freshest available signing snapshot. A checkpoint at least 64 blocks behind is rejected before broadcast. Regression coverage verifies the actual signature with a newer nonce and older finalized checkpoint, and the expiry boundary. Existing transaction retries/deadlines are unchanged; no chain error is suppressed. The affected test fixture uses
parking_lot::Mutex.The former Seity
Extrinsic marked as invalidrun used noncanonical best-block anchors, but retained evidence lacks the signed bytes and typed pool reason. Fork-sensitive mortality was a real correctness hazard; it is not claimed as the conclusively proved cause of that historical failure. Prior hosted Factory/Genesis timeout causes also remain unproved. No broker/readiness workaround, prewarming, extra retry, or timeout increase was added.Final exact-head hosted checks
Real-runtime local verification
All six consumers passed configured build, typecheck and lint. The later README-only formatting correction passed targeted Prettier checks and did not change runtime source or canonical native package bytes. Original full Wallet→Chat→Seity test sequences, without test retries, added waits, or prewarming:
0a24db4aa189adad7b93f9ff508c7949e39196ee301a235ba13248ef4281e9e3d859919fb6cfbe06d3dc8a41807c36b8bcdf001c47eccb9735305499Wallet's tested head is final. Chat and Seity tested heads precede documentation-only formatting merges; native/Wasm pins and runtime code are unchanged. Factory, Genesis-after-navigation and Submit passed on all three. These bounded passes do not establish the cause or elimination of the older hosted timeouts. Prior SharedWorker lifecycle, Chat/profile, Peer and JAM runtime proofs remain historical at their recorded heads; they were not all rerun on these artifacts.
Final hosted retest: failures remain
error; it is not evidence of a chain rejection. Retained traces include People-chain/local development sockets but do not expose the Asset Hub gateway WebSocket exchange, so these new failures do not establish an upstream or broker cause.paseo-bulletin-next-ipfs.polkadot.io. The zero-failure host-settings gate correctly failed.Doom: criterion corrected, backend matrix still unqualified
The user explicitly approved 35 FPS sustained over 30 seconds, with one frame of sampling-boundary tolerance:
frames + 1 >= elapsedMs * 35 / 1000. This replaces the instantaneousFPS >= 35sample; it is an acceptance-criterion change, not a runtime speedup. Runtime and displayed FPS are unchanged; raw samples are not rounded to force a pass. Update p95 <28.6ms, cold/warm first-frame limits <3,000/<1,000ms, audio and translation-cache checks remain. The revised official RPC benchmark passed once before the vendor replacement.The later isolated matrix used the rebuilt base pair at frontend
238ab5fa739788b2eb948ba1f807a1876edbacad, with fresh owned Chrome profiles and no concurrent builds/E2E:Distinct diagnostics found no presentation loss in a later instrumented 24-second shared-worker sample and observed a successful hidden RPC new-document reload. Neither diagnostic supersedes the failures or qualifies performance. No evidence-proved runtime fix, guest rebuild, speculative tuning, or further unchanged gate rerun was made. The original strict RPC failure and every new failure remain retained. Next causal capture must instrument the original early 30-second window and distinguish warm lifecycle states before proposing a runtime fix.
Retention and rollout boundary
Local verification used
paseo-next-v2, the pinned host-playground fixturef56294cea4430163bf16ec068844b1327441073c, and existing private QA identities. All three corrected sequences paired on their first existing setup attempt. A prior local launch failure and a misconfigured Previewnet-product run (34 passed, 20 skipped, 8 Chain/Contract failures) are retained separately, not presented as reproductions of the hosted Genesis timeout. Private traces/auth/signers were not published.The first repair heads also exposed a README formatting failure (corrected by documentation-only commits) and a PVM cache-unit-test 5,000ms timeout. No cache runtime/test change, limit increase, or causal claim was made for that isolated timeout. Older in-flight runs superseded by the formatting correction remain recorded as cancelled, not passed.
No PR merge, force push, deployment, environment approval, SDK/npm/product/guest publication, or rollback was performed by this repair. JAM remains JAM-TEST-INSTANCE, never JAM-PUBLIC-DEVNET. The user-owned
deploy: paseo.fyilabel is retained; repair-triggered deployment runs 36970790399 and 36971286469 were cancelled before deployment. The earlier rollout audit is retained below: an older workflow deployed56cea5d37577bf82684fb5c6b6e4ba81d2142938; this record does not claim live remained unchanged historically.Historical integration qualification (superseded; retained verbatim)
Current merged-main refresh and qualification — 2026-10-01
dcdef40499119183aed82a39f784ef740d494341; base:feat/chat-seity-profile. Includes merged mainf4012c50c3400d1186c332ad2ae50298cefd153dand fix: protocol iframe and SharedWorker chains on the pool, and every chain client recovers from halts #313. No separate/unmerged fix: protocol iframe and SharedWorker chains on the pool, and every chain client recovers from halts #313 boundary remains.7e65d2eb8d73b7db49ef1f3681377a0db8998db2, including native mainbda6ac518c8cc59319491b12e4e23b96777375fd. Complete canonical SDK/host artifact-generation pin:e51563a447a03666316c2f3e99e734866696b4cd. Later native changes are tests/docs/iOS-only, not SDK/Wasm inputs; the generation pin intentionally differs from the latest source head.web-wasm-signing-hostwithouttest-host, with testing Wasm separate. No hand-edited generated declarations or mixed variants. No package publication.1103910932941a1d57deb4b7278b40c22c1489bbd11c609e398dd4418922d850dist/generated/client.js(notdist/index.js)79d8b4a1ec6c94af558cd7ad59e52aa4c8fb3c3634bb8dd3c0cb46126b4fab7806f4b0798c02bb4ba17f346ca897b02a5943b30773c92c1f42eeec0f2460de3028e16236f7396fd188e7a2b8df98fe7d150957c3f5b3b21f2ba8b71d373e9439Stack and hosted qualification
Wallet → PVM → Chat → Seity; PVM → Peer; JAM contains both Seity and Peer. All updates used fresh-fetch ancestry checks and ordinary pushes. User worktrees, metadata and canonical repositories were preserved.
70845db96bdd21409310daeff5e471b74ab5a1c9.351e5d73fab803a0fd2a4007ce2d2557aebaff05.bb9ad3d8921c63cf62c98b9029289f458b1a67a2.b03e83616857f4e4745d479776dde43cdfa6267a.44ed4f830a2c8f86990e02fb061c802aa389b0bc.dcdef40499119183aed82a39f784ef740d494341.Exact-head hosted results: functional 91 passed, 3 skipped; E2E 42 passed, 20 skipped; 3 passed in the cold-start suite. Tests run.
Performance Tests runs the cold-start suite, not the strict Doom matrix below. Existing thresholds, retries, deadlines and skips were not relaxed. Native current-head Core CI has 22 passed jobs and 2 path-filter skips; full iOS application CI is not claimed for the latest native heads.
Local and actual-runtime evidence
main-refresh-terminal-verified-pvm.json/ screenshot.main-refresh-pvm-transport.json/ screenshot.0x10c123f02eb6df4c01397d797a112055be691883baa2e82f83b618ed6ce45e46. No TLS bypass or new published guest. Evidence:main-refresh-jam-pvm-live.jsonand screenshots; Seity encrypted-content evidence is separately scoped above the Chat layer.Strict Doom matrix — retained failure
Fresh isolated visible headless Chromium profiles; cold cache miss, real compiler, nonzero audio, and 360 frame updates for each backend. Warm reload uses a new document in the owned iframe: cache hit and zero translation. Gates remain FPS ≥35, p95 <28.6ms, cold first frame <3000ms, warm first frame <1000ms.
Evidence:
main-refresh-isolated-doom-{rpc-gateway,smoldot-direct,smoldot-shared-worker}.jsonand screenshots. Earlier hidden-tab and concurrent-QA failures remain recorded; no clock/rounding/threshold change or failure-only rerun was used to erase them.Other retained limits
Extrinsic marked as invalid). One UI call caused the existing two native broadcast attempts; both validated then invalidated. No matching included Submit was found in the inspected canonical block range. [INFERENCE] Noncanonical mortality anchors may explain invalidation, but the exact cause is unproved without the unretained signed extrinsic bytes. Evidence:main-refresh-seity-submit-diagnosis.json. Passing hosted E2E does not erase this local failure.main-refresh-seity-factory-diagnosis.json. No added retries, deadline changes, or unsupported cause claim.Rollout boundary
Not an all-green rollout qualification. The refreshed heads were not deployed, and this qualification granted no environment approval. No PR merge, SDK/npm publication, or guest/product publication was performed. JAM remains JAM-TEST-INSTANCE. All three refresh-triggered JAM Deploy runs were cancelled before rollout; latest final-head cancellation. Other branches have no deployment labels.
The live environment changed during qualification: older Deploy run 36945647296, attempt 3 was approved under GitHub account
replghost, explicitly checked out baseline56cea5d37577bf82684fb5c6b6e4ba81d2142938, and recorded deployment success at 2026-10-02 01:19:01 UTC. Its later published-product smoke failed. The operator/client/session behind that account is unproven; this qualification granted no approval and performed no rollback. The observed live content hash changed from4a7caf047fb7f350c1833039b93ba634698a47c56f051b8c7fc0525d4c59a5c8to5882695ee20df5d24a6ed2feb9e997f176fe27ecf4eafe742fabb39eba92885f; these are content hashes, not Git SHAs, and their exact byte-level mapping to a source commit is unproven.Earlier deployment authorizations/results below are historical evidence, not approval to deploy this refreshed stack.
Historical integration qualification (superseded; retained verbatim)
Current-main integration qualification (2026-10-01)
117ef1eb2928a470e65e48c05b5bf22e8ab29c02. Includes main74bb603e518ace149a846124f6e7353aca198c57, propagated through feat(wallet): add an opt-in debug-only browser test wallet #238 → feat(polkavm): run App Manifest v2 runtimes in Dotli #185 → feat(chat): restore separate Chat authority integration above PolkaVM #255 → feat(profile): show product-referenced Seity profiles in a host drawer #287 and feat(polkavm): run App Manifest v2 runtimes in Dotli #185 → feat(polkavm): JamPeerTransport over WebTransport for JAM apps (layer atop #185) #290, then combined in chore(deploy): Seity layer + JamPeerTransport (#287 + #290) #291. All six heads are published by normal ancestry-guarded pushes; no history rewrite.af087f734be4d65d9363e68e43bf134145ae0085; complete feature-specific artifacts, signing-only browser Wasm, and separate testing Wasm. Native base #540 CI and Peer #1010 CI are green. No npm or guest publication.117ef1eb2928a470e65e48c05b5bf22e8ab29c02(successful deployment and smoke, deployment ID6778272827). Hosted smoke passed 8/8 published products and 19/19 wallet-free capabilities. Independent fresh HTTPS Chromium sessions confirmed Build0.6.0 (117ef1e)and playable Doom with advancing frames/input/audio on smoldot-direct, RPC gateway, and an actual SharedWorker, with zero browser exceptions. All three screenshots and geometry checks show the 384 px frame meeting the 360 px debug panel without a gap. An actual retained productionc4a08e9session waited for consent, navigated exactly once after Reload, retained the URL plus localStorage/IndexedDB/product-cache markers, and resumed playable Doom on117ef1ewith an activated controlling worker, no waiting worker, and zero exceptions. This is an actual release upgrade, not a substituted worker-script test. Local JSON/screenshots are retained underdotli-community-worktrees/paseo-fixed-doom-*andpaseo-debug-fix-retained-*. No other environment was approved; no PR merge, force push, npm release, or on-chain guest publication.Earlier sections are historical implementation and qualification records.
Latest dependency refresh qualification (2026-09-30)
4c9e1a33f72a4fb179caeb8f2aba31d282790a38; normal merges and ancestry-guarded pushes only, no history rewrite.af087f734be4d65d9363e68e43bf134145ae0085. Feature-specific 0.23.0 client/host/WASM artifacts remain unchanged; this source pin is intentionally not relabeled as the refreshed upstream branch head.4c9e1a33f72a4fb179caeb8f2aba31d282790a38deployed only to paseo.fyi and passed 8/8 published products + 19/19 wallet-free TrUAPI capabilities: https://github.com/paritytech/dotli-community/actions/runs/36750639257. A real retained session waited for consent, reloaded exactly once, preserved URL/localStorage/IndexedDB, and rendered Doom on the final release. Fresh HTTPS SharedWorker Doom also compiled/rendered and accepted input with no page errors. No other environment was approved.Earlier implementation and qualification history follows; the versions and heads above describe this refresh.
Summary
Deployment integration for paseo.fyi: Seity (#287) plus JamPeerTransport (#290), with the combined host from paritytech/trinity-user-agents#1011. Feature implementations are reviewed in the parent PRs; this layer integrates their source and authoritative SDK artifacts.
Stack
main → #238 → #185 → #255 → #287 → this PR, with #290 merged in. The
deploy: paseo.fyilabel belongs here while the two feature branches remain separate. This layer is not intended to merge into #287; once #290 flows through the base, it can be closed and the deployment label returned.Artifacts
@parity/truapiand@parity/truapi-host: 0.23.0.af087f734be4d65d9363e68e43bf134145ae0085in host-rust-core#1011.vendor/truapi-host.lock.jsonrecords exact archive, generated-client, and WASM digests. The wallet bundle enableswasm-signing-host, nottest-host; the package also contains a separately built testing bundle.Startup and deployed smoke behavior
URL-selected protocol settings settle before wallet/debug initialization. Shared-mode writes drain before startup replaces the protocol iframe or reloads the page, so wallet initialization cannot remain attached to the discarded iframe.
PolkaVM execution defaults on for test environments (
paseo.fyi,paseo.li, previews, and localhost) and off for productiondot.li. Settings → Experimental → PolkaVM apps explicitly overrides either default; existing saved opt-outs and opt-ins remain authoritative. This is an execution gate, not build-time exclusion of runtime assets or Firebase-controlled eligibility. Product permissions remain separate from the execution setting.Testnet product smoke exercises fresh visits without opting in. On production
dot.li, the suite explicitly enables the runtime through Settings and Save & Apply first. Existing rendering, input, audio, and GPU assertions remain unchanged.The signed-out egui-chat smoke checks the demand-driven UI by cancelling its initial sign-in prompt, using Retry to request a fresh prompt, cancelling again, and checking redraw and resize. Game rendering, input, audio, and GPU assertions remain unchanged. Failed deployment scenarios retain traces and screenshots for three days.
Qualification
Current cached-host upgrade recovery
Deployed to paseo.fyi only at
1514e45dd0a4c9316525e4c313e2962dfcb4a519. The deployment and Quality Gate passed. Hosted smoke passed 8/8 published PolkaVM products and 19/19 wallet-free TrUAPI capabilities. Native/SDK artifacts and source pins are unchanged.The generated host worker probes each open host's sandbox-contract version. Legacy, incompatible, or nonresponsive hosts navigate to the same URL after the new shell is installed; matching hosts retain the normal update prompt. Strict sandbox validation remains intact. Persistent host storage is not cleared; ordinary reload semantics still restart in-memory app state and credentialless iframe storage.
Independent retained-session verification started with an actual service-worker-cached live Doom host at
76eb846e, then observed exactly one automatic navigation to1514e45d, retained localStorage and IndexedDB markers, an activated controlling worker with no waiting update, and Doom rendering afterward. The isolated browser was closed and its temporary profile removed. A separate local production-built v4-to-v5 migration also rendered the real Doom guest and retained host storage.Both new upgrade regressions passed in CI: legacy automatic recovery with persistent-data preservation, and compatible-version updates waiting for user confirmation. Their gate permits neither failures nor skips. Unit, E2E, static analysis, dependency audit, bundle size, performance, and secret scanning checks passed.
Qualification limit: the broader functional run recorded 47 passed, 2 failed, 3 skipped; its existing threshold still passed. The failures were the warm-cache URL-hygiene readiness timeout and RPC-gateway resolution timeout, not the new upgrade regressions. A focused local replay of the unchanged warm-cache test against a metrics-enabled build passed in 1.8 minutes; this does not erase the CI failures or establish their root cause.
Previous testnet-default-on release
Previously qualified and deployed head:
76eb846e06713679891c6e0cc17a65919909eced. Previous test run, including unit, functional, and live E2E, static analysis, dependency audit, bundle size, performance, and secret scanning. The paseo.fyi deployment passes its Quality Gate, production build, identity-proxy smoke, and hosted product/capability smoke.Hosted smoke output records 8/8 published PolkaVM products without a Settings opt-in and 19/19 wallet-free TrUAPI capabilities passing. Independent isolated Chromium observed the exact deployed release, a fresh PolkaVM switch ON, sandbox gate
1, and the published Doom guest running with the compiler backend (32 rendered frames). A separate context with an existing saved0remained disabled before and after reload. Browser contexts were closed afterward.Production-built hostname checks also verified fresh
dot.lidefaults OFF, an explicit saved production opt-in remains ON after reload, and a saved testnet opt-out remains OFF. Those checks used locally served production assets under real hostnames with Paseo network configuration; they do not claim a production-chain deployment.The default-policy change preserves the Node-safe config boundary by passing
SITE_IDat browser call sites. New CI advisories were resolved by updating existingfast-uriandbrace-expansionoverrides to 3.1.8 and ^5.0.11; the SDK artifacts and source pins are unchanged.Previous refresh qualification
Previously qualified and deployed head:
032e97128983570eac9c32d6cd9dd8a41d181bca.Previous refresh checks pass, including unit, functional, and live E2E, static analysis, bundle-size, dependency-audit, performance, and full-history secret scanning. The paseo.fyi deployment also passes its Quality Gate, production build, identity-proxy smoke, and hosted product/capability smoke.
The real hosted output records 8/8 published PolkaVM product scenarios and all 19 wallet-free TrUAPI capability checks passing at this head. Independent fresh, isolated Chromium verification observed release
032e97128983570eac9c32d6cd9dd8a41d181bcaand passed feature discovery, JSON storage round-trip, and live chain-genesis lookup against the published Host Playground. The returned genesis was0x4349b00e54897e21196fd331015fc5be0f14e118beb0375ed2bb1793737bb57a. The browser/context was closed afterward.Artifact and release boundary
The user explicitly selected Deploy new sharing APIs to experimental paseo.fyi. The final artifacts pin
af087f734be4d65d9363e68e43bf134145ae0085, incorporating the qualified Chat/Profile parent sources rather than retaining the older refresh source08a08fbd921b56fd3ce36f6db3aad6f993bba784. Client/host archives were packed from canonical generated and compiled outputs, with matching wallet and testing WASM; exact archive/client/WASM digests are recorded in the lock. The generated client remains byte-identical to the intermediate sharing build, while the wallet runtime was refreshed.Both packages still say 0.23.0, but the generated client declares TrUAPI version 3, Profile
disclose/presentContactV2 andplaceContactAvatarsV3, includingChatApps,App, andContactsaudiences and opaque-handle selection. Browser integration includes audience-wide consent and encrypted wallet/chain-scopedProfilePersonalReferencesReceivedstorage. These are explicitly selected runtime-contract changes, not a browser-only refresh.The intermediate deployment run at
f46219daf8d1957c4f3cb2c5857a4202d33d735adeployed successfully and passed 19/19 capabilities, but all eight product scenarios failed at the default-off PolkaVM gate. The smoke setup now performs the real Settings opt-in; no production gate or existing product assertion was weakened. The passing final run above supersedes that failed qualification.Historical evidence and limits
The earlier successful deployment at
57aaf948a7b9d9fb6f35b9a731ad9cad9856a859, using host source08a08fbd921b56fd3ce36f6db3aad6f993bba784, also passed 8/8 products and 19/19 wallet-free capabilities. Its previously recorded independent fresh-context Chromium verification observed that exact release and passed feature discovery, JSON storage round-trip, and live chain-genesis lookup. That evidence remains historical and is not reassigned to a newer head.Earlier local production-origin browser execution passed all 19 capabilities, shared-backend persistence, and a URL-triggered backend reload. The historical macOS product run passed 4/8 because pointer-capture/WebGPU checks were unavailable there; the final hosted Ubuntu run passes all eight.
These smoke results do not qualify a live Profile/Contacts/avatar-sharing scenario, a live own-profile/avatar fetch, or a new JAM-validator transport trial. No wallet creation, funding, payment, or on-device Chat message was performed for this deployment qualification. The earlier malformed-reference Profile smoke remains limited to that rejection path.
After pulling local-file SDK dependencies, use
bun install --force --frozen-lockfileto replace Bun's cached packages. SDK provenance is the exact source and digests in the lock, not the unchanged package version.The public resolver fixture exemption still matches only its exact value and path; changed values and the same value elsewhere remain detectable. Only the explicitly selected environment deployments were approved; no PR approval or merge was performed.