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
  • Single contributor nodes
  • Multicontributor nodes

Contribute to the Session Network

Last updated 5 days ago

The best way to participate in the Session Network is by operating or contributing to a Session Node. Nodes are responsible for securing and validating transactions and data (such as messages) for the Session Network. By operating or contributing to a Session Node, you contribute to essential infrastructure for the Session ecosystem—and help protect the security and privacy of the people using Session.

All Session Nodes are required to deposit (or ‘stake') a fixed amount of Session Tokens and run validator software to register on the network.

Single contributor nodes

Session Node operators manage the server (such as a VPS or home server) which runs the Session Node validator software. To run the software, the node will need to meet minimum hardware requirements. In a single contributor node, the node operator deposits the full stake required to register on the network.

Stakes can be deposited and managed using the .

Multicontributor nodes

If an operator does not have enough Session Tokens for a full stake (or does not wish to provide a full stake for some other reason), they can operate a multicontributor node. Multicontributor nodes allows for multiple to delegate their stake to a single node.

Stakes are still managed by the staking smart contract, and funds are not held by the operator.

Operators can set an operator fee on their multicontributor nodes, which is collected in SESH. This helps to cover operating costs of running a node. For example, if the operator sets a 10% operator fee, they will earn 10% of the SESH that would have been distributed to contributors. This mirrors how node operator fees will work on mainnet.

Staking Portal