NO CUSTODIAN, NO KYC, NO ACCOUNT.  ZETO is a web interface for BTC → XMR atomic swaps, built on the swap protocol of eigenwallet (formerly UnstoppableSwap). You trade peer-to-peer with a liquidity maker - at every point of the protocol, either the swap completes or you can recover your bitcoin.

Quote — you ask a maker for a price over libp2p.
Setup — both sides generate key shares and pre-sign the Bitcoin cancel, refund and punish transactions, before anything moves.
BTC lock — your bitcoin goes into a 2-of-2 output.
XMR lock — the maker locks monero to an address derived from both key shares, and sends you the transfer proof.
Redeem — you hand over an encrypted signature. The maker redeeming your BTC reveals their Monero key share, which sweeps the locked XMR to you.
Safety — if anything stalls, timelocks let you cancel and refund the BTC.
Setup is what makes the rest safe: adaptor signatures on secp256k1, tied to the ed25519 Monero key shares by a cross-group DLEQ proof.

 BROWSER ARCHITECTURE

---

The protocol needs a Bitcoin wallet, a Monero wallet and a libp2p node. Your browser runs the interface and drives a daemon (zetod) embedding the audited eigenwallet Rust crates. A daemon is required — ZETO performs real swaps, so there is no simulated mode to mistake for one.

Makers come from libp2p rendezvous through that daemon, so you see the same book as the desktop app — including  TOR  makers a browser could never reach on its own.

 YOUR KEYS NEVER LEAVE YOUR BROWSER

---

Your Bitcoin wallet lives only in this browser, encrypted with your password. The lock transaction is built and signed locally — the daemon receives the signed result and never your keys.

Two checks make that safe against the daemon itself, which is shared infrastructure. Your browser signs only the exact transaction it just built, and it verifies the change address is the one you gave when starting the swap — the protocol reuses that address as the destination of every refund path. If either differs, nothing is signed.

 IF ZETO DISAPPEARS MID-SWAP

---

Atomic swaps run on timelocks, so a coordinator vanishing at the wrong moment would be a real problem. At every stage you can download what you need to finish without us — a plain text file, broadcastable from any node, from a phone.

Bitcoin refund kit. From the lock until the maker redeems, you can save two already signed transactions — a cancel and a refund — that return your coins to your own address, with no cooperation from anyone. The cancel becomes broadcastable 24 blocks after the lock confirms, and you have 144 more before the maker may claim the coins. Every output pays you, so the file is worthless to whoever steals it.

Monero redeem kit. Once the maker has redeemed the Bitcoin, ZETO publishes the Monero transaction that pays you and keeps retrying until it confirms — you normally do nothing. You can still save it and publish it on any Monero node yourself; its outputs are fixed at signing time.

 FEES

---

ZETO charges a 0.7% coordinator fee for infrastructure. It is not a custody fee: it is one output of the final Monero redeem transaction — the protocol-native receive pool eigenwallet uses for its own developer tip. Network fees and the maker's spread go to miners and makers, not to ZETO.

Don't want to pay it? Use the eigenwallet desktop app directly: same protocol, same makers, zero coordinator fee. ZETO exists for those who prefer a browser.

Questions, or a swap that needs a hand? zeto.cash@proton.me
Clearnet: https://zeto.cash
Terms: https://zeto.cash/terms

Nice one!

When we talk about a noncustodial swap, this is what I want to see!

May add the terms of service link right before one creates the wallet or makes the swap  

Also, a FAQ page would be awesome. I will have more to say once I am a swap through the platform.

I checked Zeto.cash (BTC -> XMR atomic swaps in the browser, eigenwallet under the hood). Poked at the live site and the JS they ship. Not an audit, didn't run a real swap with money. Just what you can see from the outside.

Stuff that bothered me:

- "Keys never leave the browser" is only half the story. Signing keys stay client-side, fine. But if you use the hosted daemon (which is the default), that machine sees your XMR receive address, BTC refund/change address, which maker you picked, approvals, wallet balance hints, etc. Not the same as running asb/swap locally. If you care about that, force a local daemon and don't let it auto-connect to theirs.

- No CSP, no HSTS, no X-Frame-Options frame-ancestors, no nosniff. For a page that keeps an encrypted seed + session tokens in localStorage, that's sloppy. One XSS and you're done.

- When you start a swap the client sends the expected receive pool (your addr 99.3% + their fee addr 0.7%). The approval UI then just displays whatever monero_receive_pool the daemon sends back. I didn't see a hard client-side assert that it still matches the hardcoded fee address before you hit accept. If the daemon is evil or pwned, don't blindly trust that screen - check the actual addresses.

- They say the Rust crates are audited from eigenwallet. Cool. The thing signing PSBTs in your browser is a fat minified blob with no public repo that I could find. Trust model is "trust this website's JS". Filename is content-hashed which is better than nothing, still not source.

- Daemon token on the websocket URL. events?token=... Tokens in query strings end up in proxy logs, CF logs, random extensions. Put it in a header like a normal person.

- Keystore KDF is on the light side. scrypt N=2^15, r=8, p=1. Password gate is length >= 8. If someone yoinks the .json from disk/localStorage, that's not a lot of work by 2026 standards. Bump N or use argon2id, and don't allow "password1".

- Session PoW is ~18 bits of SHA256. Seconds on a laptop. They 429 you without the header, which is something, but 18 bits won't stop anyone who wants to burn sessions.health also happily tells you how many sessions are live.

- Cloudflare beacon on every page. Browser hits Kraken + CoinGecko for XMRBTC and mempool.space blockstream for fees and broadcast. Your IP, their edge, your UTXO activity - you do the math. At least make analytics opt-in and let people set their own electrum/explorer.

