mirror of
https://github.com/RoboSats/robosats.git
synced 2024-12-14 19:36:24 +00:00
2.9 KiB
2.9 KiB
RoboSats - Buy and sell Satoshis Privately
RoboSats is a simple and private way to exchange bitcoin for national currencies. Robosats simplifies the peer-to-peer user experience and uses lightning hold invoices to minimize custody and trust requirements. The deterministically generated avatars help users stick to best privacy practices.
Try it out
Bitcoin mainnet:
- Tor: robosats6tkf3eva7x2voqso3a5wcorsnw34jveyxfqi2fu7oyheasid.onion
- Url: robosats.com (Coming soon)
- Version: v0.1.0-mvp
Bitcoin testnet:
- Tor: robotestagw3dcxmd66r4rgksb4nmmr43fh77bzn2ia2eucduyeafnyd.onion
- Url: testnet.robosats.com (Coming soon)
- Latest commit.
Always use Tor Browser and .onion for best anonymity.
How to use it
How it works
Alice wants to buy satoshis privately:
- Alice generates an avatar (AdequateAlice01) using her private random token.
- Alice stores safely the token in case she needs to recover AdequateAlice01 in the future.
- Alice makes a new order and locks a small hold invoice to publish it (maker bond).
- Bob wants to sell satoshis, sees Alice's order in the book and takes it.
- Bob scans a small hold invoice as his taker bond. The contract is final.
- Bob posts the traded satoshis with a hold invoice. While Alice submits her payout invoice.
- On a private chat, Bob tells Alice how to send him fiat.
- Alice pays Bob, then they confirm the fiat has been sent and received.
- Bob's trade hold invoice is charged and the satoshis are sent to Alice.
- Bob and Alice's bonds return automatically, since they complied by the rules.
- The bonds would be charged (lost) in case of unilateral cancellation or cheating (lost dispute).
Contribute to the Robotic Satoshis Open Source Project
See CONTRIBUTING.md
Original idea
The concept of a simple custody-minimized lightning exchange using hold invoices is heavily inspired in P2PLNBOT by @grunch
License
The Robotic Satoshis Open Source Project is released under the terms of the AGPL3.0 license. See LICENSE for more details.