> For the complete documentation index, see [llms.txt](https://docs.kintsu.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kintsu.xyz/the-kintsu-protocol/architecture-and-integration/hyperliquid-lst-architecture/community-actions.md).

# Community Actions

## Compounding

Hyperliquid staking protocol auto-compounds the accrued yield on HyperCore. To reflect this change in the Vault (on HyperEVM) and thereby update the [Redemption Ratio](/the-kintsu-protocol/definitions.md), Anyone can execute the [syncStaking()](/the-kintsu-protocol/architecture-and-integration/hyperliquid-lst-architecture/contract-interface-abi-and-functions.md#condensed-stakedhype-contract-interface) call to sync the state with HyperCore.

{% hint style="info" %}
The Vault uses the `L1Read` module to read HyperCore state from the HyperEVM.
{% endhint %}

## Submit Batch

Anyone can execute the [submitBatch()](/the-kintsu-protocol/architecture-and-integration/hyperliquid-lst-architecture/contract-interface-abi-and-functions.md#condensed-stakedhype-contract-interface) call to send the pending stake/unstake request(s) stored in the Vault to the HyperCore for processing. 

{% hint style="info" %}
The Vault uses the `CoreWriter` module for HyperCore <> HyperEVM interaction.
{% endhint %}

## Transfer spot balance from HyperCore to Vault

Anyone can execute the [sweep()](/the-kintsu-protocol/architecture-and-integration/hyperliquid-lst-architecture/contract-interface-abi-and-functions.md#condensed-stakedhype-contract-interface) call to transfer the unstaked funds that have completed the unbonding cooldown period from HyperCore to the Vault (on HyperEVM).


---

# 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.kintsu.xyz/the-kintsu-protocol/architecture-and-integration/hyperliquid-lst-architecture/community-actions.md?ask=<question>&goal=<endgoal>
```

`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.