> ## Documentation Index
> Fetch the complete documentation index at: https://pond.dflow.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Identity verification service linking verified identities to Solana wallets

Proof is an identity verification service on Solana. It enables partner applications to verify that a wallet belongs to a KYC'd individual without handling identity verification themselves.

<Note>
  Have a specific question? See the [Proof FAQ](/resources/faqs#proof).
</Note>

## When to Use Proof

Use Proof when your application needs to confirm that a wallet belongs to a verified, KYC'd individual: to gate features by identity or jurisdiction, or to meet compliance requirements, without building identity verification yourself. Spot trading on DFlow does not require Proof.

## High-Level Model

Proof connects three key entities: users, verified identities, and wallets. Users authenticate and verify their identity once, then link multiple wallets to that identity. Partner applications query the identity graph to check verification status.

```mermaid theme={null}
flowchart TD
    User -->|authenticates| Session
    User -->|completes| Verification
    Verification -->|creates| VerifiedIdentity[Verified Identity]
    VerifiedIdentity -->|links to| Wallet1[Wallet 1]
    VerifiedIdentity -->|links to| Wallet2[Wallet 2]
    VerifiedIdentity -->|links to| WalletN[Wallet N]
    PartnerApp[Partner App] -->|queries| VerifiedIdentity
```

## Verified Information

Proof verifies the following information about users:

| Verified Information      | Description                             |
| ------------------------- | --------------------------------------- |
| Name                      | Full legal name from government ID      |
| Address                   | Residential address                     |
| Contact Information       | Email address (used for authentication) |
| Government Identification | Government-issued ID document           |

## Key Outcomes

### Identity Graph

Creates a mapping between verified identities and wallet addresses that can be queried by partner applications. This graph is the core data structure that enables verification across the ecosystem.

### Reduce Friction for Partner Apps

Allows apps to outsource identity verification while maintaining a seamless user experience. Partners redirect users to Proof, and users return verified, no need to build KYC infrastructure.

### Compliance

Helps partner applications meet regulatory requirements by providing verified wallet ownership data. When a partner queries a wallet, they get a clear verification status they can use for compliance decisions.

### One-Time Verification

Users verify once and can use their verified identity across all partner applications. This reduces friction for users and increases conversion for partners.

## What Proof Delivers

### Authentication

* Email-based authentication with one-time codes
* Session persistence across visits

### Identity Verification

* Document verification (government-issued ID)
* Biometric verification (selfie matching / liveness check)
* Clear status communication (pending, verified, failed)

### Wallet Management

* Link multiple wallets to a single verified identity
* Cryptographic proof of wallet ownership (signature verification)
* Optional wallet labels for organization
* Remove wallets when needed
* Audit trail of wallet changes

## Next Steps

<CardGroup cols={2}>
  <Card title="User Journeys" href="user-journeys">
    Understand the verification flows for different user types.
  </Card>

  <Card title="Integration Guide" href="partner-integration">
    Learn how to integrate Proof into your application.
  </Card>

  <Card title="Proof API Reference" href="/resources/proof-api/verify-address">
    Explore the API endpoints for verification and wallet management.
  </Card>
</CardGroup>