> For the complete documentation index, see [llms.txt](https://solayer-labs.gitbook.io/solayer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solayer-labs.gitbook.io/solayer-docs/developers-guides/for-builders/architecture.md).

# Architecture

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

The restaking pool manager oversees the flow of assets into the protocol. When users deposit LST or SOL (which is first converted to sSOL-raw), they receive a fungible token representation in return. Collectively, we call them Solayer assets. Currently illiquid to facilitate points calculation for the liquidity reward program, this representation will become liquid in the future to encourage composability with DeFi.

Solayer assets at this layer won't have any unbonding lockups since they unwrap into the respective LSTs. The AVS unbonding process is separately managed by the delegation manager. To offer more flexibility, Solayer allows them to design their own unbonding process with a maximum unbonding period within 2 days. Solayer will also provide an emergency exit mechanism to release the bound stake from users should the AVS cease to function.

Stage 2 of our protocol development will enable users to pledge their Solayer assets to secure additional networks by delegating them to a Solayer operator responsible for managing the AVS nodes. Should an operator engage in malicious behavior, they will be subject to penalties, potentially resulting in a loss of the user's deposit. Consequently, users must exercise caution when selecting operators to delegate to, ensuring that they possess a trustworthy track record and fulfill the requisite criteria of the AVS.

Once delegation to SVNs and node operators is live, users will construct their restaking portfolio by selecting the node operators to delegate to and SVNs to secure. They will then be issued a non-fungible token. This token is non-fungible due to the idiosyncratic risks associated with the selected node operators and the SVNs.

Rewards accounting is calculated offline. Solayer has implemented a state watcher to keep track of deposits and withdrawals. Together with the invite relationship data, additional rewards will be applied to user accounts in real-time.

The Restake method on Solayer is permissioned and requires an additional signature from the server. This is to allow us to enforce deposit limits in the first few epochs. The Unstake method does not require an additional signature from Solayer.


---

# 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://solayer-labs.gitbook.io/solayer-docs/developers-guides/for-builders/architecture.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.