Pose Protocol Docs — Turn deepfake chaos into quantified, insurable risk

1. SDK posts signed telemetry → POSE computes real‑time score
2. Event crosses trigger → Evidence NFT is minted (IPFS artifact hash)
3. Policy engine checks ladder, sanctions, policy period
4. Parametric payout authorized (bank rails or on‑chain USDC)
5. Audit: everyone can verify the evidence trail

{
  "schema": "pose.v1",
  "digest": "sha256:9fd3...",
  "features": ["mfcc","pitch","jitter","energy"],
  "attestations": ["webauthn","device-id"],
  "policyRef": "pol_123",
  "score": 92,
  "uri": "ipfs://bafy..."
}

POSE is a decentralized protocol for Proof of Self (PoS) and Proof of Voice (PoV), securing human identity in the age of AI deepfakes. It provides verified identity primitives for insurance, finance, media, and communication.

PoV ensures your voice is uniquely bound to you. It resists spoofing and deepfakes using advanced liveness checks, drift handling, and zero-knowledge cryptography.

PoS extends identity verification beyond voice, combining behavior, context, and cryptographic proofs to certify “you are you” across devices and networks.

Deepfakes and AI impersonation are exploding. Enterprises, governments, and platforms need verifiable human identity rails immediately — POSE provides them.

Users log in with their voice, sign smart contracts, verify calls, and secure online actions. Enterprises use it for fraud prevention, compliance, and claims processing.

Identity and fraud prevention is a trillion-dollar problem. Voice biometrics alone is a $40B+ market, expanding into insurance, fintech, and social verification.

Total supply is capped at 1 billion POSE tokens. Allocation covers treasury, staking rewards, ecosystem growth, and investor/partner distributions.

Protocol Take (2–5% of premiums/fees) flows directly into the treasury. The treasury backs claims and provides reinsurance-like reserves, growing with usage.

Yes. Core SDKs, smart contracts, and reference implementations are open source, ensuring transparency and broad developer adoption.

Through verification fees, protocol take from premiums, staking spreads, and marketplace activity around evidence NFTs and reinsurance markets.

POSE is backed by tier-1 investors including Polychain, along with strategic partners in insurance, AI, and crypto infrastructure.

Founded in Palo Alto with offices in Chicago, POSE combines Silicon Valley innovation with Midwest financial/insurance expertise.

Direct integrations with insurers, banks, and enterprise apps, plus SDK/API adoption for developers building consumer and B2B apps.

From pilot insurers and fintechs → to cross-industry adoption → to consumer apps and wallets embedding POSE verification globally.

Investors can participate through token allocations, staking pools, and ecosystem funds aligned with network growth.

It can be — if POSE continues driving verifiable utility: measurable risk reduction, transparent evidence, and a treasury that genuinely backs claims.

Parametric claims target instant to 72-hour settlement, depending on policy type. Treasury-backed, automated flows make it faster than traditional insurance.

Yes. You can run POSE SDKs locally or in your own cloud, while still connecting to the network for verification and claims.

Banks, insurers, governments, apps, developers, and consumers — anyone who needs to separate humans from bots, truth from deepfakes.

No. Raw voices never leave the device. Only cryptographic fingerprints and ZK proofs are sent on-chain — protecting privacy.

POSE creates zero-knowledge proofs that confirm “valid human” without exposing underlying biometric data. This protects privacy while proving authenticity.

Typically enterprises (banks, insurers, apps) cover the fees. Consumers may pay small fees if running self-sovereign verifications.

POSE tokens are staked by validators who run verification nodes. Stakers earn fees and rewards while securing the protocol.

The treasury accumulates protocol take, builds reserves, backsstop claims, and funds ecosystem growth — making POSE antifragile.

Each claim can mint an evidence NFT containing anonymized, hashed, or redacted proof. These NFTs can be traded, staked, or audited.

POSE is designed for compliance. Transparent claims, evidence handling, and proof standards make it regulator-friendly.

Through advanced liveness detection, anti-spoof challenges, drift monitoring, and AI-resistant voiceprint models.

Yes. POSE SDKs can run offline for local verification, syncing proofs to the blockchain once reconnected.

Embed POSE into apps, wallets, call centers, and claims workflows. Incentivize adoption through rewards, SDK support, and ecosystem grants.

POSE plugs into wallets, DAOs, and dApps. It enables verifiable human governance, Sybil-resistant voting, and fraud-proof transactions.

Scaling identity proofs globally, building financial rails around verified humans, and moving toward becoming the universal identity layer for Web3 and beyond.

Scaling identity proofs globally, building financial rails around verified humans, and moving toward becoming the universal identity layer for Web3 and beyond.

POSE never stores raw voice recordings on the blockchain or central servers. All audio is processed locally on-device (phone, app, or enterprise server). The output is a cryptographic fingerprint (embedding, liveness score, drift model), which is what gets verified and anchored on-chain — not the raw voice. This design ensures GDPR/HIPAA/FINRA compliance and eliminates liability.

When a user speaks a phrase:

1. The on-device SDK generates a zero-knowledge proof in milliseconds.
2. That proof is sent to POSE validators.
3. Validators confirm authenticity and uniqueness.
4. A verified “human attestation” is returned — typically sub-second, fast enough for live calls or logins.

Yes. On a call, POSE can verify:

