@tat-protocol/gate

Gate services for access verification and challenge/proof workflows.

Install

npm install @tat-protocol/gate

Exports

• GateServerSpec (spec-oriented NWPC gate service)
• GateBase (extensible base class)
• Gate (minimal wrapper)
• Built-in strategies: singleUse, multiUse, timeWindow, allOf
• SimpleAccessPolicy / createAccessPolicy
• Types from types.ts and spec-types.ts

Quick Start (Spec Server)

import { GateServerSpec } from "@tat-protocol/gate";
import { NodeStore } from "@tat-protocol/storage";
import { KeySigner } from "@tat-protocol/signers";

const gate = await GateServerSpec.create({
  signer: new KeySigner(process.env.GATE_SECRET_KEY!),
  storage: new NodeStore(".gate"),
  relays: ["wss://relay.damus.io"],
  serviceName: "Premium API",
  challengeExpiry: 300,
  sessionExpiry: 3600,
});

console.log(gate.getPublicKey());

Easy Local Validation

For in-process gates, compose defaults instead of writing custom strategy classes:

import {
  createAccessPolicy,
  singleUse,
  allOf,
  timeWindow,
} from "@tat-protocol/gate";

const policy = createAccessPolicy({
  name: "Main entrance",
  allowedIssuers: [process.env.TICKET_FORGE_PUBKEY!],
  requireValidSignature: true,
  requireNotExpired: true,
});

const strategy = allOf([
  singleUse(),
  timeWindow({ startsAt: eventStartMs, endsAt: eventEndMs }),
]);

Protocol Flow

1. Client calls gate.request_access.
2. Server returns challenge (gate.challenge).
3. Client submits proof to gate.verify.
4. Server responds with gate.result and optional session token.

Runtime Notes

• Session validation is available via verifySession(sessionToken).
• Gate supports full and minimal proof modes.
• Persist state to avoid replay gaps across restarts.