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
  • Session Node states
  • Decommissioned nodes and credits
  • Quorums tests
  • State change transactions
  1. Session Network
  2. Session Nodes

Deregistration

The Session Network uses deregistration rules to enforce standards of node performance in a decentralized way. This ensure all operational Session Nodes are up to date and performing adequately to maintain the network.

Session Node states

Session Nodes have four different states: awaiting, active, decommissioned or deregistered.

State
Description

Awaiting

Active

Session Node is staked, performing tasks as required, and receiving rewards.

Decommissioned

Session Node is not performing tasks as required or is not meeting uptime standards, and has been placed into an inactive state. Decommissioned nodes do not earn rewards.

Deregistered

Session Node has been inactive (decommissioned) for too long, and has been deregistered from the network.

Decommissioned nodes and credits

Session Nodes have "credits" which determine how long a node may remain inactive (decommissioned) before being deregistered from the network. These credits are used during any time period where the Session Node is offline (or otherwise stops meeting network requirements).

A new node starts out with INITIAL_CREDIT, and then builds up CREDIT_PER_DAY for each day the it remains active, up to a maximum of DECOMMISSION_MAX_CREDIT.

INITIAL_CREDIT

60 blocks (~2 hours) of decommission time.

CREDIT_PER_DAY

24 blocks (~0.8 hours) of decommission time.

DECOMMISSION_MAX_CREDIT

1440 blocks (~48 hours) of decommission time.

MINIMUM

60 blocks(~2 hours) of decommission time.

Example:

If an Session Node stops sending uptime proofs, a quorum of service nodes will analyze whether the node has built up enough credits (at least MINIMUM). If so, instead of submitting a deregistration, the quorum instead submits a decommission, removing the node from the list of active Session Nodes. While decommissioned, the node does not receive rewards or participate in active network duties.

If the Session Node node comes back online (i.e. starts sending the required performance proofs again) before its credits run out, a quorum will reinstate the node using a recommission transaction. This transaction adds the Session Node back to the reward list and resets the node's accumulated credits to 0.

If the Session Node does not come back online within the required number of blocks (i.e. if the node does not come back online and begin performing as required before its credits are depleted), then a quorum will send a permanent deregistration transaction to the network, locking that node's stake for 30 days.

Quorums tests

Uptime Proofs

Checks if a node has provided uptime proofs within the last 2 hours. If the node has not provided uptime proofs, but it has at least MINIMUM credits, it will be decommissioned. If it does not have at least MINIMUM credits, it will be directly deregistered.

IP Changes

Checks if a Session Node has broadcast more than one IP to the network in the last 24 hours. If a service node's IP has changed, it will be forced to the bottom of the reward list.

Checkpointing

Checks if each Session Node within the quorum has provided a hash of a block for a specific block height. If a node within the quorum does not provide a hash, but it has at least MINIMUM credits, it will be decommissioned. If it does not have at least MINIMUM credits, it will be directly deregistered.

State change transactions

State change transaction change the state of a Session Node. Typically, state change transactions are created when a quorum comes to a consensus about a given node's activities (or lack thereof).

The only state change transaction that can be created by any indivdual node is the Register transaction, which changes the state of a service node from awaiting to active.

State_Change_Transaction
Description

Register TX

A transaction created from the staking portal registering the Session Node.

State Change: Awaiting -> Active

Note: This is not a quorum transaction.

Decommission TX

Node is made inactive; it remains in the service node list, but is removed from the rewards list and from any network duties.

State Change: Active -> Decommissioned

Recommission TX

Node is added back to the Session Node list and placed at the bottom of the rewards list.

Stage Change: Decommissioned -> Active

IP Change TX

Node is pushed to the bottom of the rewards list as punishment for changing its IP.

Stage Change: N/A (no change)

Deregister TX

Node is deregistered from the network.

State Change: Active -> Deregistered / Decommissioned -> Deregistered

Last updated 15 hours ago

Session Node is awaiting the required of Session Tokens.

stake