Developer Quickstart

Developer Quickstart

This guide helps you verify the NovaPanda Verifiable Delivery Claim (VDC) lifecycle in five minutes.

Card A · Trial boundary

Available vs limited

  • Available: full state machine, dual-signed VDC, offline reverify
  • Limited: no real money, no tokens, no licensed clearing

Card B · Topology

Site vs Zero Node

  • Site: whitepaper, architecture, specs
  • Zero Node: mock API, debug console, quotas

Phase 1 Node health & discovery

discovery 
$ curl -fS https://node.novapanda.io/health
$ curl -fS https://node.novapanda.io/.well-known/novapanda.json

Phase 2 Run the reference implementation

trial_remote 
$ git clone https://github.com/novapanda-protocol/novapanda.git
$ cd novapanda && python -m venv .venv && source .venv/bin/activate
$ pip install -e . && python demo/trial_remote.py

On Windows, use .\.venv\Scripts\Activate.ps1. Keys stay local — never uploaded.

Phase 3 AI tooling (optional)

MCP tools

Mount novapanda.* in Cursor / Codex; point at Zero Node.

Cursor Rules / Skill

Install Skill; agents propose / deliver / sign VDC per contract.

Equivalent surfaces

Surfaces only translate grammar — never alter VDC cryptography.

See BINDING-MCP · BINDING-SKILL · SPEC

Need a visual VDC console?

Exchange tables and debugging live on Zero Node — not this site.

Open Zero Node →