# Ruby One V2 - Your Complete Ruby One Wallet Guide

<figure><img src="/files/uAcr2zGH78MsqRFMbmZa" alt=""><figcaption></figcaption></figure>

### **The only way to protect crypto is to build crypto.**

### **The only way to serve privacy is to build privacy tools.**

### **The only way to move forward is to break the status quo.**

Since day one, we have been developing solution after solution to tackle the challenges associated with privacy and access control. We believe your data and ability to exercise control over it will set the technological course for future generations and eventually determine how our societies will evolve.

Ruby Protocol is operating and building privacy & access control solutions in the space of constant change, which necessitates us developing a mindset that embraces uncertainty and evolution. Moreover, the diversity of data needs, the density of its technical landscape, and the growing incumbent system, every day, keep pushing us forward and beyond the known territory.

**Ruby V2 and the rollout of Ruby One (Ruby MPC Wallet) mark the beginning of a new chapter of Ruby Protocol.**&#x20;

With our wallet and MPC solutions in place, Ruby Protocol will add another layer of protection to user information, which ensures that only authorized computing nodes will have access to specific pieces of data, limiting the possibility of data breaches and unauthorized access.&#x20;

Plus, with its simple user interface reducing the likelihood of user error, this solution will give our users peace of mind regarding the safety and security of their personal wealth and sensitive data.


---

# 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://rubyprototcol.gitbook.io/ruby-one/ruby-one-v2-your-complete-ruby-one-wallet-guide.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.