# Sessionchains Our innovative approach to scalability is encapsulated in what we call **Sessionchains**. These are transient, ephemeral chains built upon the Sovrun platform. The primary function of these Sessionchains is to facilitate the **execution of logic that doesn't require long-term storage or persistence**. This characteristic makes them ideal for the dynamic environments of various Autonomous Worlds or DApps, which might frequently need computation without the overhead of enduring data retention. These are issues preventing the growth and innovation of the fully onchain gaming space. By offloading such tasks to our Sessionchains, we ensure that processes are both efficient and scalable, allowing for rapid implementation and execution in scenarios where longevity of data is unnecessary. This design choice reflects our commitment to providing scalable solutions that are both flexible and powerful, enhancing the overall efficiency of the systems they serve. Sessionchains can be spun up by **staking SOVRN**, after which a chain deployer can initiate the instantiation process via smart contract interaction. Chain deployment itself will be abstracted away from the end user by Sovrun Labs, and will come predeployed with the necessary tools to build Autonomous Worlds. *** Sessionchains will be released for Public Beta in Q1 2025. To participate in the Closed Beta (on testnet), please sign up via this [form](https://airtable.com/appXBtIEe0QlgL9A6/pagqS1GfDK5xi7IB5/form). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.sovrun.org/the-sovrn-token/usdsovrn-on-evm-chains/hyperliquid/sessionchains.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.