> For the complete documentation index, see [llms.txt](https://docs.gigaeth.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gigaeth.org/readme.md). # Why GigaETH ## Introduction *Why DeFi’s next phase is not about yield, but about making yield usable.* DeFi succeeded at proving a point and failed at becoming a product. Over the last cycle, decentralized finance built an extraordinary amount of technical infrastructure: automated market makers, lending markets, liquid staking, restaking, synthetic assets. Capital became programmable, permissionless, and globally accessible. Yet for the majority of users, none of this translated into something that felt like money. DeFi produced yield, but it did not produce **spendability**. This gap is not accidental. Traditional DeFi was architected around protocols, not people. Users were expected to understand wrappers, bridges, chains, staking derivatives, collateral ratios, liquidation thresholds, and governance risk. The burden of integration was pushed onto the user. As a result, DeFi became powerful but brittle, lucrative but unusable outside of speculative loops. GigaETH starts from a different premise: **yield-bearing capital should behave like money**. Today, hundreds of billions of dollars’ worth of ETH-derived assets exist in the form of liquid staking tokens and their variants. These assets represent productive, yield-generating capital secured by Ethereum consensus. But they are fragmented across chains, protocols, and wrappers. To a retail user, sETH, wETH, pETH, restaked ETH, and their derivatives are indistinguishable abstractions with incompatible rules. To institutions, they are balance-sheet assets that cannot be operationalized for payments without complex risk and custody assumptions. The result is dead capital. Valuable, productive, but locked behind UX and integration walls. GigaETH is built to collapse this complexity into a single, coherent endpoint. It treats liquid staking tokens not as niche DeFi instruments, but as **monetary infrastructure**. Assets that already generate yield should not require users to unwind positions, exit DeFi, or re-enter centralized rails just to spend value in the real world. The deeper insight is this: payments are not an add-on to DeFi. They are the forcing function that exposes its weaknesses. Lending protocols stop at “borrow”. Staking protocols stop at “yield”. Wallets stop at “hold”. None complete the loop from productive capital to everyday economic activity. GigaETH completes that loop. By unifying heterogeneous liquid staking assets into a single borrowing and payments surface, GigaETH allows users to retain yield exposure while accessing canonical ETH or USD-denominated liquidity for real-world spending. No manual unwinding. No chain-specific reasoning. No protocol-hopping. --- # 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.gigaeth.org/readme.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.