Worth separating two things that get blurred: not collecting an email, password or persistent history is data minimisation at the platform layer. On-chain visibility is untouched by any of that — amounts, timing and addresses stay public regardless.
For anyone here running a community or writing regularly: the affiliate share is 40% of profit on every exchange a referral makes, ongoing rather than a one-time signup payment. Minimum payout is 100 USDT and referral activity is visible in the affiliate account.
Reminder worth repeating: the order inquiry code is the only reference tied to a swap here. Losing it doesn't stop the exchange or affect where funds land, but it does mean there's no way to pull up status or raise that specific order with support afterward.
Distinction worth keeping straight when comparing platforms: the network fee goes to the chain and never touches the exchange, while the rate is where any platform margin sits.
Cross-chain swaps also carry network costs on both legs, so two expensive chains total more than two cheap ones at an identical quoted rate.
Distinction that gets blurred in comparisons: a bridge mints a wrapped claim backed by a locked pool, while a conversion hands over the native asset with nothing outstanding afterward.
Different exposure windows — a conversion's ends at settlement, a wrapped position's continues for as long as it's held.
Both have their place depending on whether you need the same asset elsewhere or just value elsewhere.
Open question for the thread: which pair or network variant is missing from your workflow?
Most useful format is the pair plus what you're routing through instead right now — that shows the actual cost in extra fees and confirmations rather than just the gap.
Rate locks become most valuable precisely when they become hardest to execute — volatility drives network congestion, which extends confirmation times against a fixed window. The decision is a joint function of risk preference and execution speed.
For anyone hitting an invalid address error: it's a network check, not a typo check. Address formats carry checksums so genuine typos fail differently.
Multi-network assets like USDT cause almost all of these — confirm which network your receiving address belongs to before pasting it.
An interface that holds a market-derived figure still is displaying something progressively less true. Showing movement lets reality contradict the interface continuously rather than at the moment of commitment.
Worth stating plainly since roadmap questions come up: no standing balances, no accounts, and no saved address lists are deliberate exclusions rather than things pending.
Each costs something real — no parked funds, no recovery path, and pasting an address each time. If those matter to your workflow, a custodial exchange with an account is the better fit.
https://cce.cash/exchange
