After many people stake their tokens, they usually just keep them in their wallet and leave them untouched, treating them as mere receipts.

The haWAL issued by the liquidity staking protocol on Sui is often treated like this too. In fact, it has more use cases. One of them is to provide it as liquidity for a pool—for example, pairs like haWAL/WAL or haWAL/SUI.

The logic behind this is that the haWAL obtained from staking WAL is already accumulating staking rewards. If you also put it into a pool so others can trade it, you can earn an additional share of transaction fees—effectively using the same asset to do two things at once.

This layered type of usage is more user-friendly for those who are already familiar with liquidity-provision mechanisms, because it adds another variable to pay attention to—the price fluctuation risk that liquidity provision itself carries.

For people who only want to stake and earn rewards, leaving it untouched is also perfectly fine. Whether to take this extra step depends on how much additional complexity you are willing to handle.

From an asset perspective, haWAL fundamentally has two roles at once: it functions as both a staked receipt token and a regular trading token. The former provides stable staking rewards, while the latter opens up the possibility of participating in various pools.

Understanding how these two identities coexist helps you see more clearly what role haWAL can actually play within the entire ecosystem, rather than simply treating it as a static receipt token.