Ecosystem Contract (Testnet)

Ecosystem Contracts (Testnet)

This page provides the official contract addresses for the SATUCHAIN testnet ecosystem. Use these addresses when integrating swaps, liquidity, and batched on-chain reads.

Contract Directory

Contract	Address
Multicall3	0x26ba8f0eb932558edde315f58e4b9ddd36bb9c76
SatuDexRouter02	0x867ff58e34d1801dd90291aeddad5bfd1234799d
Factory	0xf1e4d052f991728cb8616d5398f89d47b1d96cfe
Wrapped STU (WSTU)	0x9d863c0fe98e425054c72ebdc50655742001c5d1

---

What Each Contract Does

Multicall3

Purpose: Aggregates multiple read-only calls into a single RPC request. Use cases:

• Fetch token balances for many addresses at once

• Batch balanceOf, allowance, decimals, symbol, name

• Reduce RPC overhead for dashboards and indexers

Integration notes:

• Best used for staticcall / view calls (no state changes)

• Common pattern in analytics, portfolio views, and DEX UIs

SatuDexRouter02

Purpose: Primary router for swaps and liquidity operations. Typical actions:

• Swap exact input / exact output

• Add liquidity / remove liquidity

• Quote amounts (depending on router design)

Integration notes:

• UI and bots usually interact with the Router, not directly with pairs

• For ERC-20 swaps, ensure token approvals are set before calling swap methods

Factory

Purpose: Creates and tracks DEX pair contracts. Typical actions:

• Create new trading pairs

• Query pair address for two tokens (if supported by the factory interface)

Integration notes:

• Your indexer or frontend can use the Factory to discover pair addresses

• Pair creation is usually restricted to router workflows or specific permissions (implementation-dependent)

Wrapped STU (WSTU)

Purpose: ERC-20 wrapped version of the native token used in DeFi contracts. Use cases:

• Trading native token in ERC-20 pairs

• Liquidity pools that require ERC-20 compatibility

Integration notes:

• Use WSTU for router/factory interactions that require ERC-20 tokens

• Wrapping/unwrapping is typically done via deposit() and withdraw() (standard WETH-like interface)

---

Developer Notes

• Always use the addresses in this page as the source of truth for testnet integrations.

• When deploying test contracts, use WSTU as the native token representation inside DEX pools and router calls.

• For app performance, prefer Multicall3 for bulk reads instead of many individual RPC calls.