> For the complete documentation index, see [llms.txt](https://team57.gitbook.io/web3-sensei/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://team57.gitbook.io/web3-sensei/ecosystem/infrastructure.md).

# Infrastructure

In its pursuit to integrate developers and applications into the Web3 landscape, Web3 Sensei is in the process of developing cutting-edge middlewares. These include a one-login DID (Decentralized Identity) solution, a built-in wallet infrastructure, and a social graph integrated interface, forming an all-encompassing onboarding system.

The adoption of rollup technology as the foundational layer for asset and data consolidation represents another critical component of Web3 Sensei's strategy. This approach is instrumental in establishing a fast and scalable blockchain infrastructure. By moving computational logic and data onto application rollups, Web3 Sensei is methodically building its ecosystem, paving the way for a more efficient and interconnected Web3 environment.

<br>


---

# 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://team57.gitbook.io/web3-sensei/ecosystem/infrastructure.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.