Zeto 🔄 Non-custodial BTC → XMR | Trustless atomic swaps - No custodian - No KYC

[Zeto Cash]

ZETO update
A Monero wallet in the browser, a security audit, and a better history

Since the last update, most of the work went into what happens after a swap: where the Monero lands, and what you can do with it without leaving the site. There was also an external audit of the refund path. Both are live.


New: a Monero wallet, in your browser, from the same seed

Until now a swap needed a Monero address from somewhere else. ZETO now derives a Monero wallet from the same 12 words as your Bitcoin wallet, in the browser, and nothing leaves it:

• Receive. Tick "Receive in my ZETO Monero wallet" on the swap form and the payout goes to your own address. Payments from swaps are detected on their own; any other payment can be added by pasting its transaction id. Amounts are decoded locally with your view key; the node only learns which transaction you looked at.
  
  
• Send. Building and signing happen in the browser, with the same Monero library as the eigenwallet engine (monero-oxide, compiled to WebAssembly). Ring selection, decoys, fee and change are standard, so the transaction is not fingerprintable as "made by ZETO". Before broadcast the browser re-checks the signed transaction against what you confirmed: destination, amount, fee, change. Your spend key never reaches the node or our server. Marked experimental: it works, we have used it on mainnet, but treat it as young software and start small.
  
  
• Scan. The wallet can scan the chain for payments you did not paste, for the last 30 days. Our coordinator keeps a compact copy of that window (a few MB per day); your browser downloads it and matches it with your view key in a background worker. The server learns that a browser asked for block ranges, not which wallet, not what matched. Older payments stay reachable by txid, or by restoring the 25 words in a full wallet.
  
  
• Portable. Settings shows the 25-word Monero seed and the restore height, so the same wallet opens in Feather, the official GUI, or anything else. Nothing here locks you in.
  
  
• Your node. Settings lets you pick which Monero node the wallet talks to: our default pool, one known node, or your own URL. Same for the Bitcoin data source, which was already there.

The audit, and what we fixed

An independent review of the refund path found two real problems. Both are fixed and deployed:

• The refund kit was never kept locally. The kit (signed cancel + refund transactions, the thing that gets your Bitcoin back without us) could only be downloaded while the engine that built it was alive. If that engine was gone, so was the kit. The browser now keeps a verified copy of the kit from the moment the Bitcoin is locked, and offers it directly when the engine cannot be reached.
  
  
• The refund address was taken on trust. The kit was checked for structure but not against the address your browser chose when the swap started. It is now: a kit paying anywhere else is refused and reported, before you ever depend on it.

Smaller things

• Activity. Both wallets now have an Activity section: every deposit and every send, dated, with a link to the explorer, in a short paged list.

Being honest about what this is

The Monero wallet is a convenience on top of the swap, not a replacement for a full wallet. It sees 30 days of chain history, one account, one address. Sending is experimental. If you hold a meaningful balance, restore the 25 words somewhere that scans the whole chain and keep ZETO for the swap itself.

What the browser verifies, and what it still trusts. The refund path (kit, address, transactions) is checked in your browser and kept there. The swap engine is still hosted by us, and it holds the swap-side key while a swap runs; that is the part an audit cannot make trustless without moving the engine into the browser, which is the next big piece of work.

Your Bitcoin only ever moves after you confirm the lock in your browser, and aborting before that is always free.

The maker side is still open to anyone: zeto.cash/run-a-maker.

Keep the reports coming. The audit came from one of you, and the wallet exists because several of you asked where the Monero was supposed to go.

[robelneo]

ZETO update
A Monero wallet in the browser, a security audit, and a better history

Since the last update, most of the work went into what happens after a swap: where the Monero lands, and what you can do with it without leaving the site. There was also an external audit of the refund path. Both are live.

Thanks for this latest update. I will create a new transaction to see the updates and review it.

There is no problem if they stay inactive.
But their activity will surely boost their visibility. People prefer to use services that are more engaging with the potential customers. I myself would choose a service that hangout in the forum. Since they are promoting here, it would be good for them to engage with the forum members.

