HashScan is the human-readable explorer. For machine verification, query the public Mirror Node directly:
/contracts/{id}, /accounts/{id}, or /tokens/{id}. Replace the example ID with the deployment you need to verify.Hedera mainnet
V1 (AMM)
V2 (CLMM)
V3 (order book)
V3 order matching runs off-chain with on-chain settlement through a reactor contract. The reactor address is not a static list entry: fetch it per environment from the signing-domain endpoint, which returns the EIP-712 domain used for order signatures. Unauthenticated access to this endpoint is rolling out network by network with the July 2026 deployment — if it returns401, call it with a JWT instead.
verifyingContract is the reactor contract for that environment, and chainId identifies the Hedera network. Example response from the testnet environment, captured July 9, 2026:
Output
Staking and farming
Fee routing and governance
Governance submissions do not use one permanent “proposal creator” account. Historical Labs submissions used:
0.0.7281411for the 2024 Topic 103 record.0.0.4543385for later submissions.0.0.10035210for Topics 330–385.
Vesting (genesis allocation)
The vesting schedule ended July 16, 2025. Checked July 29, 2026: MarketingVesting retained 199,961.736852 SAUCE; the other three balances were zero. A residual balance is not an active vesting schedule.
WHBAR and wrappers
Tokens
Hedera testnet
For the V3 testnet reactor, fetch
https://testnet-orderbook-api.saucerswap.finance/signature/domain as shown above.
Cross-chain SAUCE — Axelar ITS
Next steps
Developer quickstart
Call these contracts through the public mirror node.
Security audits
Audit reports covering the deployed contracts.
V2 swap operations
Quote and swap against the V2 contracts.
Orderbook API
Trade the V3 order book programmatically.