Contracts and admin powers

These are the contracts Zephyr Trade uses. They are open source and verified on the explorer: each address opens there, where anyone can read the code and every transaction.

What each contract can and can't do

GiwaDexRouterV3 (router)

• No owner, no admin functions, not upgradeable. Nobody can change it, pause it or take funds from it.
• The fee (1% / 0.9%) and the referral split (25% / 3%) are constants in the code. The treasury and the rewards vault it pays are immutable.
• It only takes tokens from the wallet that calls it, checks your minimum output on every trade and returns to the caller only what belongs to that same transaction: it never keeps your funds.
• Tokens that someone else leaves in the router by mistake can only be swept (sweep, callable by anyone) to the treasury, never to a user.
• If the rewards vault ever rejects the referral payment, the whole fee goes to the treasury and the RefSkipped event records it, so trades never get stuck.
• Token-to-token routes that pass through WETH pay the fee in ETH.

GiwaDelegateV2 (EIP-7702)

• No owner, no admin functions, no storage. The treasury and the rewards vault are immutable; the fee and the referral split are constants.
• Its execute function only works when the caller is the wallet itself. Nobody else — including Zephyr Trade — can use it to move your funds.
• It runs the launchpad trade and charges the fee on what actually moved, measured on-chain. If anything fails, the whole transaction reverts.
• A delegated wallet still accepts ETH payments that come with data, like a normal wallet.
• It supports ERC-1271 signature checks and only accepts signatures made by the wallet's own key, so apps such as Permit2 keep accepting your wallet's signatures.

GiwaOrdersV3 (order contract)

• The router, the treasury and the rewards vault are immutable. The fee is charged by the router, with the same fixed rates.
• The route of each order is fixed when it's placed, the price is checked on-chain at the current price of the route's pools, and every fill must give at least the minimum output fixed when the order was placed. See Limit orders.
• The owner (the timelock below) can only add or remove keepers, allow or disallow pool factories, set the minimum order size (never above 0.1 ETH), change the guardian and transfer ownership.
• Nobody — not the owner, the guardian or the keeper — can touch the ETH deposited for your orders, cancel your orders or change them. Only you can cancel an open order; once expired, anyone can cancel it and the ETH always goes back to you.

GiwaRefVaultV2 (rewards vault)

• The referral split (25% / 3%) is fixed in the code. Payments into the vault can never be paused: the referral share can't be diverted.
• The owner (the timelock below) can only set the minimum claim (never above 0.01 ETH), switch emergency mode on or off (emergency removes the minimum), withdraw the excess (ETH in the vault beyond what's owed to users), change the guardian and transfer ownership in two steps.
• Rewards owed to you can only be claimed by you. Nobody can take them.
• Anyone can pay into the vault, on purpose: crediting someone means sending real ETH, which then belongs to them.

Timelock and guardian

• The owner of the order contract and of the rewards vault is a timelock contract (GiwaTimelock) with a 1-day delay. Every owner action is published on-chain first and can only run after the delay, so anyone can see it coming.
• A guardian can act without delay, but only to stop things: remove keepers or factories from the order contract (which stops fills) and switch the rewards vault to emergency mode. It can never touch deposits, and cancelling an order always works.

Previous contracts

These contracts replaced earlier versions. Orders placed on the previous order contract stay listed in the terminal, can be cancelled, and the keeper keeps executing them until they expire. Any balance in the previous rewards vault can still be claimed from the Referrals page.

Audit status

The contracts are open source, verified on the explorer and tested against a fork of the chain, but they have not had an external audit. Keep that in mind, see Risks.