# Session Appchain

Session Node state is primarily tracked by the Session Appchain, a native L1 which includes rewards calculation logic and voting logic required to deregister or punish nodes on the network. New nodes are permissioned into the Session Node network through staking into the EVM native staking contract.

The consensus of Session Nodes can be snapshotted and signed efficiently using BLS signatures and posted back to the native EVM native chain for validation. This is used for node deregistration and is required for any Session Node to claim funds or withdraw their Session Node from the network.

{% hint style="info" %}
Appchains are specialized, app-specific blockchains built to increase scalability and throughput. The Session appchain logic is based on the original Oxen blockchain.
{% endhint %}

In this way, the most expensive and frequent operations can occur in an appchain environment (where fees are lower). The appchain state is then snapshotted and returned to the EVM chain for validation and security purposes.

The Session Appchain is based on the original Oxen Blockchain, the first blockchain used by Session.


---

# Agent Instructions: 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://docs.getsession.org/session-network/session-nodes/session-appchain.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.