Oxen Landing Hardfork (11.3.0) Activation and Session Token TGE

Thank you to all operators who participated in the Landing Hardfork! The Hardfork is complete, and the Oxen Network has officially migrated to the new Session Network. 

OXEN>SESH Coin Claims Portal

OXEN holders can now swap their OXEN for SESH via the Coin Claims Portal here. The Portal provides two ways to migrate your OXEN.

OXEN>SESH on the Arbitrum One Network (these tokens can be staked to the Session Network straight away)

wOXEN>SESH on the Ethereum Network (these tokens will subsequently need to be bridged to the Arbitrum One Network to be staked on the new Session Network)

The conversion rate from OXEN to SESH is 1 OXEN = 0.54 SESH

The conversion rate has been determined based on the circulating supply of Oxen at the time of the Session Token TGE, excluding the OPTF’s Oxen balance and accounting for an estimated portion of tokens likely to remain unclaimed. With 30,000,000 Session tokens allocated to the Oxen Coin claims Program, this analysis supports a conversion rate of 1 OXEN = 0.54 SESH. This rate is designed to ensure a fair and equitable migration of Oxen holders to the Session network.

Although this program will run indefinitely, after 6 months the conversion rate will decrease from 1 Oxen = 0.54 SESH to 1 Oxen = 0.37 SESH, a 30% decrease, to encourage Oxen holders to convert their Oxen to SESH within the first 6 months. The portion of the 30,000,000 Session Tokens which are unclaimable after the multiplier decreases will be automatically reserved for future node rewards. Learn more here. 

How to use the Oxen Coin Claims Portal

1. Head to https://claim.oxen.io/ and select whether you want to convert OXEN>SESH (on Arbitrum) or wOXEN>SESH (on Ethereum)

2. For OXEN>SESH, enter your Arbitrum wallet address or connect your wallet, then follow the instructions to send your OXEN to the indicated OXEN address. You'll then see a pending transaction on the page (refresh the page if it doesn't appear). Once the transaction is confirmed SESH will be sent to your provided Arbitrum wallet address. This may take around 20 minutes.

3. For wOXEN>SESH, connect your Ethereum wallet and follow the instructions to approve your wOXEN to swap, then approve the swap via the popups in your wallet.

To view SESH in your wallet, follow this guide.

Service Node Migration

If you were registered for the Service Node Bonus program, your staked OXEN has now been automatically swapped for SESH, and you have also been allocated SESH based on your Bonus points. Based on your SESH allocation, nodes you were running or staking to may or may not have been restaked on the Session Network. You can check if your node was restaked by connecting your wallet to the Staking Portal and check your My Stakes page for active nodes. If your node wasn’t restaked, you’ll see your unlocked SESH ready for you to claim under “Unclaimed Rewards”, also on the My Stakes page. How to claim your excess SESH from the Staking Portal

1. Head to https://stake.getsession.org/mystakes and connect your wallet that you were signed up to the Service Node Bonus Program with. Make sure your wallet is on the Arbitrum One network, not Ethereum.

2. If you have excess SESH*, you'll see it under Unclaimed Rewards on your My Stakes page

3. Hit the 🎁 Claim button and approve the claim via the popups in your wallet.

*Excess SESH is comprised of SESH converted from your staked OXEN, and SESH you earned from the Service Node Bonus Program that was not able to be restaked to a node during the migration. If you don't have excess SESH to claim, but you do have Active Nodes on your My Stakes page, this means all your nodes were restaked successfully!

Network-Wide SESH Claims Limit 

For users who have migrated their staked OXEN—as you may already know, any excess SESH that does not get restaked to a node on the Session Network will be unlocked and claimable from the Staking Portal as staking rewards. Please note that across the entire network, up to 1M SESH can be claimed every 12 hours. This is a security measure to protect against exploits. 

If you attempt to claim SESH and the limit has been exceeded, you will be notified in the Portal with a countdown for when you can return to the Portal to claim, once the 12 hour period has reset. Learn more here. 

How-to Guides 

Full guides for how to stake to and run nodes on the mainnet Session Network are now available. Please take some time to familiarize yourself with the steps and requirements.

Learn how to stake to a node here.

Learn how to run a node here.

For operators, additional documentation on optimally configuring L2 tracker settings based on your individual Arbitrum RPC provider has been added here.

Official Contract Addresses, Links and Handles

Please be wary of scams and phishing attacks during the TGE period. Always double check contract addresses, URLs and social media handles for your safety. 

SESH Token Contract:  0x10Ea9E5303670331Bdddfa66A4cEA47dae4fcF3b (on both Arbitrum One and Ethereum) 

Service Node Rewards Contract:  0xC2B9fC251aC068763EbDfdecc792E3352E351c00

Reward Rate Pool Contract:  0x11f040E89dFAbBA9070FFE6145E914AC68DbFea0

Service Node Contribution Factory Contract:  0x8129bE2D5eF7ACd39483C19F28DE86b7EF19DBCA Uniswap Pool (Ethereum): https://app.uniswap.org/explore/pools/ethereum/0x249afd31a49d9bd44259b8f03dd74030d7d41153bc891d12f469c5cb94b03729

Uniswap Pool (Arbitrum): https://app.uniswap.org/explore/pools/arbitrum/0x249afd31a49d9bd44259b8f03dd74030d7d41153bc891d12f469c5cb94b03729

Session Token website: https://token.getsession.org/ 

Session Token on X: https://twitter.com/session_token 

Session Staking Portal: https://stake.getsession.org/ 

Oxen website: http://oxen.io/ 

Oxen on X: https://x.com/oxen_io 

Session Token Discord: https://discord.gg/sessiontoken 

Session contributors will NEVER DM you on Telegram, Session, Discord or Twitter. When joining Discord, you are recommended to turn your DMs off. 

Support

The fastest way to access support for running and staking to nodes, along with for the Coin Claims Program, will be via the Session Token Discord. Please open a ticket so that a Session contributor can assist you.