This is just your misconception; engagement is good, but constant updates, addressing issues and concerns, no complaints, continuous marketing, and a good rating are far better.

[mv1986]

@Zeto Cash I wanted to give your service a try and I literally tried to swap 12-15 times or so. Always let the 90 seconds countdown go down and start over again, changed market makers, tried again.

Is there any issue on my side? First I tried automatic, but then went through the whole list, made sure they have the right range and yet it never worked. Have been using your wallet, everything went until then, but now I wonder whether there is anything I could be doing wrong. Wanted to try with around $40 (BTC to XMR).

Maybe others got the same issue?

[Lucius]

@mv1986, I read several reviews on welivecrypto and it is possible that the problem is in the amount you want to swap. $40 is not an amount that should be in the range of something that should be rejected, but I'm not sure that's the problem.

Maybe @Zeto Cash can answer that.

I personally haven't tried swap, but I think I will do so very soon.

[mv1986]

@mv1986, I read several reviews on welivecrypto and it is possible that the problem is in the amount you want to swap. $40 is not an amount that should be in the range of something that should be rejected, but I'm not sure that's the problem.

Maybe @Zeto Cash can answer that.

I personally haven't tried swap, but I think I will do so very soon.

We are in touch with them already. The main problem I see is if market makers set a lower threshold and the threshold is 0.000001 BTC and you try to swap 0.000475 BTC, it should definitely work. I chose market makers whose lower threshold I fulfilled and I used automatic selection. But let's see, I am waiting for a response and will try again later.

Other than that, you are of course right, the amount can play a role, but $40 should not be in that range.

[robelneo]

@mv1986, I read several reviews on welivecrypto and it is possible that the problem is in the amount you want to swap. $40 is not an amount that should be in the range of something that should be rejected, but I'm not sure that's the problem.

I've already made 3 swaps, and my first two swaps are on the minimum amount, where I encountered a problem with the makers because some of them have a minimum threshold that is higher than the minimum amount, so check the other makers and follow their minimum threshold. Once you hit the right threshold, you are good to go

I personally haven't tried swap, but I think I will do so very soon.

Tried it, brother, and share your experience here for the community.

[mv1986]

@mv1986, I read several reviews on welivecrypto and it is possible that the problem is in the amount you want to swap. $40 is not an amount that should be in the range of something that should be rejected, but I'm not sure that's the problem.

I've already made 3 swaps, and my first two swaps are on the minimum amount, where I encountered a problem with the makers because some of them have a minimum threshold that is higher than the minimum amount, so check the other makers and follow their minimum threshold. Once you hit the right threshold, you are good to go

~I chose market makers whose lower threshold I fulfilled and I used automatic selection. ~

I am trying to swap 0.000475 BTC. I said this in the post I quoted above. I am at 475x the minimum amount of this market maker. I have tried other market makers, I have tried automatic selection.

When did you last make an exchange? My question is whether there is some problem that many more are facing or whether it could be - for whatever reason - a problem my end. The thing is, the engine gets started, everything seems to work as intended, but then at 90 seconds it cancels and says:



It can't be a problem on my end, can it? If so, how?

[robelneo]

When did you last make an exchange? My question is whether there is some problem that many more are facing or whether it could be - for whatever reason - a problem my end. The thing is, the engine gets started, everything seems to work as intended, but then at 90 seconds it cancels and says:



It can't be a problem on my end, can it? If so, how?

My last transaction was three weeks ago, and before it was completed, I had some aborted transactions. I figured it was because of the small amount and my limited choice of makers, so I did manual and automatic selections until my transaction went through.
I will do another one later to test the new features now that a Monero wallet has been added.

[notocactus]

My last transaction was three weeks ago, and before it was completed, I had some aborted transactions. I figured it was because of the small amount and my limited choice of makers, so I did manual and automatic selections until my transaction went through.
I will do another one later to test the new features now that a Monero wallet has been added.

My test swap with its value about $5 was not completed after more than 30 minutes, then I had to abort it. I chose $5 because I saw it is more than minimum $ for a swap but it was not completed well.

