Kintsu - Liquid Staking on Monad

Kintsu

• Introduction: Welcome to Kintsu!
• Proof-of-Stake Blockchains
• Liquid Staking
• Kintsu on Monad
• Kintsu on Hyperliquid
• How It Works: Protocol Architecture & Functionality
• Staking and Unstaking with Kintsu: How to Stake, Un-stake, and earn yield with Kintsu
• Earning Yield: How Kintsu's reward-bearing sMON token facilitates yield back to stakers.
• Definitions: Terminology for the Kintsu Protocol
• Architecture & Integration: Technical architecture, core pieces, and system processes of Kintsu on Aleph Zero
• Monad LST Architecture
• StakedMonad Contract: This is the core contract for the protocol, and implements the Vault (a.k.a. the Kintsu stake pool).
• Staking and Un-staking Mechanisms: What happens behind the scenes when a user stakes or unstakes with Kintsu
• 3rd Party Integration Guide
• Contract Interface, ABI, & Functions: Details on select functions, including previous versions when relevant.
• Community Actions
• Hyperliquid LST Architecture
• StakedHype Contract: This is the core contract for the protocol on HyperEVM, and implements the Kintsu Vault (a.k.a. the Kintsu stake pool on Hyperliquid).
• Staking and Un-staking Mechanisms: What happens behind the scenes when a user stakes or unstakes with Kintsu
• 3rd Party Integration Guide
• Contract Interface, ABI, & Functions: Details on select functions, along with the full StakedHype contract interface.
• Community Actions
• DAO & Governance
• Governance Activities & Participation
• Official Contract Addresses
• Points
• APY
• Community & Social Media
• Contribute to Open Source
• Hackathons and Meetups
• Our Philosophy: The team, mission, and values
• Why We Build: The motivation
• FAQs
• Bug Reports
• Feature Requests
• Support

Agent Instructions: Querying This Documentation

If you need additional information, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on a page URL with the ask query parameter:

GET https://docs.kintsu.xyz/overview/introduction.md?ask=<question>

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.