> For the complete documentation index, see [llms.txt](https://docs.gridlock.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridlock.network/the-tech/design-principles/simple.md).

# Simple

The greatest crypto security means little if it's not user-friendly. As human error is the leading cause of security breaches and theft, ease-of-use is a paramount consideration in our design.&#x20;

Gridlock is built with user convenience in mind. Whether you're a day trader or a long-term investor, Gridlock ensures an intuitive and seamless experience for all users.&#x20;

Our user experience research has led to the creation of a wallet accessible to anyone. Your crypto and NFTs are always within reach, anytime, anywhere.&#x20;

To start using Gridlock, simply invite two friends to be guardians, then purchase or transfer crypto into your wallet. Try Gridlock today and discover its simplicity for yourself.


---

# 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://docs.gridlock.network/the-tech/design-principles/simple.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.
