> For the complete documentation index, see [llms.txt](https://whilz.gitbook.io/whilz-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whilz.gitbook.io/whilz-whitepaper/user-friendly-technology.md).

# User-Friendly Technology

It provides the easiest wallet ID in the crypto world. This refers to the time needed for a transaction verification in less than 3 seconds! And as a receiver, you have to option to accept or reject the incoming transactions. Each transaction is safe and secured. The wallet is fully encrypted and the user is the only one who has access to Private KEY, PIN and backup.

The biggest problem with today's wallet technology, if one forgets the wallet’s private key. There is no way to recover and one can lose millions. This is The user is enabled to set his own private key and a transaction authentication pin. The user is enabled to set a private key and a transaction authentication pin. Certain information can never be cracked due to the fact that Whilz uses cryptography to keep account information safe. Account information is encrypted, remains stored, and only users are able to reset the password. Additionally, users are able to add another form of security, utilising 2FA with Google Authentication.


---

# 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://whilz.gitbook.io/whilz-whitepaper/user-friendly-technology.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.