Owning SAUCE: Uses, Storage and Risks

SAUCE is SaucerSwap’s governance and rewards token. If you hold it, you may be able to vote in the SaucerSwap DAO on proposals such as protocol changes and incentive settings. The token is also used to incentivize liquidity in SaucerSwap V1 and V2, with rewards managed by a Masterchef smart contract.

SaucerSwap says holders can stake SAUCE to receive a share of trading fees, HBAR staking rewards and emissions through an automated buyback mechanism. These are variable protocol rewards, not guaranteed income: their value can change, and staking may involve smart-contract and withdrawal risks. Check the current terms and how rewards are calculated before committing tokens.

SAUCE is not the same as HBAR, Hedera’s native token. Holding SAUCE gives you exposure to SaucerSwap’s governance and reward mechanisms, but it does not give you ownership of the exchange or a claim on a fixed amount of revenue.

SAUCE is issued on Hedera and Base; it is not listed as the native token of either network. Check which network your SAUCE is on before you send it, connect a wallet or use a trading venue. A transfer to the wrong network or an unsupported wallet may leave tokens inaccessible. Hedera and Base use different token formats and addresses, so do not assume an address or token listing works across both.

Choose a wallet that explicitly supports the relevant network and token. SaucerSwap Wallet is described as a self-custody wallet for HBAR and Hedera tokens, with keys kept on your device. Confirm that it supports the specific SAUCE token you hold; for Base, use a wallet that supports Base and verify the token contract before adding it. Keep your recovery phrase offline, and never share it with a site or person claiming to help you claim rewards.

As of 2026-11-08, SAUCE has a maximum and total supply of 1 billion tokens, with about 929.9 million in circulation. That leaves roughly 70.1 million outside the reported circulating supply. The figures describe token supply, not how much is actively traded or available to buy.

A fixed maximum can help you understand the limit on reported supply, but it does not tell you who holds the tokens, whether any are locked, or when non-circulating tokens could enter circulation. SaucerSwap uses SAUCE emissions as part of its staking and liquidity incentives, so check the project’s current token and reward disclosures if supply distribution matters to your decision. Do not treat the maximum supply as a price floor or as evidence that demand will rise.

For a small holding, use a wallet that supports SAUCE on the network where your tokens are held. For a larger balance, consider a hardware wallet if it supports that network and token. Before sending, verify the receiving address, network and token identifier, then make a small test transfer if the amount justifies the extra transaction cost.

Keep your recovery phrase and private keys offline and private. Do not enter them into a website, share them with support staff or store them in a screenshot or cloud note. Bookmarking a legitimate app is safer than following unsolicited links, and you should check an app’s publisher before installing it. Be cautious with token approvals: a malicious or compromised contract may use permissions you granted to move assets. Revoke approvals you no longer need using a trusted tool, and remember that revocation itself may require a network transaction.

SAUCE can lose value sharply, and its price may not track SaucerSwap’s activity or the value of rewards. Liquidity provision adds separate risks: pool prices can move against your position, and concentrated-liquidity pools require you to choose a price range. If the market moves outside that range, your position may stop earning trading fees until it returns or you adjust it. Fees, slippage and the value of incentives can also change.

The exchange relies on smart contracts. SaucerSwap describes its contracts as non-upgradable, which can limit how a vulnerability is fixed once deployed. Using a decentralized exchange does not remove the risk of bugs, malicious tokens, wallet compromises or mistakes when signing transactions. Moving SAUCE between Hedera and Base also requires care: check the supported route and destination token rather than assuming a transfer is interchangeable. Only commit funds you can afford to lose.