A new Swiss foundation—the Session Technology Foundation—has been created for the ongoing stewardship of Session and to contribute to the Session ecosystem through development, education, grant-making, and advocacy.

Learn more here.

Session Token is planned to launch between February 5, 2025 to March 20, 2025 to ensure migration readiness and ecosystem sustainability.

Some Oxen service node operators and contributors have voiced a preference both for an earlier TGE date and clarity on a fixed timeline. This sentiment is entirely reasonable, considering their long-term commitment to Session and ongoing participation in the Oxen Service Node Bonus Program. In addition, the past timeline adjustments, from Q2 2024 to 2024, and now to February-March 2025, have left Oxen stakeholders feeling uncertain and frustrated.

While the goal has always been to provide clear timelines to stakeholders, the evolving requirements of the network migration now mean that flexibility is necessary to ensure both stability and sustainability for the Session ecosystem both at and after TGE.

Read this Session Token blog to find out:

- Which factors have made a launch in February-March 2025, rather than 2024, necessary?

- Why can’t TGE happen before the migration from Oxen to the new Session Network?

- Why can’t you give a more specific date for TGE beyond the February 5 - March 20 timeframe?

- What are the benefits to launching in February-March 2025?

- What does a February-March 2025 TGE mean for stakers in the Oxen Service Node Bonus Program?

Learn more here: https://token.getsession.org/blog/tge-timeline-update

👇 Important Information for Oxen Service Node Bonus Program Participants👇

To ensure that early participants in the Oxen Service Node Bonus program retain their advantage, daily points will be adjusted from 800 points per day to 700 points per day per active node. This adjustment supports the planned February-March 2025 TGE timeline, helping to sustain the benefits for those who joined the program early.

As a reminder, participation in testnet is the best way to prepare for TGE. The majority of mainnet features, including multicontributor nodes, have been launched on testnet, along with a bonus for operators running multicontributor nodes and a referral program.

Thank you for your continued support. All questions, comments, feedback are welcome.

📢 Announcement: Oxen Service Node Bonus Program Update

Hi everyone,

The daily points for the Oxen Service Node Bonus program have been adjusted to align with a February-March TGE for Session Token.

Following feedback from operators who felt that a reduction from 800 to 700 points would be too modest, the daily points have instead been reduced from 800 to 600.

This adjustment took effect at 4:00 PM UTC on November 18, 2024, at block height 1720078.

A non-mandatory Oxen Service Node update is now available to operators.

This update is optional but recommended, as it includes important bug fixes to address issues that Service Nodes have recently encountered.

Click below to learn more 👇

https://oxen.io/blog/non-mandatory-service-node-upgrade-now-available

🔊 Announcement 🔊

As TGE draws closer, many things are falling into place and being finalised, including Session Token's official ticker 👀

The official ticker for Session Token will be $SESH.

SESH is a simple abbreviation of Session, which is instantly recognisable as such to a global audience, and has been a popular option in the Session Token community.

Learn more 👇

https://token.getsession.org/blog/official-ticker-sesh

Big news today guys!

The journey to mainnet has taken an important step forward with a date now set for the Anchor Hardfork. The packages will be released on Feb 18th and the hardfork will occur on Feb 25th. This is the first technical step in the migration from Oxen to Session Token, and it will begin to prepare the Service Node network for the migration through changes like the ability to witness the Arbitrum blockchain and generating / publishing BLS keys.

New Service Node registrations will be disabled, and active nodes will be snapshotted to seed the initial Session Nodes on Arbitrum. Operators in the Bonus Program who upgrade before the hardfork will have their Oxen automatically swapped for Session Tokens, making them the first-ever mainnet Session Node operators.

Things are heating up, and the countdown to launch is officially on 🎉

This hardfork is very different to all previous hardforks, so make sure to read the blog here 👇

https://oxen.io/blog/oxen-anchor-hardfork-11-1-0

Oxen is announcing changes to the rollout of Oxen Anchor (11.2.0) Hardfork. An additional point release (version 11.1.0) will be released in advance of the Anchor Hardfork release.

Oxen 11.1.0 is a non-mandatory upgrade scheduled for release on Tuesday February 25.

The decision to add the Oxen 11.1.0 release has been made out of caution due to the Anchor Hardfork disabling new Service Node registrations. This point release offers the opportunity to verify the proper function of new features in the Oxen mainnet environment without disabling new Service Node registrations, providing more flexibility for both Session Contributors and the Oxen community.

The release date of Oxen 11.2.0 (Anchor Hardfork) is pending the success of the migration candidate (Oxen 11.1.0). Currently, the release and live testing of 11.1.0 is taken to be part of the testing allowance which was originally scheduled for the period before the Landing Hardfork.

More details can be found in the full announcement, here: https://oxen.io/blog/anchor-hardfork-update-new-point-release

Oxen 11.1.0 Is Now Live ⚡️

A new point release for Oxen Service Node operators, Oxen 11.1.0, is now available. This non-mandatory update includes all planned features from the upcoming Anchor Hardfork (11.2.0). It allows live testing on mainnet while keeping Service Node registrations open.

