FAQ

Short, honest answers to the questions a holder or developer asks first. Each answer links to the page that covers it in full.

Note

TIDE currently runs on a testnet, so no real funds are at stake yet. The contracts are immutable and the position is un-rug-able by design: a fixed 10,000 supply, no transfer tax, and no admin drain. TIDE is independent and self-reviewed, and it is not yet third-party audited; an external audit is a prerequisite before any mainnet launch. Review the trust model and size your position accordingly. See Known limitations.

Do I need to deposit anything or manage a liquidity range?

No. There is nothing to deposit, stake, or range-manage, and there are no liquidations. The entire fixed supply lives in one protocol-owned ETH/TIDE Uniswap V4 position owned by the hook contract itself. You just hold the TIDE token. Via a DN404 mirror, every whole TIDE you hold automatically materializes one tradable Tide-LP NFT — and that NFT earns a pro-rata share of every swap fee. Holding is providing liquidity.

See Hold = LP (DN404).

How do I start earning?

1. Connect a wallet and buy TIDE (native ETH → TIDE) through the in-app swap or any router against the canonical pool.
2. Each whole TIDE you hold auto-mints one Tide-LP NFT (UNIT = 1 ether, i.e. 1e18).
3. Every swap against the pool accrues fees to your NFTs pro-rata. Anyone can pokeFees() to roll accrued fees into the per-share accumulators; you then claim to harvest your share.

See Quickstart and Claim = in-pool buyback.

I hold some TIDE but earn nothing — why?

Fees accrue per NFT, and you only mint an NFT when you cross a whole-token threshold. Fractional TIDE below the next whole unit earns nothing until it completes that unit. The amount you still need is:

need = UNIT - (balance % UNIT)   // UNIT = 1e18

The dapp shows this shortfall and a progress meter toward your next NFT on the Collection page. Acquire enough to cross the threshold and the NFT mints automatically.

See Collection & your position and Hold = LP (DN404).

Why is a claim paid in TIDE instead of ETH?

When you claim, the protocol takes the ETH leg of your accrued fees and buys TIDE back in the pool, then pays you in TIDE (the share already accrued in TIDE is paid as-is). There is no direct ETH payout. Every claim therefore creates buy pressure on the token, which is the point — the buyback is integrated into the claim. The protocol’s own buyback swap is fee-exempt.

Note

The buyback’s minOut is derived from spot price with a 10% slippage band (MAX_BUYBACK_SLIPPAGE_BPS = 1000), so large claims are sandwichable. Keep per-claim amounts modest. See Known limitations.

See Claim = in-pool buyback.

What happens if I sell (or transfer) an NFT while my rewards are still vesting?

Claimed gains vest linearly (production: 72 hours; compressed on Sepolia). If you sell or transfer an NFT before your vesting fully unlocks, you forfeit the not-yet-vested TIDE — you keep only what has already vested. The forfeited amount is then raffled to another holder (the seller and counterparty are excluded from that draw only). The winner has a window to activate the prize, which re-vests it; an unactivated prize expires to the Treasury.

See 72-hour linear vesting and The forfeited-vesting lottery.

Does a new claim restart my vesting clock?

A new claim re-locks the still-locked remainder over a fresh vesting window (this is intentional — it rewards holding over claim-and-dump). A withdrawal of already-vested TIDE does not restart the clock. Vested-but-not-yet-withdrawn TIDE is yours even if you sell.

See 72-hour linear vesting.

Can the team rug? Where are the funds?

No path lets anyone — including the dev — seize user funds.

• Supply is fixed at 10,000 TIDE, minted once in the constructor. The owner cannot mint; supply only ever goes down, via Treasury buyback-burn.
• After the one-shot seed() call, the owner cannot move, withdraw, or migrate the liquidity, and cannot redirect, pause, or skim fees — fees flow only to NFT holders via claim. There is no proxy, no upgradeability, no admin pause.
• The Treasury has no withdrawal function. Its only outward action is executeBuyback(), which burns the treasury’s TIDE. The dev “holds the button, not the cashbox.”

See Trust model & no-rug and Treasury.

Is it audited?

Not yet. TIDE is independent and self-reviewed: a careful internal review found and fixed one medium-severity bug, and the contracts are immutable on a Sepolia testnet deployment today, so no real funds are at stake yet. It is not third-party audited, and an external audit is a prerequisite before any mainnet launch. Review the trust model and size your position accordingly.

See Known limitations.

What network is it on, and what are the addresses?

The live deployment is on Ethereum Sepolia (chain ID 11155111).

Component	Address
TideHook (TIDE ERC-20 + hook)	0xF6F88E408Ea5df8a809a3b4232b9Ef7f2a9d40c0
TideMirror (Tide-LP ERC-721)	0x4c08F0B24254BE677924C5655Ca1706Feb8259F4
Treasury	0x076f29063199DB470D260E5cE2cb560Af98cfBd3
TideArt	0xE08Cb2BDa6517573FD6DB93B300f54CBcd5fdcf4

For the full table (V4 infra, swap router, RPC) see Addresses & network. To run a local fork, see Run it locally.

How is the swap fee decided?

The pool uses a degressive launch fee enforced inside the hook at swap time, not a fixed fee. It decays with time since launch:

Window	Fee	Pips
First feeWindow1 (prod 5 min)	25%	250_000
feeWindow1–feeWindow2 (prod 5–8 min)	10%	100_000
Thereafter	5% (forever)	50_000

currentFee() recomputes this every swap from block.timestamp − launchTime. The schedule is hard-coded with no setter — not even the dev can change it — and it is router-agnostic: because it is enforced at the PoolManager level, every swap through the pool pays it regardless of which router or aggregator initiates it. The protocol’s own buyback (sender == address(this)) is fee-exempt.

See Degressive launch fee.

What exactly are the NFTs?

Each Tide-LP NFT is two things at once:

1. The unit of fee accounting — one NFT is a 1/10000 share of the single pool and accrues fees pro-rata.
2. Generative on-chain art — a deterministic “tidal-harmonic gauge” SVG rendered fully on-chain by TideArt from (tokenId, seed), with five traits (Hue, Amplitude, Period, Phase, Harmonics). No IPFS, no server.

The NFT collection is the ERC-721 contract TideMirror (name "Tide-LP", symbol "TIDE-LP"), reached as hook.mirror(). All NFT state lives on the hook; the mirror is a stateless DN404-style facade. Always interact with the NFT via the mirror, never call the hook’s onlyMirror handleNFT* functions directly.

Note

Ranks (Paper → Bronze → Silver → Gold → Platinum → Diamond, one day each, capped at Diamond) are an off-chain art overlay keyed on how long the current holder has held the token. They do not touch the contracts; the on-chain SVG stays canonical.

See TideMirror and TideArt.

How do I see my collection or look up another address?

On the Collection page:

• My tides — wallet-only; shows your own NFTs plus a “My position” banner (TIDE held, Tide-LP count, share of fees, shortfall to next NFT).
• All tides — the public explorer of the whole minted gallery, with a “Look up any 0x address…” field. Enter a valid address to view that holder’s NFTs and a read-only position card.

See Collection & your position.

What does it cost to claim, and who gets paid?

claim(tokenId) and claimMany(tokenIds[]) always pay the current owner of each NFT, but only ever process the caller’s own owed balance — so you cannot restart someone else’s vesting clock by claiming their NFT. Claiming is a permissionless write you pay gas for; there is no protocol fee on claiming beyond gas. pokeFees() is also permissionless (a griefer poking fees only wastes their own gas).

See Claim dashboard and Claim = in-pool buyback.