If many people had similar issues and had to abort their small value swaps many times already, is it time for Zeto to consider increasing their exchange minimum swap value?

If a change can bring more convenience, save time for users, I believe that Zeto user community will appreciate it. Especially with people who aim at having a first test with the exchange. First impression is very important because it decides what people will do next, use or don't use the platform.

[robelneo]

My test swap with its value about $5 was not completed after more than 30 minutes, then I had to abort it. I chose $5 because I saw it is more than minimum $ for a swap but it was not completed well.

If many people had similar issues and had to abort their small value swaps many times already, is it time for Zeto to consider increasing their exchange minimum swap value?

If a change can bring more convenience, save time for users, I believe that Zeto user community will appreciate it. Especially with people who aim at having a first test with the exchange. First impression is very important because it decides what people will do next, use or don't use the platform.

That was my first reaction on my first swap. There are limited makers that accept the minimum amount, but it will eventually be completed. You just need to be patient, or you can increase the amount. There is no need to doubt the platform; everything is automated, and they have escrow funds in case of an error.

I just completed another swap after two failed attempts. I have increased the swap amount to 0.0007 from 0.0004, the estimated time is shorter than what's actually shown on the images.



I also used the platform's Monero address, and it went smoothly

[notocactus]

There is no need to doubt the platform; everything is automated, and they have escrow funds in case of an error.

I did not say anything like I am doubtful about Zeto platform. I discussed about inconvenience for users and clearly with people who are new users at Zeto, want to explore it, get their very first experience, inconvenience means likely skip the platform and try with other ones.

If too low swap value has very high rate of failures for swap trades and users have to abort their swaps, Zeto will have to consider to change their minimum swap value to a threshold that has much lower failure rate. As an exchange operator, they truly have all these stats so that they can find a good threshold for achieving this purpose.

If they want to maintain low swap value for users, they can split it to two categories: one below a threshold for low valued swaps; another one above a threshold for higher valued swaps with better successful rates.

[robelneo]

I did not say anything like I am doubtful about Zeto platform. I discussed about inconvenience for users and clearly with people who are new users at Zeto, want to explore it, get their very first experience, inconvenience means likely skip the platform and try with other ones.

If the swap value is too low, it has a very high rate of failures for swap trades, and users have to abort their swaps, Zeto will have to consider changing its minimum swap value to a threshold that has a much lower failure rate. As an exchange operator, they truly have all these stats so that they can find a good threshold for achieving this purpose.

As someone who shared the same experience, I agree with your observation. I think the admin should look into these failure rates and possibly increase the minimum threshold that makers will accept, as it takes patience to complete your transaction if you're doing it with a small amount. I'm sure the admin is reading all reviews and will take action on issues that affect their users.

[robelneo]

This is the current rating of Zeto.cash on Welivecrypto so far they have a good rating, the bad feedback is not because the users have lost money, it's their experience, I'm sure the admin will improve the platform and add more makers to make transactions fast and easy to acquire more good feedback.

[robelneo]

Done with my fourth swap to see the new changes the developer has made so far. There is now a timeline of the swap, so no need to guess how much time you have spent swapping your Bitcoin to XMR.

In my case, it took 19 minutes to finish the swap.

[robelneo]

I just submitted the latest review on my last transaction yesterday. Hopefully, the moderator will approve it as soon as possible. We'll post the review link once it's approved.

[Zeto Cash]

ZETO update
An onion service, faster wallets, and a light theme that works

Since the last update, most of the work went into one question several of you asked: can this run over Tor without leaking anything on the side? It can now. The rest is speed, in the two places where the wallets were slow, plus a few things around the site.


New: ZETO as an onion service

http://iwa5tjcyfjxrg4zn3csagmsq7zqcuuhcpgrsbhyc4asnavpnd64lqqid.onion

The clearnet site now sends an Onion-Location header, so Tor Browser offers the onion by itself, and there is a small onion badge in the footer. The onion is not the same site proxied: it is a separate build, with a different policy.

