Overview
CARNADO is a privacy tool on the Cardano network that hides the on-chain link between who sends a payment and who receives it. You connect a wallet, deposit ADA or Cardano native tokens, and the service mixes your funds with a shared pool before sending the equivalent amount to the addresses you name. Fees are always paid in ADA1.
It is aimed at people who want to move value on Cardano without leaving an easily traceable trail from one address to another. The service runs at adamixer.io under the brand CARNADO and describes itself as a mixer for both ADA and other tokens issued on Cardano1.
Key Features
- Sender-recipient unlinking. Your deposit is pooled with other users' funds, so the outgoing payment no longer traces cleanly back to the wallet it came from1.
- Mixes ADA and native tokens. The tool handles ADA, Cardano's main coin, as well as Cardano native tokens, which are separate assets issued on the same network1.
- Adjustable privacy levels. A step in the flow lets you pick how much mixing to apply; spreading funds across more recipient addresses raises privacy and also raises the fee1.
- Fees paid in ADA. Whichever asset you mix, the cost is calculated and collected in ADA rather than in the asset being moved or in the project's own token1.
- Guided multi-step flow. The mixer walks you through a fixed sequence (token, amount, recipients, privacy level, and a final review) before anything is confirmed1.
What to Expect
Using CARNADO starts with connecting a Cardano wallet. From there you pick a token, enter an amount, list one or more recipient addresses, choose a privacy level, and review the transaction before approving it. The interface notes a minimum deposit for each asset type: a floor amount of ADA for ADA, and a larger unit count for native tokens.
The service presents itself as powered by a token called $NADO, though it does not explain what the token does; the fee you pay is charged in ADA, not in $NADO. The token is registered in the Cardano Token Registry under the name NADO, listed as the mixer's native token and linked back to adamixer.io2. Other details that would let an outsider vet the service are thinner: the project runs under a pseudonym rather than a named team, the code is not published on any public repository, and no independent security review has been identified3.
The only project channel that resolves is an account on X, where the service posts self-reported activity figures. Those figures are the project's own and have not been independently checked against the chain3.