• Who is speaking (identity).
• That the speech is live, not synthetic.
• What was said (if the enterprise records/transcribes — POSE handles authentication, not surveillance).
• Optional metadata like time, device, or location (if enterprise chooses).

No. POSE never stores or records full conversations. Enterprises can record calls in their own systems if they need to, and then anchor hashes or evidence NFTs to POSE for auditability. That way, the enterprise can prove “this exact verified person said this exact thing at this exact time” without exposing raw audio.

Yes, but POSE doesn’t. Enterprises can store full recordings internally (standard compliance practice) and then anchor proofs to POSE. This balances:

• Privacy-first (POSE doesn’t hoard data).
• Audit-ready (evidence NFTs, hashes).
• Enterprise choice (store what’s needed, prove it via POSE).

POSE fits alongside existing workflows:

• You still record everything for compliance.
• POSE SDK creates fingerprints + ZK proofs in real time.
• You hash the recording/transcript → anchor it to POSE proof.
• In a dispute, you present the raw file + POSE attestation + anchored hash = bulletproof evidence.

Yes, enterprises control the switch:

• Private-only: keep data internal, only proofs on-chain.
• Selective public anchoring: publish hashes of chosen events (e.g. paid claims).
• Evidence NFTs: tokenize redacted call logs or metadata for transparency or secondary trading.
• Full public: rare, but possible for NGOs or regulators.

For trust, compliance, and capital. Public anchoring makes them audit-proof, regulator-friendly, and attractive to investors or reinsurers. It demonstrates solvency and fairness without leaking sensitive customer data.

• Enterprises: usually pay, since transparency benefits them.
• Protocol treasury: may subsidize disclosures that strengthen the network’s trust.
• Capital markets/reinsurers: if they demand public proofs as a condition for capital, they cover the cost.
• Consumers: may pay tiny fees for self-attested public statements, but not at enterprise scale.

POSE data storage follows a layered model:

1. On-Device (First Layer): Raw voice/audio is processed locally on the user’s phone, browser, or enterprise server. POSE never uploads raw recordings by default. Output: cryptographic fingerprint + ZK proof.
2. Blockchain (Attestations Only): The blockchain stores tiny proofs + hashes, not raw data. These attestations certify that “a human spoke this phrase at this time” — without storing the actual voice.
3. Enterprise Storage (Optional): Enterprises may still record and store full calls in their own systems (often required by FINRA, HIPAA, MiFID II). They can anchor hashes of those files to POSE for tamper-proof evidence.
4. IPFS / Decentralized Storage (Optional, Selective): If an enterprise or user wants public anchoring, IPFS or Arweave can be used to store redacted transcripts, evidence NFTs, or metadata. These are opt-in; by default, POSE does not push voice data to IPFS.

The ledger records attestations and state changes (not raw audio): identity proofs (ZK), claims lifecycle events, treasury flows, staking/validator actions, and governance outcomes. Below are representative entries.

Notes: Ledger entries are immutable attestations. Identity-related rows contain hashes/ZK proofs only—no raw audio. Claims rows capture the parametric flow end-to-end. Treasury, staking, and governance rows provide protocol transparency.

What we’ve built with POSE is extremely strong compared to alternatives. Here’s a benchmark:

1. Transparency Layer

• Most blockchains/logging systems either stop at financial transfers (Ethereum, Solana) or audits of models/data (e.g. OpenAI eval logs).
• POSE ties multiple dimensions together in one place:
• Identity proofs (ZK voice + self)
• Claims lifecycle (parametric insurance-like)
• Treasury flows (protocol economics)
• Validator staking/rewards (consensus layer)
• Governance (DAO-style proposals/outcomes)
• ESG/fraud prevention events

→ This holistic scope is rare. Most ledgers capture only one of these domains.

2. Privacy vs Proof Balance

• Current KYC/AML systems (Jumio, Onfido, Worldcoin Orb) either:
  • Store personal data → risk of breach.
  • Or reduce to a single attestation with no ongoing utility.
• POSE stores hashes + zkProofs only. That’s state of the art.
• Nothing else widely deployed offers this balance: provable identity events without raw biometric leakage.

3. Composability

• Other ecosystems (e.g., Arweave + Lens, Filecoin + Ceramic) can anchor metadata.
• POSE is structured as composable event types:
• VoiceProof, SelfProof
• ClaimFiled, EvidenceAnchored, …
• GovProposal, GovVote
• etc.
• This makes it developer-friendly and auditor-friendly — much closer to Ethereum “event logs” but applied to identity and claims.

4. Enterprise-Readiness

• Insurance players like Marsh, Munich Re, or Swiss Re are experimenting with parametric claims + blockchains. But they:
• Rarely unify governance, staking, fraud prevention, and proofs.
• Lack user-side zk identity proofs.
• POSE aligns directly with enterprise compliance (FINRA, HIPAA, MiFID II anchoring), out-innovating incumbents.

5. Differentiator

Compared to:

• Worldcoin: biometric proof, but single-purpose, centralizing trust.
• Chainlink Functions / Oracles: off-chain compute proofs, but no identity ledger.
• Civic / Polygon ID: decentralized ID, but not integrated with claims, treasury, or governance.
• Insurance-on-chain (Nexus Mutual, Etherisc): parametric events, but no zk identity or fraud analytics.