• One host, nothing else. The clearnet page talks to a dozen third parties straight from your browser: Esplora servers for the Bitcoin wallet, public Monero nodes, Kraken for the reference price, two block explorers. Each is a reasonable trade on the clearnet. Over Tor each one is a fresh circuit to a company that then learns which addresses or transactions you care about. So the onion build talks to exactly one host: the onion it was served from. The hostnames of the third parties are not in that bundle at all; the build fails if one gets in.
  
  
• What the coordinator does instead. The Bitcoin wallet's chain queries, the Monero scan feed, the few monerod calls the Monero wallet makes (transactions, key images, decoys, broadcast), and the reference price all go through our coordinator, on the same onion. Be clear about the trade: our server then sees what those third parties no longer do. It sees which transactions you look up, never an address of yours, never a key. That is the same trade as the "via ZETO" option that already existed for the Bitcoin data source, now applied to everything, because over Tor the alternative is worse.
  
  
• What is off. No explorer links (the txid stays copyable text), no fallback maker registry, no search engine metadata. You can still point the Monero wallet at your own node, and an onion node is accepted there.
  
  
• Two servers. The onion front end runs on a machine that holds nothing of the backend; it reaches the coordinator through a second onion. Tor Browser sends "Origin: null" between onions, which no CORS policy can accept safely, so the front end carries the API on its own origin instead of letting the browser cross onions. One circuit from your side, no CORS at all.

Faster wallets, on Tor and off

• Bitcoin wallet scan. It used to ask about one address at a time: sixteen round trips for an empty wallet, around forty for a used one, and every unlock started again from zero. It now asks about a whole gap window at once and remembers how many addresses each chain had used (two integers, nothing else is stored), so the next unlock re-checks those in parallel and probes only beyond them. An empty wallet is two round trips. Same result as before, in the same order; over Tor this is the difference between a minute and a few seconds.
  
  
• Monero scan. The first scan now lets you choose how far back to go: 24 hours, 7 days, 15 days, or everything the coordinator holds, with the download size next to it (about 4 MB per day). Later scans continue from where the first stopped. The scan no longer gives up on a slow link: it times out on silence, not on total time, the bar moves while a range downloads, and over Tor three ranges download at once.
  
  
• Monero sends over Tor. Choosing decoys needs the RingCT output distribution, which public nodes only serve as 23 MB of JSON, and Tor Browser forgets it with every new identity. The coordinator now keeps one copy, kept current every five minutes, and serves it compact: about 3 MB for the whole history. The browser applies the same checks to it. On the clearnet nothing changes: the wallet still takes it from the node you chose, once, and caches it.

Around the site

• Engine. The coordinator runs eigenwallet 4.16.1. The footer now shows the engine version and the site commit, read from the running binary, so you can see when it moves.
• Light theme. Reworked from the tokens up: alerts, disabled buttons, the mobile menu and the progress ring all read correctly on white now. The dark theme is pixel-identical to before.
• Progress ring. The swap progress bar is a hollow ring with a gradient thread, instead of the filled disc.
• Blog. A small blog at zeto.cash/blog, on Monero privacy and what an atomic swap does and does not hide. Static pages, RSS, nothing dynamic.
• Reference price. On the onion it comes from the coordinator (Kraken's mid, asked once a minute for everyone) rather than from your browser, so the "vs market" lines work there too.

Being honest about what this is

The onion removes the third parties from your browser's side. It does not remove us: the coordinator hosts the swap engine during a swap, and over Tor it also relays the chain queries that the clearnet page would have sent elsewhere. Everything that was verified in your browser before still is: the refund kit, the refund address, the signed Monero transaction before broadcast, the amounts decoded with your view key.

If you run Tor Browser: the scan feed is 4 MB per day of history and a first Bitcoin scan is a handful of requests, both through two onion circuits. Expect the wallet pages to feel a few seconds slower than on the clearnet. The swap itself is unaffected.

Your Bitcoin only ever moves after you confirm the lock in your browser, and aborting before that is always free.

The maker side is still open to anyone: zeto.cash/run-a-maker.

Keep the reports coming. The onion exists because you asked for it, and three of the fixes above came out of one afternoon of someone testing the wallet over Tor and telling us what broke.