Panther Protocol Documentation
WebsiteBlogTwitterGovernance ForumVoting
  • 📘Start Here
    • Get Started
    • What is Panther?
    • Who is Panther for?
    • Realized vision and use cases
  • 🔩Panther Core
    • Testnet dApp
    • Mainnet Beta (Canary)
    • Panther Transactions
      • Shielded Pool
      • zAssets
      • zAccount
      • zTrade (OTC Trading)
    • Panther Compliance
      • User Reveals
        • History CSV Export
      • Forensic Reveals
  • 🌌Ecosystem
    • Ecosystem roles
      • Compliance Providers
      • Relayer
      • zMiner
        • Get Started
      • Zone Manager
        • Get Started
    • Fees & Rewards
  • ⚙️Interoperability
    • DeFi Adaptors
      • zSwap
        • Economic optimization of swaps
    • Multi-chain
  • 📚LEARN
    • Glossary
    • UTXOs
      • UTXO Model
      • UTXO Cryptography
      • Merkle Trees
    • ⚗️Cryptographic Primitives
      • ZK proofs
      • ZK SNARKs
        • Groth16
      • Homomorphic encryption
      • Hash functions
      • Poseidon
      • Other Privacy Enhancing Technologies (PETs) used by Panther
      • Elliptic curves
      • Pairings
    • 🔓Security Audits
    • 🤝Community
    • 📚Resources
  • Panther DAO
    • DAO and Decentralization
      • Governance Framework
    • Road to decentralization
      • Decentralization Tool
  • Changelog
    • Product versions
    • Oshiya
    • Panther Testnet
      • Stage 0
      • Stage 1
      • Stage 2
      • Stage 3
      • Stage 4
      • Stage 5
      • Stage 6
      • Stage 7
      • Stage 8
      • Mainnet Beta (Canary)
Powered by GitBook
On this page
  • TL;DR
  • Introduction
  • What next?
Export as PDF
  1. Panther Core

Panther Compliance

Compliance

PreviouszTrade (OTC Trading)NextUser Reveals

Last updated 11 months ago

TL;DR

  • determine what compliance looks like for their Zone/s

  • The Protocol is agnostic as to which third-party integrates

  • The Protocol does not process user data; compliance providers do

  • Transactional data can only be accessed by stakeholders with the correct keys

Introduction

Considering the difficulties in developing a decentralized solution that preserves privacy and enables compliance, Panther designed an approach that utilizes three essential components: third-party integrations, Panther , and .

By leveraging the Protocol’s Zero-Knowledge characteristics, these elements collectively form a pathway to achieve compliance.

Read about the for Panther integrating compliance tools.

Panther has built a system that retains neutrality by integrating compliance providers that accept multiple types of verification. These systems are called “multi-compliance vendors,” as they allow users to choose from a variety of compliance providers while retaining a decentralized approach.

At mainnet beta, there will be just one verification level available for all users.

When integrating these providers, the following requirements are taken into consideration:

  • Ability to blocklist Politically Exposed Persons (PEPs) or newly-flagged individuals based on unverified identities

  • Blocklists for Externally Owned Accounts (EOAs), i.e. wallets

  • Ability to create an “allowlist” to control entry to a Zone

  • Preferably, the ability to have an on-chain verification list maintained through oracles/smart contracts

  • Performing validations at deposit and withdrawal

  • Optionally, allowing users to register multiple addresses. This is suggested so that users can break the on-chain link between their transactions by withdrawing and depositing from different addresses.

  • Optionally, using a Zero-Knowledge proof to allow users to create new accounts once they have passed verification.

Panther Protocol allows compliance providers to process user data without the Protocol learning it: by proving a user’s ownership of their wallet and giving them a Zero-Knowledge proof that attests to the validity of their KYC statements. This allows users to access Panther but maintains the Protocol’s neutrality. The diagram below exemplifies this process:

What next?

Not only do the compliance providers enable Zone Managers and users to demonstrate their transactional activity to regulators, but they also give the individual zAccount holder, the user, a high degree of control over what data they reveal to whom. Learn more about user reveals.

For testnet, the Panther DAO was commissioned to select a that aligns with its interests.

Discussed in Panther’s .

Panther’s flow for user verifications.
🔩
multi-compliance vendor
forum
Zone Managers
compliance provider/s
compliance provider
zAccounts
regulatory rationale
Zones