- Manual "Daemon URL" field. Placeholder is 127.0.0.1:9976 but it will talk to whatever you paste. Classic phishing angle: fake daemon, convince you to unlock wallet and approve a lock. Warn hard if the URL isn't localhost their known host.

- Number(x) || 0 on approval amounts. Garbage from the daemon becomes zero in the UI. Also expiration_ts uses || so a falsy/0 value becomes "now + 180 seconds". Don't use || for numeric fields, use nullish checks.

- Wallet state uploaded to the daemon. balance, max giveable, next receive address. Needed for their architecture maybe, still a data leak on the hosted path.

- When I looked, a bunch of makers had maxSwapAmount=0 or version < 4.13.0 (client filters those). Clearnet TCP multiaddrs still show up. Prefer onion/wss if you're swapping for privacy reasons. Also discovery can fall back to api.unstoppableswap.net - third party in the loop.

- Suspend path can clear local state even if the daemon didn't ack ("clearing locally anyway"). History is localStorage only - wipe the profile and the in-app history is gone. Download the refund/redeem kits. Seriously.

- Some of the hostnames look like shitposts. You're trusting whoever runs those for lock checks if the UI uses them. Run your own daemon/node if you can.

What I liked

- They do check change address against what you started with before building
- They refuse lock amount above your approved budget
- Refund kit hex gets some local sanity checks before you broadcast
- CORS on the API is locked to https://zeto.cash (not *)
- Asset filenames are hashed; CF insights script has SRI

Bottom line:
Interesting project, better than another custodial "instant exchange". I would not put serious coin through the hosted path until the frontend is public, CSP/HSTS are on, and the approval screen cryptographically checks the fee outputs. If you use it, local zetod + download kits + verify every address on the lock screen yourself.

Again: read-only look at the shipped JS and public API. No funded swap from me. DYOR.
NB: I have used my AI assistant tool to decorate this post. 

Thanks for the reply.
I was interested in joining the review Campaign. But my forum ranks won't let me apply for the review campaign.
I would have focused on the Tech side, especially during the review campaign, if possible.

Rechecked against the live site.

Fixed side checks out. Headers are there (CSP, HSTS, X-Frame-Options, nosniff, Referrer-Policy, Permissions-Policy, COOP). Cloudflare beacon is gone; one same-origin hashed script. Lock screen now refuses approve when the receive pool fails the checks you described — address has to match what the browser already has, shares have to sum, your cut has to clear ~99.3% minus the rounding slack. Unusable makers are out of the headline figures (still show up greyed in the list, which is fine).

One small leftover on the pool assert, not a disagreement with what you wrote: it enforces your share and the sum, it does not pin the leftover 0.7% to the hardcoded fee address. So a bad daemon cannot quietly cut your Monero below the advertised cut anymore, but it could still point the fee slice somewhere else without tripping that check. Worth tightening when you touch that path again.

Appreciate the straight answers on the design points. Especially the correction that pointing at your own zetod is not a working path today, that means the metadata exposure (receive/refund/maker/balance hints to the hosted daemon) is not optional if you use zeto at all right now. Same with the wallet snapshot: need it to size the swap, browser still has to refuse a PSBT it didn't approve. History in localStorage + refund kits is coherent once there's no account. Used AI to make it sound better.

Can we do Bitcoin monero transactions in both directions, or only BTC to XMR?
There is already non custodial Eigen wallet, and it is using atomic swaps in one direction.
I see Zeto is built based on Eigen, but there is coordinator here, so I am not sure it's really decentralized.

Hello team Zeto,

I think it would be a good idea to check the comments on the review campaign thread yourself, as people are commenting about the swap failure. I myself tried three times to swap, and they failed as well. However, I see someone was able to swap. It would be good if you could give us some instructions or tips to avoid a failed swap. I like the fact that we have full control over our funds.

I am sure most people would have been frustrated seeing their swap wasn't completed, and their funds are stuck. However, Zeto advances here because the user himself controls the funds and can send the funds to another address. After three failed attempts, I have moved my funds to another wallet address. I am planning to try again, but I hope you can check the logs and tell us what we were doing wrong.

If you manually broadcast the monero redeem tx, the client tries random community nodes including joke names like surveillance.monster and definitelynotafed.com. 

Your signed tx hex goes to whoever runs those.

Proven maker rep is kinda weak. New rep badges look helpful but its all zeto's ledger. Proven = literally one ok swap. Maker can reset by showing up as a new peer id. Id treat those counters as a hint, not proof.

The market has moved well over the past few days, and investors are starting to build their portfolios for the coming bull run, so the question is: is it worth accumulating Monero?

So I have included the coin Monero in my cryptocurrency terms platform. This is a must-read for anyone asking whether it's worth adding Monero and what its potential is.


Everything You Need to Know About Monero (XMR)

After reading this and seeing its potential, you need Zeto.cash to swap your Bitcoin for Monero

Thank you for explaining it, and this is what I suspected myself.
I already used Eighne and Unstoppable wallet, and I don't see any big advantage for switching to Zeto wallet.
Only selling point that would make me use something new would be decentralized atomic swaps in both diretions, but I think that is coming soon with FCMP++ monero update.

If you take a look at the Zeto website, they are very transparent about this information, which I liked the most from a new startup.

According to their website, they say - ZETO charges a 0.7% coordinator fee, taken as an output of the final Monero transaction that pays you (it covers infrastructure). Prefer zero fees? Use the official eigenwallet desktop app directly — same protocol, same makers, no coordinator.

They are not hiding anything here. They are even suggesting people use the eigenwallet desktop app if someone wants to avoid the 0.7% coordinator fee. I also hope Zeto will bring something new in the future to keep the customers' interest in using their service.