@odatano/nightgate v0.11.0

@odatano/nightgate 0.11.0 (2026-07-28)

• Fully public zero-config: only network set means public RPC + hosted
  indexer + in-process (wasm) proving, no local Docker at all. Configuring a
  proof-server URL selects server proving automatically;
  NIGHTGATE_PROVING_MODE=server|wasm overrides.
• In-process proving for EVERYTHING: wallet circuits via the SDK WASM prover,
  contract circuits via NIGHTGATE's own srv/midnight/wasm-proof-provider.ts
  (zkir over the contract's local key material; midnight-js ships no
  in-process ProofProvider).
• sendNight sends custom tokens: optional tokenTypeHex (64 hex,
  lowercased), shielded or unshielded by receiver address; new
  contracts/shielded-token test contract to exercise the zswap circuits.

Live proof (preprod, dead proof-server URL http://127.0.0.1:9999)

NIGHT send        00474d79…  (55.9 s cold)
counter deploy    37bb15aa…  (79.3 s)   increment  d58e4420…  (76.3 s)
0.31-mint         56892f3e…  (~170 s)   both compiler generations pass local zkir
zswap self-send   00e9065c…  (176.1 s cold incl. 11 MB spend-key download)

Notes

• wasm caveats (reference.md): standard-circuit keys from Midnight's S3 at
  runtime (no integrity check, in-memory cache per process), seconds of CPU
  per proof. Production runs a proof server; configuring its URL is enough.
• New harnesses: wasm-proving:e2e / wasm-contract:e2e / wasm-zswap:e2e.
  Older consumer DBs need scripts/apply-schema-delta.mjs once (0.10.1
  column WalletSessions.accountIndex).