Synth sUSD (retired) (sUSD) — what its owner can do
Who can do these things
The permissions above rest with 0xEb3107117FEAd7de89Cd14D463D340A2E6917769, itself a contract, which may be a multisig or a timelock. Whether that is acceptable depends on who holds it.
0xEb3107117FEAd7de89Cd14D463D340A2E6917769— a contract, possibly a multisig. Found via owner().
Only named getters were read. If this contract uses role-based access control without enumeration, its role holders cannot be listed, and the absence of a controller here does not mean there is none.
What the contract permits
Can new tokens be created?
The supply is fixed. No function exists to create new tokens.
- No mint entry point in the contract ABI
Can transfers be blocked?
No mechanism was found that would let anyone block a transfer.
- No address blocking, pause, trading switch or transfer cap in the ABI
Is there a trading tax?
No trading tax mechanism was found.
- No tax setter or tax rate in the ABI
Can the contract logic be replaced?
The contract logic is fixed and cannot be replaced.
- No proxy pattern detected in the deployed bytecode
Is the liquidity locked?
The trading liquidity can be withdrawn by whoever holds the LP tokens.
Withdrawing liquidity leaves holders with tokens and no pool to sell them into. This is the mechanism behind most losses described as rug pulls.
- Uniswap V2 WETH pool at 0xf80758aB42C3B07dA84053Fd88804bCB6BAA4b5c: 0.0219 WETH of depth, 0% of its LP supply burned
- Uniswap V2 USDC pool at 0x0865b9C7Cd9aa9F0e9F61E96C11e524145b70550: 0.0217 USDC of depth, 0% of its LP supply burned
- Uniswap V2 USDT pool at 0xB0A539BEA1787813359Fb9AF8e2efD35dd35a744: 0.001 USDT of depth, 100% of its LP supply burned
- SushiSwap WETH pool at 0xF1F85b2C54a2bD284B1cf4141D64fD171Bd85539: 0.5483 WETH of depth, 0% of its LP supply burned
Who holds the unburned LP tokens cannot be established: ERC20 holders cannot be enumerated over RPC. It may sit in a time-lock contract, or in a wallet, and this check cannot tell those apart.