Multisig GUI wizard
What
1 — User-friendly desktop app
A cross-platform Monero multisig wallet GUI aimed at people with zero technical background. Main capabilities:
-
Create new multisig wallets over Tor with just a few clicks.
-
Operate an existing multisig wallet
- start a new transaction and collect co-signatures
- fetch the latest wallet state from peers to show an up-to-date balance
-
Handle several multisig wallets at once in one window.
-
Auto-generate multisig wallets for e-commerce (details below).
2 — Local API + headless client
The same functionality exposed as a locally hosted API so a website back-end can:
- spin up new multisig wallets between predefined peers,
- push or pull wallet data,
- drive the full signing flow automatically.
Ideal for shops, marketplaces, or escrow services that want to integrate Monero multisig without reinventing the wheel.
How
Tech stack
| Purpose | Technology |
|---|---|
| GUI | Qt /QML |
| Back-end | Python |
| Wallet ops |
monero-rpc (one process per wallet) |
| Data exchange + identity | Tor (bundled binaries) |
- The app bundles and launches both Tor and the required
monero-rpcdaemons in the background; rpc logs are viewable in the GUI. - Built with Qt and Python, so installers can be shipped for Linux, macOS, and Windows.
Why
Multisig can dramatically cut fraud and boost trust, but today it is too hard for non-experts. By hiding the complexity we make multisig:
- As easy to use as a normal wallet --> broader adoption.
- Instantly useful for e-commerce through auto-created 2-of-3 wallets.
Quick e-commerce flow
-
Actors
- Buyer
- Seller
- Marketplace (e.g., XMRBazar)
Each runs the app and thus has an onion address.
-
Buyer and seller mark the marketplace’s onion as a trusted peer (one-time setup).
-
At checkout the marketplace’s back-end calls the API to request a new 2-of-3 wallet for the three parties.
-
The request for a new wallet pops up in the buyer’s and seller’s apps; the wallet and payment address are generated automatically—no manual data exchange.
-
Buyer sends funds to that address.
-
When conditions are met, the app gathers the necessary
multisig‐info, proposes a payout transaction, and each party simply clicks “Sign”.
If everyone’s app is open, the whole round-trip can finish in under a minute. All raw transaction hex and rpc logs remain available for power users who want to inspect or broadcast manually.
The same interface also works for shared treasuries among any number of co-signers.
Who
I previously built two (now archived) Monero projects:
-
Nibelungx.com – swaps using monero as collateral https://www.reddit.com/r/Monero/comments/14s48b1/nibelungxcom_new_prediction_market_and_index/ https://www.reddit.com/r/Monero/comments/16ug7s8/nibelungxcom_is_closing_down_on_31st_october/
-
Sigmanero.org – community sports betting with multisig tooling (revealed many pain points this proposal addresses) https://www.reddit.com/r/Monero/comments/1c8rzib/announcement_sigmaneroorg_sports_betting_with/ https://www.reddit.com/r/Monero/comments/1gn8jer/announcement_sigmaneroorg_is_closing_down_monday/
To prove commitment, I’m asking for payment only after deliverables are in users’ hands:
| Milestone | Payout |
|---|---|
| Fully working Linux GUI + source code | 50 % |
| Headless/API version | 25 % |
| macOS & Windows builds + tutorials | 25 % |
This schedule ensures the community pays only for tangible, finished software that moves Monero multisig from “power-user toy” to everyday tool.
Thank you