> For the complete documentation index, see [llms.txt](https://doc.yabumi.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.yabumi.xyz/english/yabumi/architecture/precondition.md).

# Precondition

## SNS ID

Yabumi uses unique numbers to identify various SNS sites. For example, Discord is ID 1, X is ID 2, etc.. To reduce gas costs, this numbering scheme has been adopted.

## Signatures

The following three components are used for backend signature generation:

1. User ID on the SNS platform (e.g., 123456789).
2. SNS ID (e.g., 1).
3. Minted wallet address (e.g., 0x123456789... - a 40-digit hexadecimal value).

## JointedID

The User ID on the SNS platform and the SNS ID are combined using an underscore, resulting in a JointedID. For example, 123456789\_1.

## Hashing

User ID, JointedID and minted wallet address are concatenated and hashed. This hashed value is used as the signature message.


---

# 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://doc.yabumi.xyz/english/yabumi/architecture/precondition.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.