As Session Token’s TGE draws closer, important details about Session Token, including the ticker, are now being locked in.

Since Session Token's announcement, there has been curiosity and discussion around the choice of ticker for the token. The ticker is an important choice for any crypto project—it can generate excitement, build an identity, and foster a culture of creation and participation in the token’s community.

Today it is being announced that the official ticker for Session Token will be SESH.

Why is SENT not an ideal ticker for Session Token?

Many testnet participants are familiar with the ticker SENT, which has been used as the ticker throughout the testnet phase. SENT was previously considered as a possible ticker for Session Token on mainnet. However, key drawbacks to SENT have emerged during this period, making it clear that a different ticker would be more suitable.

Unclear connection to the Session brand

As community members know, the launch of Session Token is a part of a broader effort to improve brand cohesion by strengthening the connection between the Session app and the network that powers it, currently branded as the Oxen network. While SENT is an acronym for ‘Session Network Token’, some community members have pointed out that this connection is not clear enough, particularly for new entrants learning about the Session ecosystem for the first time. In this regard, using SENT as the ticker would work against ongoing brand unification efforts.

Lack of clarity due to multiple meanings of the word ‘sent’

In addition to the link between SENT and Session being unclear, the word ‘sent’ has multiple meanings, resulting in a lack of clarity. The ticker (SENT) can be interpreted to mean the action of sending messages, which is relevant to Session as a messaging app to an extent, but it could also be interpreted to refer to the action of sending tokens, or anything else. SENT could also be confused with the word ‘cent’ (unit of currency), particularly in the context of non-native English speaking audiences.

In order to make the Session ecosystem accessible to a global audience, and to make a clear connection between the token and the messaging app, SESH has been chosen as the ticker for the reasons outlined below.

Why is SESH a better ticker for Session Token?

Although the ticker does not change Session Token’s fundamentals, it is an important part of building and defining the project’s identity. Tickers of projects with large, vibrant and engaged communities all share certain traits.

Qualities of effective project tickers 

Successful tickers are powerful communication tools that encapsulate a project's essence in just a few characters. A compelling ticker should be instantly recognizable and memorable, creating an immediate connection to the underlying project. It needs to resonate with the project's community members, both current and prospective. The most effective tickers transcend linguistic barriers, avoiding potential misinterpretations. Ultimately, an ideal ticker serves as a concise, powerful identifier for a project and its ecosystem.

Strengths of SESH as a ticker

In light of these factors, SESH emerged as the strongest choice: It's phonetically tied to "Session" as an abbreviation of the project's name, making it more memorable and recognizable. Unlike SENT, which can be confused with the action of sending a message or a unit of currency, SESH avoids ambiguity and is better suited for global audiences of non-native English speakers. The ticker has also gained clear support among Session Token community members, reflecting its organic appeal and resonance. Overall, SESH stands as the optimal ticker to support the success of Session Token and its broader ecosystem.

What will happen with my test SENT?

The test Session Token contract will be redeployed shortly with SESH as the ticker. This will allow testnet participants to get used to SESH. On the Staking Portal and in testnet documentation, references to SENT or test SENT will be replaced with test SESH as well. Until the contract has been relaunched, however, they will not be changed to avoid confusion.

When will the testnet Session Token contract be redeployed to change to SESH?

A final redeployment of the testnet Session Token contract is planned as part of the remaining preparations for mainnet. This will see Session Token deployed on the Ethereum Sepolia test network, to then be used on the Arbitrum Sepolia test network, simulating mainnet conditions where Session Token will be deployed on Ethereum mainnet for use on Arbitrum One mainnet. Up until now, the testnet token has been deployed solely on Arbitrum Sepolia.As part of this relaunch, a new Session Token contract will be deployed with the test token renamed to test SESH. The upgrade releasing this and other changes will commence tomorrow, Tuesday, January 14th, and conclude on Thursday, January 16th. For more information, please see the Session Token Discord.

Will my test SENT automatically change to SESH?

Your existing test SENT will not change its ticker automatically. Instead, the testnet Session Token contract will be redeployed, test SESH will be issued, and sent directly to the wallets of testnet participants. At that point, you will be able to import test SESH into your wallet, where it will display as SESH. You can then hide the old test SENT tokens, as you have likely done for previous token contract relaunches during testnet. Please visit the Session Token Discord for more information relevant to testnet participants.

I have further feedback or questions. Where do I share these?

Your feedback and input is always welcome. Please feel free to share any comments, concerns or questions via the Session Token Discord!