Appearance
Gateway Artifacts
Kehto hosts such as Paja load napplets through content verification:
- Build a self-contained
dist/index.htmland signed.nip5a-manifest.json. - Resolve the manifest from the relay simulation and verify its signature.
- Fetch the artifact by its
xhash from Blossom and verify its bytes. - Bind the iframe Window to
(dTag, aggregateHash)before execution. The existing field name carries the current artifact hash, or a legacy aggregate hash. - Inject the runtime namespace and CSP outside signed bytes, then assign
srcdocwithsandbox="allow-scripts".
Gateway routes remain debugging/acceleration surfaces. Neither their metadata nor their bytes are trusted. Legacy path/aggregate events share the same verified loader through a separate compatibility adapter. Use pnpm audit:csp to check built napplet artifacts and event migration for the schema boundary.