# Why Default Privacy?

Solana is the fastest and most efficient blockchain in the world. However, its greatest strength is also a major privacy vulnerability. By default, every action on Solana is completely transparent.

### The Transparency Problem&#x20;

When you send SOL or USDC to a friend, pay a freelancer, or interact with a decentralized application, you are leaving a permanent public trace. Anyone who knows your wallet address can easily view your entire financial history. They can instantly see:

* Your Total Net Worth: Exactly how much SOL, USDC, and other tokens you hold.
* Your Transaction History: Every payment you have ever sent or received.
* Your On-Chain Habits: Which protocols you use and when you are active.

### The Real-World Equivalent&#x20;

Imagine paying for dinner at a restaurant with your credit card, and the waiter instantly receives a printout of your entire bank statement. You would never accept that level of exposure in traditional finance. Web3 should not force you to accept it either.

### Security Through Privacy&#x20;

Privacy is not just about keeping secrets. It is a fundamental security requirement. When your wallet balance is publicly tied to your identity, you become a target for scams, phishing attacks, and social engineering. By using VeerTx, you protect yourself. Breaking the on-chain link between your main wallet and your transactions ensures your financial data stays exactly where it belongs: in your hands alone.


---

# 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://veertx.gitbook.io/veertx-docs/introduction/why-default-privacy.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.