This release also improves L2 request caching, reduces memory usage, and fixes slow chain rescans that could cause node deregistration.

While not mandatory, it's strongly encouraged as it allows operators to experiment with new features, such as connecting to an Arbitrum One RPC node, before they become strict requirements following the Anchor Hardfork.

Hey everyone, a non-mandatory upgrade (11.1.2) has been released!

Based on the earlier snapshot build, this release enables oxend to proxy requests to an L2 provider. This is aimed in particular at people planning to run multiple nodes on the Session Network after the migration.

This feature works by having only 2-3 of your nodes configured with an L2 provider URL, and having all the others configured to talk to those 2-3 nodes to get Arbitrum updates, without having to use multiple or paid tier accounts for your set of nodes.

Please note that this feature works through the existing oxen "quorumnet" port, and so does not need to open additional ports, but it does require some one-time configuration.

Once you've upgraded, check out this guide on how to get set up here: https://docs.getsession.org/user-guides/session-stagenet-node-setup/how-to-set-up-an-oxend-l2-proxy

Hey everyone,

The Session Technology Foundation’s partnership with Legion was publicly announced today!

https://x.com/session_token/status/1903004952999661837

Incubated by Delphi Labs, Legion is a merit-based platform that is rapidly disrupting the way that projects curate and grow their communities in crypto.

Other projects that partnered with Legion recently include DePIN projects Pulse and Silencio, Ethereum L2s =nil; and Fuel, the decentralized key management network Lit Protocol, and the interoperability network Hyperlane, among several other leading crypto projects. So Session will be in great company!

To learn more about Legion and its mission, check out their whitepaper here.

Oxen community members can join the SESH community on Legion using this private referral link.

Disclaimer: Not for UK Persons

Hey everyone, here are some important updates about the upcoming TGE. In this blog, you’ll find the latest on:

- Session’s strategic partnership with Legion + key dates

- Full transparency on the reasons behind TGE timeline adjustments

- Critical hardfork dates you need to know

Check it out here.

Hey everyone, the software upgrade for the Anchor Hardfork (11.2.0) was released today. You have 7 days to complete the upgrade.

The Anchor Hardfork will be activated on Tuesday April 29th, 00:00 UTC at block height 1836239, after which no new service nodes will be able to register to the Oxen Network.

Information and guide for completing this upgrade: https://oxen.io/blog/oxen-anchor-hardfork-11-2-0

Migration checklist for node operators:
https://docs.oxen.io/oxen-docs/using-the-oxen-blockchain/migrating-to-the-new-session-network/migration-checklist

Migration FAQ:
https://docs.oxen.io/oxen-docs/using-the-oxen-blockchain/migrating-to-the-new-session-network/migration-faq

Hey everyone, while some operators have been able to upgrade to 11.2.0 successfully, some operators have reported issues upgrading.

To minimize the risk of nodes getting decommissioned or deregistered we recommend not upgrading for the time being. We are investigating these issues and hope to have a fix pushed by tomorrow.

If you have upgraded successfully and your node is sending uptime proofs and is reachable, no need to do anything right now. If you have already upgraded and are running into issues, please flag these issues the Service Node / Migration channels on Discord or Telegram.

Thanks for your patience as we resolve this! A progress update will be shared tomorrow.

Hey everyone,

Thank you for your patience - the issue has been resolved and fixes have been pushed 🎉

If you haven't upgraded your Service Node, you can now safely upgrade to 11.2.0. Just make sure to pull down the latest packages from deb.oxen.io again before upgrading, this can be done by running "sudo apt update"

If you have previously successfully upgraded to 11.2.0, you don't need to take any further action.

Please note that in some cases, the upgrade can take several minutes because of a necessary rescan of recent block states, depending on what version you were on before upgrading!

The Anchor Hardfork will not be delayed. It will still be activated on Tuesday April 29th, 00:00 UTC at block height 1836239.

Please be sure to upgrade as soon as possible!

Hey everyone,

With the SESH TGE upcoming, please note that the OXEN<>wOXEN bridge will be disabled on Monday, May 19th. If you're currently holding wOXEN, don't worry, you'll still be able to convert this to SESH on Ethereum via the Coin Claims bridge on TGE!

Thanks!

Hi everyone,

Everything is on track for TGE tomorrow! Here are some last details you need to know for the day:

TGE Timing
Currently, TGE is estimated to take place approximately between 00:00 UTC-02:00 UTC, May 21st. However the timing may change as the technical steps roll out.

OXEN>SESH Coin Claims Portal
The link to the OXEN>SESH (Arbitrum One) and wOXEN>SESH Ethereum Coin Claims Portal will be announced across all Oxen channels tomorrow, and you will also find it on this page: https://token.getsession.org/oxen-coin-claims

