# 📌8 Major Problems

**🔐 Forgetting the Seed Word = Losing All Assets**

Web3 wallets are tied to just 12 words. Losing these words means losing assets forever.

 

**⚰️ Assets Die When a User Dies**

When many users die, there's no way to access their wallets. The inheritance or transfer mechanism is still a mystery in Web3.

**🧩 No NFT and Token Recovery**

Current systems can only recover the wallet; NFTs or tokens remain inside.

KEYNOX is the first system to offer asset-based recovery.

**🏦 Centralized Recovery Systems Are Unreliable**

Recoveries performed through KYC, email, or centralized services are both contrary to the spirit of Web3 and carry the risk of hacking.

 

**⛓️ No On-Chain Recovery**

Many recovery solutions operate off-chain. This means transactions are unauditable, centralized, and potentially risky.

 

**🧠 Forgetfulness is Human, But Web3 Is Unforgiving**

People can lose their devices and forget their information. But Web3 offers no resilience to these errors.

**🧑‍💻 Web3 Is Still Very Intimidating for New Users**

Concepts like seeds, private keys, and backups are complex for non-technical users. This creates a very high barrier to entry.

 

**💸 Unrecoverable Assets Damage the Ecosystem**

Lost assets create dead capital on-chain. This reduces both liquidity and ecosystem efficiency.


---

# 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://keynox-1.gitbook.io/keynox-docs/getting-started/8-major-problems.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.