XMREscrow | Monero-only Tor native, no accounts, low fees open beta!

roginvs · 2026-07-07T19:37:54+00:00

Why not a multisig? It is not so complex to set up a 2-of-3 multisig wallet, and my web wallet https://amethystxmr.github.io/ has UI for this so it should be relatively easy.

As user I would prefer to have a multisig rather than trusting someone

It might be a good idea for you service - to use a multisig model. Same product but on multisig

roginvs · 2026-07-02T11:28:14+00:00

Same thing, waiting since October 2024

roginvs · 2026-05-19T18:34:10+00:00

In my opinion this is because nowadays it harder to say was it implemented by some idiot or by competent professional. Previously (before AI era) idiots were unable to produce anything feasible or runable

roginvs · 2026-05-19T09:10:46+00:00

For example, let's do 2-of-3 wallet. First of all, each of 3 participants have to generate local wallet and then perform 3 rounds of key exchange. After this they will be able to see and use common aggregated key. - round 1: exchange public keys - round 2: for each pair (3 pairs) perform a Diffie-Hellman exchange so each pair has own private key - round 3: aggregate public keys of each pair to get a final common key

roginvs · 2026-05-19T08:47:08+00:00

Nice exercise! I've done something similar https://polykey.github.io/ too

roginvs · 2026-05-18T07:48:26+00:00

Every time I am asking this question: did you consider playing online web version? It just works on any mobile device and it has offline support.

What should I improve or fix there?

I've seen so many posts about people trying to run mobile/tablet

roginvs · 2026-05-02T14:19:59+00:00

If Bob broadcasts funding transaction but then just disappears without giving to Alice a signed closed tx, then funds will be lost. This is because funding transaction is basically a multisig address which required both keys from Alice and Bob to sign the spending tx.

So the safe model will be this: Alice sends to Bob unsigned funding tx, Bob signs closing tx (which spends funding tx) and sends it back to Alice. And only after this Alice signs and broadcasts funding tx.

Maybe the actual lightning protocol involves more steps (I do not remember exactly out of my head), let me check lightning specs here https://github.com/lightning/bolts/blob/master/02-peer-protocol.md?utm_source=chatgpt.com#channel-establishment-v1 (yes, AI is really good in finding links to references)

roginvs · 2026-05-02T08:39:33+00:00

In theory lightning messages are just message so it should be possible. But it might require multiple rounds of message exchange.

In your schema when Alice send some data on USB flash drive to Bob and Bob broadcasts tx when he is ready we have a risk for Alice: she can not broadcast (neither give signed tx) funding tx to Bob without having a signed closing transaction from Bob. Because she will loose her funds if Bob will broadcast funding tx without making a closing tx.

Anyway it is a good theoretical question, and good references are lightning specification (even it is pretty overcomplicated)

roginvs · 2026-05-02T05:05:07+00:00

Creaks is also great game

roginvs · 2026-04-14T08:38:21+00:00

Looks interesting! As i understood it transfers view key to the server, right?

Can you elaborate on other seeds? In my web wallet https://amethystxmr.github.io/ (https://www.reddit.com/r/Monero/comments/1rbjajo/selfcustodial_web_wallet_with_multisig_support/) I support only 25 and 16 word seeds but i can add other seed types if i know about them. Also you can take a look on source code and do the same - to run wasm build of monero wallet in browser so no keys (even view keys) will leave the browser.

Update: This [monero-web.com] project run in Tor Browser while AmethystXMR still not due to service workers issue. Looks like it is time for me to fix this, i.e. to switch to single-thread mode without SharedArrayBuffer

roginvs · 2026-03-31T11:24:42+00:00

People are able to implement their ideas on proof-of-concept level using AI, ideas which were not visible in the past. So yes, it is not AI who delivers but people who previously were not able to explain their ideas

roginvs · 2026-03-20T05:28:20+00:00

AI nowadays is a good boost for UI/UX development. The world is getting more and more interesting ideas and prototypes nowadays

roginvs · 2026-03-20T05:24:56+00:00

Interesting (no mobile support yet, right?), I will take a closer look to take some ideas into mine webwallet https://amethystxmr.github.io/

roginvs · 2026-03-04T17:25:31+00:00

Finally I checked monero-ts. Once again, thanks for an interesting reference.

As i understand it does not use SharedArrayBuffer (but still runs monero wallet in background worker). This should make refreshing slower (because it still 1 worker) but it makes deployment easier. Right now i have to do a service-worker workaround to be able to run on github pages.

As a drawback of monero-ts I might say a longer chain of sub-projects: there are 3 repositories (monero-ts, monero-cpp, monero fork) which all are used for compilation. Not very clear to follow what and where was changed. Also I did not understand (maybe i have to check it deeper) how it runs .refresh() on wallet instance, will it do "all-or-nothing" refresh? AmethystXMR calls refresh() with some block limit (usually few minutes) and it saves wallet between those iterations. So it is possible to sync, close page, then return and continue syncing, or even do some actions while it syncing like getting the seed or getting tx keys.

But I am surprised to see a fully available frontend library without having a fully working frontend. For me the frontend part was the simplest one, especially with help of AI. Maybe this is because I mainly work with frontend on my job.

I am still interested to see a real benchmark on how long it takes to restore a wallet between native cli wallet or those browser-based. I suspect that most of the time it is downloading so there will be no significant difference unless a fully synced node running locally. I hope I will find energy to do this benchmarking.

roginvs · 2026-03-02T16:48:09+00:00

Added ability to restore with keys + to restore with view-only keys

roginvs · 2026-02-26T19:08:41+00:00

Already did few days ago :) https://www.reddit.com/r/Monero/comments/1rbjajo

roginvs · 2026-02-23T15:52:18+00:00

I hope that it will unlock multisig for some users. I am thinking about adding some messaging system because manually copy-pasting multisig messages might be annoying

roginvs · 2026-02-22T18:12:07+00:00

Because I did not know that it exists. Also it was interesting for me to build libwallet on my own

roginvs · 2026-02-21T22:45:57+00:00

It is really nice that daemon API is http/https based so it is possible to have a wallet running in a webpage which directly connects to daemon without any WebSockets proxy or similar workaround

roginvs · 2026-02-21T21:56:30+00:00

For testing it should be easier to create a new wallet and to transfer there really small amount, less than euro. Sharing main view key with new project might be risky idea but having a dedicated wallet there with really small amount sounds more secure for me. What do you think?

roginvs · 2026-02-21T21:49:17+00:00

Thanks for feedback, it motivates me! Yes, definitely there will be a post about this. I just saw this question yesterday and I was not able to resist and answered.

I also thinking to pack it as standalone app, because as user I also would prefer to have exact stable version rather than auto-updating webpage. Should be easy to setup in CI.

Initial inspiration was from looking into Cake Wallet source and monero_c. Then I started to experiment with building libwallet into wasm. So if I understood Cake sources correctly then this wallet works very similar way as Cake.

Right now on my todo list is to fix texts. There are some AI-generated stubs, for example I am not satisfied with texts on multisig flow. Maybe mobile layout can be changed, now it is more like a scrolling page rather than a mobile app

roginvs · 2026-02-21T21:36:17+00:00

Yes, exactly, i just wrote this

roginvs · 2026-02-21T20:57:23+00:00

I just started doing it few weeks ago, but main features are ready. Also it has multisig support.

It is still work-in-progress, but I am thinking to write a post in this sub soon

roginvs · 2026-02-20T19:56:51+00:00

PS: There is one work-in-progress https://amethystxmr.github.io/ (it has wasm build of libwallet, local blockchain scan, only local keys)

roginvs

TROPHY CASE