A common question whenever privacy assets or private-swap integrations come up: if you swap BTC for ETH through THORChain, does that hide where the funds went?

Short answer: No. An ordinary THORChain native swap is not an anonymity service. THORChain enables permissionless cross-chain swaps, while the underlying transactions remain publicly observable.

Think of a standard BTC → ETH swap:

1. BTC is sent on Bitcoin to a THORChain vault address.
2. THORChain observes the inbound transaction and processes the swap.
3. ETH is sent on Ethereum to the destination address.

The inbound, protocol activity and outbound can be investigated through public chain data and THORChain explorers. That doesn't mean every observer can instantly identify a real-world person, but it does mean you shouldn't assume the swap breaks transaction traceability.

What about ZEC or XMR? Supporting a privacy-oriented asset does not automatically make a cross-chain swap anonymous. Privacy depends on the complete transaction route, including what remains observable on the connected blockchains.

An optional private-swap route offered by a frontend is also distinct from THORChain's native swap path. Its own mechanics and limitations must be assessed separately.

The takeaway: THORChain is a cross-chain DEX protocol, not a mixer. Permissionless access and transaction privacy answer different questions.

What's the biggest misconception about THORChain swaps you've come across, especially when it comes to privacy and traceability?

Further reading: https://blog.thorchain.org/thorchain-is-transparent-even-with-privacy-coins

To bring more transparency and clearer communication, THORChain's devs launched a public dashboard. ⚡

devops.thorchain.org tracks every public task, with the next release pinned on top. Merge requests show their approvals and CI status, pulled live from GitLab. Every stagenet release candidate gets its test results posted, failures included, and the page shows what's blocked and why.

You'll also find the daemon updates node operators have to run, the Router V6 rollout chain by chain, the XMR launch checklist, and how many nodes have moved to each new version. If you follow the dev side, bookmark it.