For implementers
For implementers
The whitepaper describes the protocol, the formal specification defines the exact wire format, and the reference implementation is checked against a conformance-vector corpus.
Whitepaper — the specification. All fourteen chapters plus appendices, online or as a PDF: motivation, the wire profile, channels, security, privacy, incentives, and governance.
Formal spec — interoperability spec F1–F10. The exact rules an implementation conforms to, with a conformance-vector corpus. The whitepaper describes; the formal specification defines.
Reference implementation — paytp-ri. A Rust core with rail adapters and a WebAssembly demo facade, MIT / Apache-2.0. cargo test --all-features --workspace runs the unit suite and the F10 conformance corpus.
paytp-ri, run cargo test --all-features --workspace (unit tests, F10 conformance, property tests), then node demos/suite/serve.mjs to open the demonstration suite locally. The browser demos are built from the demo WebAssembly facade (demos/wasm/, paytp-demo-wasm; wasm-pack build --target web) — a demo and measurement artifact, not an implementer SDK. The specification is pinned by commit hash in PINNED_SPEC; a divergence found while building is resolved by changing the specification, not by working around it in code.