Robosats accepts anything, you can even trade with chickens 🐔

RoboSats v0.8.7-alpha is now out! 🚀

Changes

What's new

TL;DR Security hardening across the full stack, live coordinator ranking by DevFund donations, federation consensus mechanism, image upload in encrypted chat, 3 new payment methods, and new coordinators (Eleuteria, Freeport, Ammanaya).

For Users

• New coordinators joined the federation: Eleuteria, Freeport, Ammanaya — FreedomSats removed
• Image uploads in encrypted chat — Users can now upload E2E encrypted images in the order chat via Blossom. Only available on coordinators that opt in.
• Federation consensus mechanism, learn more here https://github.com/RoboSats/robosats/pull/2683
• Live coordinator ranking — coordinators are now sorted by their actual real-time DevFund donation value (devfund% × fee rate), falling back to the static federation.json value when unreachable

New payment methods

• eBay Gift Card
• MobilePay
• PYUSD

Bugs

• Fixed PGP armor blank line being stripped when escaping robot key headers, which broke PGP verification
• Fixed null premium default blocking order creation in the maker form
• Fixed sensitive data exposure on password-protected orders — location and description are now redacted from non-participants; password-protected orders are also excluded from the public order book
• Fixed Server-Side Request Forgery vector in the Android WebView interface
• Fixed Redis 8.x channel layer timeout causing WebSocket disconnections

For Coordinators

• Federation consensus mechanism, learn more here https://github.com/RoboSats/robosats/pull/2683
• BLOSSOM_ENABLED — new opt-in env var to re-enable image uploads in chat (off by default); requires a Blossom blob server running behind the coordinator
• STRFRY_HOST / STRFRY_PORT — new env vars for the embedded Nostr relay
• DEVFUND is now exposed publicly via GET /api/info/ and used live by clients to weight coordinator lottery ranking — keep it accurate
• Redis cache for public endpoints (/api/book/, /api/info/, etc.) — reduces DB load significantly under traffic
• CLN pinned to v25.09.3 — holdinvoice v4.0.0 is incompatible with CLN v25.11+; do not upgrade CLN beyond v25.09.x until a compatible holdinvoice release exists
• LND updated to v0.21 with HTLC_SET_ONLY lookup and /v2/router/send REST path fixes
• GPG keys are now also purged when cleaning expired robot accounts
• Fixed CSRF protection — DisableCSRFMiddleware replaced with the standard Django CsrfViewMiddleware (admin fully protected; DRF API views remain exempt via APIView)

https://github.com/RoboSats/robosats/releases/tag/v0.8.7-alpha

RoboSats v0.8.4-alpha is now out! 🚀

This is probably the release with the most widely spread contributors in this project's history. Thank you all!

https://github.com/RoboSats/robosats/releases/tag/v0.8.4-alpha

Changes

What's new

TL;DR

Multiple UI improvements and bugs fixed.

For Users

• Payment methods input clears when switched to Swap @aftermath2
• API errors are globally displayed in a toast message @keshav0479
• Bond displays bellow Premium in mobile view @keshav0479
• Orders are automatically sorted by premium when filtering by SELL / BUY type @FedericoLuque
• Bond amount in sats estimated prior to order creation @FedericoLuque

New payment methods

• Binance Pay
• DANA

Bugs

• Typo in federation table @aftermath2
• Wrong swap calculation for "You receive..." @FedericoLuque
• Wrong calculation for "You receive..." in range orders @keshav0479
• WhiteEyeSats and Alice nodeapp and nostr values @Wizard079 @KoalaSat
• Pin colors are now static in map view @Wizard079

For Coordinators

• Alpine updated to allow SOCKS5 @MattDHill
• Security updates
• Update traditional scripts @jerryfletcher21
• Upstreams updated to 127.0.0.1 @Wizard079
• Nostr keys are now correctly stored from headers @KoalaSat

RoboSats v0.8.3-alpha is now out! 🚀

What's new

TL;DR

2 new coordinators, some bug fixing and security updates.

For Users

