Direct answers for developers, operators, and launch partners.
No. PrivChain uses x402-compatible payment semantics and focuses on privacy infrastructure.
The intended private scheme is priv-stark/v1, aligned with x402-compatible payment payloads.
Not strictly. A secure signer workflow plus SDK and MCP flows can power agent-first usage before a full consumer wallet UI.
Use remote signer architecture for production deployments with KMS/HSM-compatible backend paths.
Use settlement lookup by reference and reconciliation operations for long-pending states.
Stage status, interface-level docs, mission framing, and API surface are public. Launch-critical internals remain private until hardening and audit gates pass.
TypeScript SDK, Python SDK, MCP server tools, and reference examples for end-to-end payment flow validation.
Begin with API Surface, then follow Resources and Developer Intent.