> For the complete documentation index, see [llms.txt](https://docs.stakestone.io/stakestone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stakestone.io/stakestone/stone-eth/how-it-works.md). # How It Works #### Overview STONE is a non-rebase ERC-20 token that operates similarly to Lido's wstETH in terms of yield generation. As a non-rebase token, the numerical balance of STONE in your wallet remains constant; however, its intrinsic value in ETH increases over time due to accumulated staking yields. For example, if user A deposits 100 ETH for 100 STONE, and after one year, the value of 1 STONE rises to 1.04 ETH, the user can withdraw 104 ETH from StakeStone using their 100 STONE. The price of STONE is determined by the smart contract and is not influenced by DEX prices or information platforms like CoinGecko. This contract-based price is used for both deposits and withdrawals, ensuring users can always redeem their ETH according to the current STONE price in the contract. Users can view the STONE price for deposits and withdrawals on [StakeStone's dApp](https://app.stakestone.io/u/stake). Additionally, STONE is an Omnichain Fungible Token (OFT) built on LayerZero, allowing it to be seamlessly bridged across different chains. StakeStone leverages LayerZero’s solutions to develop customized contracts, enhancing STONE’s cross-chain compatibility. The upcoming mainnet will utilize Polyhedra and zkBridge for bridging STONE accumulated within the Bitcoin ecosystem, further expanding our interoperability and usability. **STONE’s address** Ethereum Mainnet: 0x7122985656e38BDC0302Db86685bb972b145bD3C Manta Pacific: 0xEc901DA9c68E90798BbBb74c11406A32A70652C3 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.stakestone.io/stakestone/stone-eth/how-it-works.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.