• 2 new coordinators: WhitEyeSats (#2295) and Alice (#2309)
• Telegram links removed
• Nostr events now includes order descriptions
• When the users tries to load the app in Tor Browser with incompatible browsing configuration, a warning message is now displayed.
• Better error messages for Order form

Bugs

• External orders with no available links now don´t display any link button
• In maker form, clear button now fully clears all inputs

For Coordinators

Security updates

https://github.com/RoboSats/robosats/releases/tag/v0.8.3-alpha

FYI

is fully operative and not showing error messages to their users

RoboSats v0.8.2-alpha is now out! 🚀

Changes

What's new

TL;DR

Order description added as optional attribute. Library updates and bugs fixing.

For Users

• Orders can now include descriptions. Available in "Advanced Options".
• Aggregated Order's meta data from Federation's book is now displayed in Order's view (Before it was only displaying data from the host).
• New Search dialog to help on-boarding users
• Currency is locked to BTC in Swaps form
• Revision of the Czech translation

Payment methods marked as reversible

• Revolut

New payment methods

• Zeam

Bugs

• Android app was not able to open Telegram app
• The Active robot feature is not available in the orders book view when connection is set to Nostr, yet it always displayed red for all robots.
• Refreshing the orders book is not necessary when connection is set to Nostr.
• Renewing orders with password now requires to re-enter a password.
• Sometimes orders were not found when adding a new robot with an active order
• Coordinators overview sometimes didn't load
• Order summary "Start Again" button wasn't working
• Used robots were not able to create new orders
• Advanced mode toggle sometimes didn't work
• "you receive" sats amount sometimes showed up incorrect values
• "Routing budget" amount showed sats instead of milisats
• Map now displays at zoom 1 (entirely) by default
• Sometimes the chat logs were not being sent on a dispute even if the user checked the option

https://github.com/RoboSats/robosats/releases/tag/v0.8.2-alpha

RoboSats v0.8.1-alpha is now out! :rocket:

Changes

What's new

TL;DR

• Brand new mobile app and mobile view
• New in-app private notifications system using nostr
• Revertible payments warning

[!Important] The new app version might remove your garage, make sure you backup your tokens before upgrading

For Users

• Nostr notifications following NIP-17. Coordinators now send nostr anonymous encrypted messages to robots. The client fetches federation's relays for this notifications and display them on a new notifications center.

[!Note] New notifications won't work until Coordinators upgrade to this version

• New mobile app written from scratch. Improving performance, security and usability.
• New mobile view (App and Web). Improving user experience and using nostr for App notifications. No more 5 minutes queries, notifications are now instant.
• Improved Robot profile window.

https://github.com/user-attachments/assets/f7d35ace-6e29-4235-b09a-4149b0504921

• Libraries security updates.
• We have created a list of payment methods consistently reported by the community as doing reverts to their transactions.

https://github.com/user-attachments/assets/a9d93bfb-43ad-432b-a57b-8eb381cb7700

Payment methods marked as reversible

• PIX

New payment methods

• USDC
• Paysend

Bugs

• Order matching view now displays relevant order data.
• Fixed some visual bugs caused by previous UI update.
• F2F orders are again created with coordinates.
• armeabi-v7a and arm64-v8a architectures signatures and versions fixed.
• Order view showing wrong amount definitively Changes

https://github.com/RoboSats/robosats/releases/tag/v0.8.1-alpha

Also available on

and IzzyDroid repo

Thank everyone (including coordinators) for the huge help provided to test the new Android app. We think this time we broke all records of people getting involved, you are an awesome community!

We updated the apk with all the fixes, it would be awesome to double check this one so we can release this week!

THANK YOU

https://github.com/RoboSats/robosats/releases/tag/v0.8.1-alpha

Last and final version of the new App. If everything goes well we'll publish it as it is. Please help us to test!

Notifications won't work until Coordinators upgrade, which will only happen once we officially publish this release

https://github.com/RoboSats/robosats/releases/tag/v0.8.1-alpha

RoboSats v0.8.0 is now out! 🚀

https://github.com/RoboSats/robosats/releases/tag/v0.8.0-alpha

What's new

For 3rd parties

⚠️ Coordinators will now require a valid nostr pubkey on headers:

https://github.com/RoboSats/robosats/blob/development-docs/development/docs.md#authentication

For Users

• Better custom payment methods tool

• To avoid performance issues, the coordinator ratings verification is now manual.

• New trade breadcrumb

• Mobile nav bar

• WebLN payments (i.e. Alby extension) window now use Hold invoices

• All translations updated (via LLM)

• New warning dialogs to help users understand the risks of each step

• Improved general performance
• Remember hidden self-hosted alert
• Fixed silent failure for invalid invoices
• Coordinator onchain payments are now disabled for swaps. These payments are unnecessary on this scenario and cause user mistakes.
• Libraries upgrades

Any Windows user willing to test the latest version of our Windows Client?

We got some reports of the app not loading in precious versions https://github.com/RoboSats/robosats/releases/tag/v0.7.9-alpha

Any feedback on that will be appreciated (and zapped)

RoboSats is a P2P platform for buying and selling BTC-Lightning, designed to facilitate fast, secure, private, and decentralized exchanges. It is a free and open-source project created altruistically by

as a gift to humanity, and behind every transaction is a team and a community committed to excellence:

1. The Coordinators (currently 6 active)
   They enable transactions, ensure security, and mediate between parties.
   They charge a small fee, part of which goes to a development fund to support future improvements.
   They are solely responsible for the orders they coordinate, and users should do their research before deciding to trust them. https://t.me/robosats/34101

2. The Federation

   npub1v3tgrww…c6yvjh

   t leads the development while

   npub1yxcj3cd…gmmzmp

   takes care of the community. They also stay in touch with any coordinators who wish to receive recommendations or collaborate on solutions. Both work almost entirely alone, voluntarily and without compensation, driven solely by passion and a shared vision for a project that is essential for the community and the freedom of individuals.

The magic of RoboSats, as with other free software projects, emerges when those who enjoy the platform, have their questions answered, or receive selfless help, decide to give back a bit of that value.
These gestures are what create community and ensure the sustainability and future of this project.

How can you get involved?

• Are you a programmer? Look for an issue on GitHub, submit your pull request, and earn a reward for your work in sats. https://github.com/RoboSats/robosats/issues

• Have you noticed something that isn’t working or that you’d like to improve? Let us know! Every piece of feedback enhances the experience for thousands of users. If you’re up for it, you can also edit the reference guides yourself: https://learn.robosats.org/

• Do you believe time has a price? Send us some sats. This helps us maintain the infrastructure and recognize the voluntary efforts of everyone day after day. Do you like us? Have we solved a problem thanks to our work? Have we saved you time from researching alone? Put a number on the value you’ve received and send it our way. We may not be able to share a coffee together, but you can treat us to one (and we’ll think of you while we enjoy it 🤖☕). Every small gesture builds community and helps keep the wheel turning.

Lastly, thank you. Infinite thanks to all who walk with us on this journey day after day. It’s wonderful to walk alongside you. Join RoboSats and let’s build a slightly better world together!

Written with ❤️ and ⚡ somewhere on Earth.

RoboSats v0.7.9 is now out! 🚀

What's new

For Users

• Orders can be created now with a password (Advance settings). These orders won't appear in the public orders view and can be taken only if the robot inputs the same password.
• Orders can be fetch now by URL in the Book view
• New coordinator: FreedomSats #2004
• npub15369wu3…3apswl

  orders now available in Global orders book
• Chat fix for Start9/Umbrel

For Coordinators

• Traditional non-docker environment files updated

https://github.com/RoboSats/robosats/releases/tag/v0.7.9-alpha

RoboSats v0.7.8 is now out! 🚀

What's new

• New coordinator: LibreBazaar https://github.com/RoboSats/robosats/issues/1903
• New payment method: Nomad
• Major libraries update
• Coordinator ratings are now cryptographically verified
• Private chat message are also sent as nip17 as part of the full migration of the chat to nostr
• Fix Start9/Umbrel nostr relay connection
• Fixed a situation where sometimes orders table loads in page 2
• Android adaptive Icons support

https://github.com/RoboSats/robosats/releases/tag/v0.7.8-alpha

RoboSats v0.7.7 is now out! 🚀

What's new

For Users

https://github.com/user-attachments/assets/cd1f9ed4-5201-4a01-b322-e2f574249948

• New coordinators view.
• Available coordinator reviews signed by both the robot and the coordinator.

https://github.com/user-attachments/assets/59231362-5f86-4518-8c82-ecac385e2155

• Coordinators now display in their profiles market price sources.
• Users are now warned if they try to cancel a non taken order after a payment attempt.
• Some bugs fixed
• Uzbek so'm currency now available

For Coordinators

• Library updates

https://github.com/RoboSats/robosats/releases/tag/v0.7.7-alpha

Also available on

https://following.space/d/6lrt6c9rzr2h

🚀 RoboSats 0.7.6 is now out. Download and changelog here:

https://github.com/RoboSats/robosats/releases/tag/v0.7.6-alpha

For Users

• Dispute statement now requires a contact method to be submitted.
• Coordinator rating over nostr (BETA)
• Token input now clears up blank spaces.
• Added some messages to the trade workflow to answer the most common questions.

For Coordinators

• Add cancel_status param to the cancel order action

Beware scams! https://robosats.org/docs/payment-methods/#scams

🚀 RoboSats 0.7.5 is now out. Download and changelog here:

https://github.com/RoboSats/robosats/releases/tag/v0.7.5-alpha

For Users

• When Javascript is disabled a box appears to help the user to enable it
• Users will now be advised when they select a coordinator not offering swamps in order creation

For Coordinators

• Now orders stay public even if there is a non-confirmed Taker, allowing multiple robots to try to take the order

This last one is specially important. It fixes an attack we detected to our liquidity. Some users continuously took orders without confirming to keep them hidden from the public book. After coordinators apply this version, the attack will no longer be possible.

#GoodFirstIssue

https://github.com/RoboSats/robosats/issues/339

https://github.com/RoboSats/robosats/issues/294

https://github.com/RoboSats/robosats/issues/135

https://github.com/RoboSats/robosats/issues/1812

https://learn.robosats.org contains a good bunch of documents and tutorials to start trading satoshis from scratch, even you are newbie.

Contributors already helped to translate the docs to:

• English
• Spanish
• French
• Portuguese

Did you know you can help with the translations to other languages!? Check: https://github.com/RoboSats/robosats/blob/main/CONTRIBUTING_DOCS.md

Same feeling 🫂

No, the best option is to wait for the trade to time out and then report to your coordinator how the other part didn't followed the contract by sharing your chat history.

The 2 peers should follow the contract as established, anything different is punished with the lost of the bond by the part not respecting it.

Agora você pode aprender Robosats em português! Visite https://robosats.org/pt

About the federation. Being a member implies only 2 points:

1 - Coordinators donate a auto assigned % of their gains from every order to the Robosats Development Fund.

2 - Coordinators share and store the global (all coordinators) order book in the form of nostr notes.

iOS requires KYC even for development. It also forces to follow so many payment related rules to be published to their store they basicaly kicked out themselves from being an option for Robosats.

And it doesn't seem to get any better in the near future:

https://techcrunch.com/2025/02/21/apple-pulls-icloud-end-to-end-encryption-feature-for-uk-users-after-government-demanded-backdoor/

You can always use Tor, Desktop or Umbrel/Start9

No, that's why we have Coordinators. Coordinators are individuals running a LN node and a Robosats specific software, when there is a dispute on the trade they get involved and act as intermediary.

As far, you are doing things right and can prove it, there is nothing to worry about.

🚀 RoboSats 0.7.4 is now out. Download and changelog here:

https://github.com/RoboSats/robosats/releases/tag/v0.7.4-alpha

• You can now see @lnp2pBot orders on RoboSats mobile app
• Changed URLs to https://robosats.org and new onion
• Order creation view now displays all available payment methods
• Libraries updates

Coordinators now have their own NIP05 from robosats.org 🤖 just another security layer to make sure you are to talking to the right people

You can do that already 😊

And not only that you literally have a free input to exchange your sats for ANYTHING