LogoLogo
Back to our website
  • Session Messenger
    • Installing Session
      • Installing on Linux (Debian based distros)
      • Installing Session using F-Droid
      • Installing Session using APKs
      • Installing beta versions of Session
    • Advanced Features
      • Communities
        • How to setup a Session Open Group Server (SOGS)
        • Creating a read-only channel using SOGS
      • Session Names and the Session Name Service (SNS)
        • Registering an Oxen Name using the Oxen Name Service
      • Session Pro
    • Contribute to Session Messenger
      • Development
      • Localization
  • Session Token (SESH)
    • Tokenomics
      • Genesis tokenomics
    • Rewards Programs
      • Service Node Bonus Program
      • Oxen Coin Claims
      • Testnet Incentive Program
    • Get Session Token (SESH)
      • How to create a crypto wallet
      • How to view SESH in your Wallet
      • How to use Session Token (SESH)
  • Session Network
    • Session Nodes
      • Staking and collateralization
      • Incentivization
      • Consensus
      • Swarms
      • Session Appchain
      • Deregistration
    • Session Protocol
      • Onion requests and message routing
      • Account IDs and self managed keys
      • Account restoration
    • Staking
      • Staking Reward Pool
  • Contribute to the Session Network
    • Frequently Asked Questions (FAQ)
    • Testnet
      • Staking to a Session Stagenet Multicontributor Node
      • Session Stagenet Node Setup
        • How to set up an oxend L2 proxy
  • Twitter / X
  • Discord
  • Session Token Website
  • Session Website
  • Session Whitepaper
Powered by GitBook
On this page
  1. Session Network
  2. Session Nodes

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.

Appchains are specialized, app-specific blockchains built to increase scalability and throughput. The Session appchain logic is based on the original Oxen blockchain.

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.

Last updated 15 days ago