# Wallet-Based Access & Analytics

#### **Overview**

Authentication in 402Gate relies on **wallet-based identity** no usernames, passwords, or accounts.\
Users connect via Solana wallets (e.g., Phantom, Solflare), and access rights are determined entirely by blockchain signatures and transaction proofs.

#### **Core Process**

1. User connects wallet → dApp verifies public key.
2. When accessing paid endpoints, wallet signs payment or authorization.
3. Transaction is verified → data or content is delivered.
4. Logs and analytics are updated in real time.

#### **Analytics Layer**

The built-in **402Gate Analytics Dashboard** provides visibility into all micropayments:

* Total revenue (per endpoint, per token)
* API call volume
* AI agent activity
* Conversion ratios and token distribution

#### **Security Advantages**

* 🔐 **Trustless Verification** — All payments validated directly on-chain.
* 🧾 **Immutable Records** — Each access event stored transparently.
* 🧠 **Privacy-Friendly** — Only wallet addresses and hashed request IDs are stored, no personal data.

#### **Why Wallet-Based Access**

It aligns perfectly with Web3’s core principle:

> **Your wallet is your identity. Your payment is your access.**

This architecture merges authentication, payment, and access control into a single seamless cryptographic flow secure, anonymous, and verifiable.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.402gate.com/core-protocol/wallet-based-access-and-analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.