Pulse Documentation
Pulse Protocol is purpose-bound consent and permissions: grant, use, revoke, and prove — with sensitive payloads off-chain and minimal anchors on-chain. It is a shared consent spine for integrations, not a single product UI.
Start here — Pulse Protocol
Protocol overview
Purpose, scope, audiences, and how the documentation is organised.
Core principles
Off-chain validation, stateless anchors, explicit consent.
Architecture
Components, flows, and how services fit together.
Deep dive
Cryptography, sequences, and implementation detail.
On client and internal docs, use Integration Guide in the sidebar for step-by-step material and OpenAPI references.
What Pulse enables
- Open-banking-style permissions with explicit grant and revoke, anchored for audit.
- Multi-party data sharing with the data subject (or agent) in control of keys and consent metadata.
- Regulated workflows that need tamper-evident consent history without centralising plaintext.
Product guides (VAS, Pulse+, Middle Tier) live under Platform services below; each product has its own documentation.
Why it matters
| Audience | Pulse Protocol docs help you… |
|---|---|
| Integrators | Wire consent grant/revoke, trust boundaries, published APIs. |
| Architects | Components, flows, and security model before you commit. |
| Operators | Deploy and run Pulse-aligned infrastructure (where published). |
Learn more
Platform services
Smarter Contracts also documents operated platform services (products built on or alongside Pulse). Each service has its own overview and integration path; they are not substitutes for the consent protocol guides above.
Never share wallet mnemonics or private keys. Pulse Protocol cannot recover lost keys and does not store unencrypted sensitive data.