> For the complete documentation index, see [llms.txt](https://matheus-draau.gitbook.io/solana-onboarding-kit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://matheus-draau.gitbook.io/solana-onboarding-kit/critical-issues.md).

# 5. Where risk becomes a block

Severity 4 is not "very bad". It is **a block or irreversible financial risk**. The concentration of these items is the most serious finding of the investigation:

| App              | Sev-4 items | Nature of the critical issue                                                                  |
| ---------------- | :---------: | --------------------------------------------------------------------------------------------- |
| **Orca**         |   30 / 30   | Total absence of onboarding (uniform marking)                                                 |
| **Kamino**       |   30 / 30   | Total absence of onboarding; in a lending context, the missing safety net is especially risky |
| **Meteora**      |      3      | Cluttered design failed entirely + zero error prevention                                      |
| **Trust Wallet** |      2      | Seed loss = permanent block; no support at the critical moment                                |
| **Phantom**      |      1      | Seed phrase displayed with no inline support                                                  |

Two findings deserve highlighting.

{% hint style="danger" %}
**The financial block from the absence of a safety net.** In Trust Wallet, losing the seed phrase means a permanent, irreversible block of the funds: no assisted recovery, no recognition mechanism to replace it. The product works on the happy path but exposes the user to total loss with no safeguard whatsoever. It is the kind of failure that does not show up in a low average, but that, when it materializes, is catastrophic.
{% endhint %}

**The silent gate.** In Ledger, *blind signing* must be enabled manually on the device to interact with Solana dApps, a step undocumented in the main interface that **blocks transactions without explaining why**. The user is stuck without understanding the reason. It is the emblematic case of a failure that mixes jargon, absence of contextual help, and a block, three of our patterns in a single point.

**KYC as a trap.** In OKX, documents rejected without specific diagnosis ("document not accepted", without saying whether it was glare, validity, or a mismatch) lead the user to resubmit the same files indefinitely, made worse for the Brazilian user, whose documents in Portuguese create friction in a system calibrated for other countries. In Backpack, mandatory KYC works as a total blocking gate that arrives as a negative surprise.

***

➡️ Continue to [**6. What stood out the most**](/solana-onboarding-kit/key-observations.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://matheus-draau.gitbook.io/solana-onboarding-kit/critical-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.