Private Testnet Hardening Active

PrivChain
Private Payments for Agents

PrivChain integrates with x402 payment semantics and focuses on privacy infrastructure: proof-aware verification, settlement lifecycle control, and secure signer workflows. Current stage is integration hardening with controlled partner preview access.

x402 Compatible
Testnet Hardening
API+SDK+MCP Integrated Surface
KMS/HSM Signer Isolation
Mint 8y5F...LR8i
Supply 1,000,000,000 PRIV
Mint Authority Revoked
Freeze Authority Revoked
Scroll to explore

Where PrivChain Actually Is

Not a placeholder: the interface stack is built and now in hardening and partner-readiness gates.

Current Stage

Private testnet hardening with controlled integration support.

  • x402-aligned facilitator lifecycle
  • Settlement lookup and reconciliation paths
  • Security and abuse-control validation

Intentionally Private

Trade-secret and attack-surface details are withheld until launch gates clear.

  • Proof-system internals and tuning strategy
  • Pool-level anti-abuse mechanics
  • Production defense thresholds and runbooks

Next Confidence Gates

Objective checkpoints before broad public rollout.

  • Hardening cycle closure on private testnet
  • External security review and remediation loop
  • Progressive partner onboarding expansion

Built Around Privacy Infrastructure

PrivChain is not a payment transport replacement. It is the privacy layer for machine payment flows.

x402-First Compatibility

Facilitator flows are built to align with x402 semantics so developers can adopt privacy without changing transport assumptions.

  • HTTP-native payment flow integration
  • Scheme support for priv-stark/v1
  • Deterministic verify and settle semantics

Proof-Aware Verification

Payload validation, replay controls, and expiry enforcement are engineered into the facilitator verification and settlement pipeline.

  • Replay and idempotency controls
  • External verifier integration path
  • Structured machine-readable errors

MCP-Native Agent Tooling

Native MCP tools allow AI agents to execute payments, check settlement state, and trigger reconciliation as part of automation pipelines.

  • privchain_pay
  • privchain_get_settlement
  • privchain_reconcile

Secure Signer Architecture

Signer workflows support local development keys and production-grade remote signing backends with KMS/HSM-compatible custody paths.

  • Remote signer contract: POST /sign-intent
  • AWS KMS backend support
  • Non-custodial deployment model

Start Using PRIV in 3 Steps

A proven onboarding flow adapted for PrivChain infrastructure.

01

Choose a Wallet Path

Set up your wallet and signing model. For agents, use the remote signer path instead of raw keys in shared runtimes.

Wallet setup -> signer integration
02

Get PRIV

Fund your workflow and route payment intents through x402-compatible verify and settle endpoints.

POST /verify -> POST /settle
03

Use It in Real Flows

Run private agent payments, monitor settlement status, and reconcile long-pending states.

GET /settlements/:ref -> POST /reconcile

Learn, Build, and Operate

A structured resource model for onboarding, integration, and operational readiness.

Open full resources page

User Guides

Wallet setup, first payment path, and lifecycle checks for private settlement operations.

Open onboarding guide

Developer Guides

SDK/MCP integration paths plus endpoint semantics for verify, settle, lookup, and reconciliation.

Read developer guides

Architecture and Mission

Protocol positioning, boundaries, and implementation direction for launch-critical delivery.

View mission brief

Operations and Security

Security posture, runbook intent, and release discipline for pre-launch hardening.

Open operations guide

Contract Economy

How PRIV is priced by real contract demand, trust, and measurable output delivery.

Read economy explainer

Common Questions

Fast answers to recurring questions from developers, operators, and partners.

View full FAQ

Is PrivChain replacing x402?

No. PrivChain integrates with x402-compatible payment semantics and specializes in privacy infrastructure.

Do I need a wallet UI app?

Not required. Agent workflows can use SDK/MCP and external signer services directly.

How do I track payment status?

Use settlement lookup and reconciliation endpoints for lifecycle visibility and pending-state refresh.

What is public right now?

Public docs and interface-level surfaces are live, including API naming, integration direction, and stage tracking. Sensitive internals remain private until hardening and audit gates pass.

Glossary of Core Terms

Glossary section for faster onboarding across protocol and operational language.

Open full glossary

Facilitator

Service that verifies payment payloads, submits settlements, and returns lifecycle status.

Nullifier

Replay-protection value used to ensure a payment proof cannot be reused across requests.

Settlement Reference

Identifier returned on settle used for lifecycle lookup and reconciliation updates.

Reconciliation

Operation that refreshes and reclassifies long-pending settlement states.

Signer Path

Workflow for secure transaction authorization using local keys or remote KMS/HSM backends.

Payment Scheme

The scheme identifier that binds payload structure and verification semantics.

Contribute to PrivChain

Contribution, research, and collaboration model inspired by effective open-source communities.

Contribute

Protocol, SDK, docs, and QA contributions are high impact and directly improve launch readiness.

  • Code and test contributions
  • Docs and runbook upgrades
  • Adversarial scenario additions

Research

Research track focuses on privacy proof systems, verification performance, and production hardening under pressure.

  • Verification pipeline research
  • Performance experimentation
  • Threat model refinement

Community Channels

Coordinate with maintainers, partners, and contributors on integration issues and launch readiness work.

  • GitHub organization collaboration
  • Partner and integration reviews
  • Launch gate progress updates

Launch Progress

Current execution status with explicit hardening and release gates.

Completed

Integration Surface Buildout

  • x402-compatible facilitator surface
  • SDK, MCP, examples, and signer integrations
  • Public docs, status pages, and partner-ready visibility
Done
In Progress

Private Testnet Hardening

  • Replay, idempotency, and lifecycle edge-case testing
  • Signer isolation and custody-path hardening
  • Gate evidence consolidation for external review
Active
Next

External Audit and Pilot Expansion

  • Third-party security audit execution
  • Critical/high remediation and re-test cycle
  • Structured partner pilot expansion
Pending
Launch Gate

Progressive Public Rollout

  • Hard-gate sign-off (founder, engineering, security)
  • Controlled visibility and disclosure expansion
  • Developer onboarding at broader scale
Pending

Track Execution and Join Early Integrations

PrivChain is in private-testnet hardening with controlled partner onboarding and clear launch gates.

Current stage: integration hardening plus partner preview, with progressive disclosure toward public rollout.