Network-Wide SESH Claims Limit
For users who are migrating 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 (https://stake.getsession.org/) 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: https://docs.getsession.org/contribute-to-the-session-network/frequently-asked-questions-faq#network-claims-limit

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

Staking to a node:
https://docs.getsession.org/contribute-to-the-session-network/staking-to-a-session-node

Running a node:
https://docs.getsession.org/contribute-to-the-session-network/running-a-session-node

For operators, additional documentation on optimally configuring L2 tracker settings based on your individual Arbitrum RPC provider has been added here: https://docs.getsession.org/contribute-to-the-session-network/running-a-session-node/oxend-l2-tracker-tuning

The fastest way to access support for running and staking to nodes, and for the Coin Claims Portal, will be via the Session Token Discord: https://discord.gg/sessiontoken

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 (for both Ethereum and Arbitrum One)

Service Node Rewards Contract:
0xC2B9fC251aC068763EbDfdecc792E3352E351c00

Reward Rate Pool Contract:
0x11f040E89dFAbBA9070FFE6145E914AC68DbFea0

Service Node Contribution Factory Contract:
0x8129bE2D5eF7ACd39483C19F28DE86b7EF19DBCA

Session Token website: https://token.getsession.org/
Session Token on X: https://twitter.com/session_token
Session Staking Portal: https://stake.getsession.org/
Session Observer: https://session.observer/
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.

Hey everyone,

The Landing Hardfork (11.3.0) has been activated and Session Token (SESH) is now live!

👉 Ethereum Uniswap Pool: https://app.uniswap.org/explore/pools/ethereum/0x249afd31a49d9bd44259b8f03dd74030d7d41153bc891d12f469c5cb94b03729

👉 Arbitrum One Uniswap Pool: https://app.uniswap.org/explore/pools/arbitrum/0x249afd31a49d9bd44259b8f03dd74030d7d41153bc891d12f469c5cb94b03729

⚠️ Please note:
Due to an issue with the Claims function in the Session Staking Portal, this feature has been disabled. There is currently an issue with BLS signatures and 'zombie nodes', where these decomissioned nodes are being requested to provide signatures when they shouldn't be. A fix is under development right now.

Because Oxen stakers cannot claim their unlocked SESH at the moment, the Oxen Coin Claims Portal has also been temporarily disabled, as this would otherwise give unfair early access to SESH claims.

Claiming excess SESH via the Staking Portal and claiming SESH via the Oxen Coin Claims Portal are both planned to be enabled ASAP tomorrow.

Although claiming SESH is disabled, the Session Staking Portal is live and can be used to register and stake nodes on the Session Network: https://stake.getsession.org/

Follow these guides to register and stake to nodes:
https://docs.getsession.org/contribute-to-the-session-network
https://docs.getsession.org/contribute-to-the-session-network/staking-to-a-session-node

Decommissioned Nodes
Some operators would have received a status that their node "Did not transition at HF21". While in some cases, this could be due to an issue with the node, in other cases it means that there was not sufficient SESH for this node to be restaked on the new Session Network. This can be due to several reasons, including insufficient SESH earned from the Service Node Bonus Program due to later participation or downtime, and/or due to a contributor not being registered for the Bonus program and their stake not being converted to SESH. These 'zombie nodes' with insufficient SESH are gradually being removed from the Network and won't be able to be brought back online. The OxenSNBot will be updated to make it clearer whether a node was decomissioned due to insufficient SESH or due to another issue.

You can check if your node was successfully restaked in the migration by connecting your Ethereum wallet to the Staking Portal and checking on your My Stakes page for your Active Nodes.

https://stake.getsession.org/mystakes

If your node was not restaked, all your OXEN (from your stake and Bonus points) has been automatically swapped for SESH, which you will be able to claim as soon as this function is enabled on the Staking Portal ASAP tomorrow after a fix has been implemented for the issue, as mentioned above.

Learn more: https://docs.oxen.io/oxen-docs/using-the-oxen-blockchain/migrating-to-the-new-session-network/migration-faq

Contract Addresses
Please be wary of scams during this TGE period! Ensure that you're only interacting with the below smart contract addresses.

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

Service Node Rewards Contract:
0xC2B9fC251aC068763EbDfdecc792E3352E351c00

Reward Rate Pool Contract:
0x11f040E89dFAbBA9070FFE6145E914AC68DbFea0

Service Node Contribution Factory Contract:
0x8129bE2D5eF7ACd39483C19F28DE86b7EF19DBCA

Hey everyone,

The Oxen Coin Claims Portal and claiming SESH via the Staking Portal are now available! Thank you for your patience as the issue affecting BLS signatures yesterday was resolved.

As a reminder, both SESH that is converted manually via the Oxen Coin Claims Portal and excess SESH that was converted automatically as part of the node migration have the same conversion rate:

1 OXEN = 0.54 SESH

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.,

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,

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!

How to move SESH from Arbitrum to Ethereum and vice versa
To bridge SESH between the Arbitrum One and Ethereum Networks, you must only use the official Arbitrum bridge https://bridge.arbitrum.io/. Using another bridge could lead to you having another kind of wrapped token which will not be compatible with the Arbitrum and Ethereum Uniswap pools

Now that the migration from the Oxen Network to the new Session Network is complete, this community has been renamed to Session Network Announcements. Session contributors will use this community to share regular updates on the Session Network and Session Token ($SESH).