Skip to content

Releases: ODATANO/NIGHTGATE

NIGHTGATE v0.3.0

29 May 21:55
1a566b4

Choose a tag to compare

@odatano/nightgate 0.3.0

0.3.0 adds a full transaction-submission layer on top, so the plugin now both reads Midnight
chain data and writes to it via Compact contracts and wallet operations.

Highlights

  • Contract submission: deployContract / submitContractCall with
    build → sign → submit through the Midnight JS SDK, run in a worker thread.
  • Async job model: long-running actions return { jobId, status }
    immediately; poll getJobStatus(jobId, sessionId). Crash-recoverable.
  • Wallet & funds: connectWalletForSigning (BIP39, Lace-compatible HD
    derivation), sendNight, shieldFunds / unshieldFunds, DUST
    register/deregister, plus read-only balance & fee-estimate diagnostics.
  • Tiered disclosure: AttestationVault contract +
    Attestations / DisclosureRoles, the AttestationService SDK mixin
    (public / legitimate_interest / authority tiers), and anchorDocument
    / verifyDocument for on-chain document anchoring (caller-managed storage).
  • ZK predicate attestations: prove value ≤ / ≥ threshold over a hidden
    value without revealing it (issuePredicateAttestation /
    verifyPredicateAttestation);
  • Production private state: CAP-DB-backed, AES-256-GCM encrypted provider
    replacing the SDK's LevelDB store.
  • Four OData V4 services: Nightgate, Indexer, Analytics, Admin.

Notes

Verified live on preprod: contract deploy + call, and a ZK predicate proof (47300 ≤ 50000 accepted, 51 ≤ 50 rejected by the circuit).

See CHANGELOG.md for the full list and
docs/reference.md for the complete API & configuration.

Preprod-First Readiness

10 Mar 20:19

Choose a tag to compare

What This Release Delivers

  • SAP CAP plugin bootstrap through cds-plugin.js and src/plugin.ts
  • cds.requires.nightgate configuration model for Midnight node indexing
  • Direct WebSocket connectivity to a Midnight node through MidnightNodeProvider
  • Catch-up indexing, live subscription, transient retry handling, and reorg rollback in the crawler
  • Local CAP-database persistence for blocks, transactions, sync state, and reorg history
  • OData services for blockchain reads, indexer operations, analytics, and admin session management
  • Wallet-session connect/disconnect flows with encrypted viewing-key storage, TTL cleanup, and admin invalidation
  • Health, readiness, liveness, and Prometheus-style metrics endpoints
  • Offline startup mode when the node is unavailable
  • Auto-deploy attempt when the target schema is missing