pontmore/nextjs-pontmore repository overview

⁠nextjs-pontmore

Next.js + TypeScript proof of concept for publishing, discovering, and inspecting Pontmore protocol events on Nostr.

The app defaults to these relays:

• wss://nos.lol
• wss://relay.damus.io

⁠Run

npm install
npm run dev

Open http://localhost:3001. Port 3001 is the default for both development and production. Set PORT or pass --port to use another port:

PORT=4100 npm run dev
npm run dev -- --port 4100

npm run build
PORT=4100 npm start
npm start -- --port 4100

Docker also accepts a runtime port override, for example docker run --rm -e PORT=4100 -p 4100:4100 pontmore/nextjs-pontmore.

⁠Docker

Build and run the production image locally:

docker build -t pontmore/nextjs-pontmore .
docker run --rm -p 3001:3001 pontmore/nextjs-pontmore

The GitHub Actions workflow in .github/workflows/publish-docker.yml publishes pontmore/nextjs-pontmore to Docker Hub on every push to main.

Required repository secrets:

• DOCKER_PONTMORE_OWNER
• DOCKER_HUB_PONTMORE_PUBLISH_TOKEN

⁠Behavior

• Generates local Nostr identities in browser localStorage.
• Publishes kind 30360 addressable PIP-00 agent definition events.
• Publishes kind 30361 addressable PIP-01 escrow descriptor events.
• Supports server-side relay reads, lookup, publishing, and process-local caching through Next.js API routes.
• Provides discovery filters, pubkey/coordinate lookup, copyable coordinates, and JSON definition inspection for agent and escrow cards.
• Lets relay defaults be edited from the Settings page.

The relay WebSocket client is intentionally small and lives in lib/nostr-relays.ts. Server-side cache orchestration lives in lib/server/.

⁠Protocol baseline

Discovery is aligned with Pontmore protocol revision d9a1eb3⁠ (checked 2026-10-03):

• PIP-00 v1: a non-empty list of versioned capability identifiers, matching pontmore-capability: tags, and optional marked escrow references. Names and descriptions use kind 0 profiles; relay preferences belong in standard Nostr relay-list events. Commercial terms are outside this capability index.
• PIP-01 v1: mechanism, networks, expires_at, and optional service.schema (openapi or asyncapi, HTTPS URL). Includes Lightning hold, custodial, and Cashu mechanisms. Funding, release, refunds, fees, disputes, and recovery are defined by the referenced service schema.
• Relay reads and publish routes verify event signatures. Publish routes also validate the relevant discovery schema. Invalid/legacy discovery content is shown with validation errors and cannot prefill the publishing forms. Republish a current definition to migrate; old content is not converted into a capability claim.
• Addressable replacement uses newest timestamp, then lowest event ID on a tie. An expired replacement remains the current descriptor; it does not expose an older revision as selectable. Expired descriptors remain inspectable and are excluded from suggested escrow references.

This app implements discovery and inspection. It does not fetch service schemas, invoke escrow services, verify service safety, or implement PIP-02 coordination chains or pontmore/swap@1 replay. A capability declaration does not prove implementation or availability. Before an economic action, a full client must validate the current descriptor, fetch and validate its schema with destination/redirect/size safety checks, and bind the exact accepted descriptor event ID in the coordination.

⁠Checks

npm test
npm run typecheck
npm run build