> For the complete documentation index, see [llms.txt](https://whitepaper.shegby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.shegby.com/how-does-shegby-work.md).

# How does Shegby work?

Shegby is based on the unique HumanRank technology, which uses the theory of six degrees of separation to verify connections and their data within a user's network.

To join Shegby, users must have a Web3 wallet, such as MetaMask (Shegby currently operates on the Scroll blockchain - which seamlessly extends Ethereum's capabilities through zero-knowledge technology and EVM compatibility).

Unlike traditional KYC methods, Shegby provides offline identity verification. Users can verify each other's identities, creating a chain of trust within the network. This approach allows users to build trust, eliminating the need for centralised authorities.

Shegby puts users in control of their personal information. They can choose what information to share and with whom, keeping their data secure and private. Users can also update their information as needed, keeping their data up to date over time.

***

You can discover Shegby with all the links collected in one <https://linktr.ee/shegby>


---

# 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:

```
GET https://whitepaper.shegby.com/how-does-shegby-work.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.