> For the complete documentation index, see [llms.txt](https://docs.baasid.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.baasid.io/authorization-based-on-blockchain/2.-introduction/2.2.-borrowing-the-db-of-baas-based-participants.md).

# 2.2. Borrowing the DB of BaaS based participants

All blockchains save transactions records the same way and offer tight security against forgery or falsification. This is because the same data, users’ sensitive personal information and important information, and verifications keys are held by everyone making it difficult to store any of that information.

"BaaSid" takes the most fundamental uniform data storage problems and limitations of blockchain, and offers an interpretation in a completely new perspective.

When verifying information required for the personal verification a "BaaSid" participant, there is no source to forge because it is not stored anywhere thus blocking any hacking attempts.

In other words, with "BaaSid" the personal information, biometric images and any other information of a user does not exist in any format whatsoever and does not even exist on one's device. It is only saved after being split and distributed (means some of the encrypted data fragments are separated from one another and distributed to participants) as fragments on the nodes of public or Private network(Company).

<figure><img src="/files/5pPSUf1AtxWxnm5O00ic" alt=""><figcaption><p>Highest form of decentralization through a blockchain database infrastructure</p></figcaption></figure>


---

# 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.baasid.io/authorization-based-on-blockchain/2.-introduction/2.2.-borrowing-the-db-of-baas-based-participants.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.
