Skip to content

Releases: RoboSats/robosats

robosats-android-3b18f6a

01 May 18:47
8d2ca28
Compare
Choose a tag to compare
Pre-release
chore: fix integration test artifact naming

robosats-android-ea3ff1c

30 Apr 21:01
9071597
Compare
Choose a tag to compare
Pre-release
improve/update documentation in api/oas_schemas.py (#1244)

Specify that the amount of the invoice sent in `update_invoice`
should take into consideration `routing_budget_ppm`.
Specify that the signed messages should be signed with SHA512.
Remove the warning that in the future canceling not taken orders
might result in losing the bond.
Fix a broken link.
Specify that the PGP key should be ed25519/cert,sign+cv25519/encr.

robosats-android-1c11ecb

31 Mar 15:31
9ef84b2
Compare
Choose a tag to compare
Pre-release
Italian translation (#1195)

* Update federation.json

* Update it.json

Hi , i have updated the italian transaltion.

* Update federation.json

---------

Co-authored-by: Reckless_Satoshi <[email protected]>

v0.6.0-alpha The Federation Layer

17 Mar 15:18
029e795
Compare
Choose a tag to compare

RoboSats v0.6.0 is now out! 🚀

Changes

New Features

Decentralization

RoboSats v0.6.0 introduces a major upgrade, introducing the RoboSats Federation, a decentralized system of independent coordinators to host orders, enhancing the platform's robustness and user experience. This version is a significant step towards decentralization, allowing users to interact with any coordinator seamlessly.

It's crucial to choose trustworthy coordinators due to the potential risks of malicious activity. The federated client is available for testing at specific URLs, with a stable release planned. Key features include multiple coordinators competing for users, decentralized instances for increased robustness, and a focus on coordinators profiles and trust.

Learn more in https://learn.robosats.com/robosats/update/pre-release-robosats-decentralized/

New avatar generator

Your Robot identity is now generated in your client app, when previously, the robot identity was created by the coordinator. This allows now for super-fast Robot avatar and nickname generation that works even if your connection to the coordinators is down. The new robot avatars, are in fact, more diverse and better looking, however, the same token will now yield a different avatar when compared to v0.5.4 (but the robot identity remains the same, also keeping the same nickname).

Bug Fixes and Performance Improvements

The whole app architecture is new. There might be new bugs, solved bugs, worse performance and better performance: who knows!! :D

Special thanks

Special thanks to @KoalaSat who has driven some of the largest development pushes needed to get The Federation Layer fully working.

Android

The Android app is currently not supported on this early phase of the Federated app.

Docker Images

Coordinator Backend Image v0.6.0-alpha (Docker Hub)

docker pull recksato/robosats:v0.6.0-alpha

Client App Image v0.6.0-alpha (Docker Hub)

docker pull recksato/robosats-client:v0.6.0-alpha

See nodeapp/docker-compose.yml for an example docker-compose usage of the robosats-client image.

What's Changed

Read more

v0.5.4-alpha

22 Jan 11:22
bf505ca
Compare
Choose a tag to compare

RoboSats v0.5.4 is now out! 🚀 RoboSats client apps before v0.5.1 are no longer be compatible.

Changes

This is a minor release with some small enhancements and bug fixes. This is the last release before the federated client release.

  • Dependency updates and security fixes.
  • Coordinator serves robot hash_ids needed for >v0.6.0 client side robot identity generator.
  • Recommended and minimum onchain fees for payouts are now more accurate.
  • Devfund node has moved. The new node now has public access to the invoices services (read-only).
  • Fix book re-render on swap/fiat change (by @aftermath2)
  • Docs have been fully translated to Spanish by @OSFr0g
  • Perf increase on coordinator image build by @proof-of-reality
  • Build new full integration tests on testnet.
  • Fix API /chat endpoint bugs.
  • Updated API docs, now OpenAPIspec is tested during the integration tests.
  • Fix buggy pricing for ARS.
  • New currency Albanian LEK.
  • Updated Russian translation.

Android

The Android app is not currently supported. It will come back stronger in the future.

Docker Images

Coordinator Backend Image v0.5.4-alpha (Docker Hub)

docker pull recksato/robosats:v0.5.4-alpha

Client App Image v0.5.4-alpha (Docker Hub)

docker pull recksato/robosats-client:v0.5.4-alpha

See nodeapp/docker-compose.yml for an example docker-compose usage of the robosats-client image.

What's Changed

Read more

v0.5.3-alpha Now we see each other.

18 Oct 09:25
2af9af9
Compare
Choose a tag to compare

RoboSats v0.5.3 is now out! 🚀 RoboSats client apps before v0.5.1 are no longer be compatible.

Changes

New Features: Face to face.

We have introduced a new feature, F2F (Face-to-Face), allowing users to add a location for face-to-face cash trades. The book page now displays a map with all F2F orders. For privacy reasons, the exact location of your order is slightly randomized (uniform random 15 x 15 Km noise) when you click on the map to locate it. This means it's not possible to be precise, and the exact location can only be shared on the encrypted chat. Please note that using high-resolution maps can leak your IP to external tiling servers if you are not using Tor Browser.

Of course, adding a geolocation tag to your order is only a good idea if you want to use face-to-face cash as a payment method. You can completely disregard this feature if you do not want to use this payment method.

Thank you @KoalaSat who single-handedly implemented the F2F upgrade. Make sure to zap some ⚡ Sats ⚡ his way!

RoboSats-deploy Coordinator Orchestration

We have released the RoboSats-deploy coordinator orchestration in https://github.com/RoboSats/robosats-deploy

Bug Fixes and Performance Improvements

  • Dependency updates.
  • Small bug fixes.
  • Improved DB Writes performance related to last_login user field.
  • Fix small bug on order logging that made automatic dispute resolutions fail.
  • Devfund Donation Pubkey has been updated to RoboSats experimental LND2 node.

Android

Click to download universal RoboSats APK for Android
Smaller bundles for each CPU architecture available in the attachments.

Verify the app using GPG:

  1. Download the ascii armored signature

  2. Run this command on a directory that contains the apk file and and the ascii armored signature.
    gpg --verify robosats-v0.5.3.alpha-universal.apk.asc

  3. Verify the signer is actually Reckless-Satoshi (fingerprints match): B4AB5F19113D4125DDF217739C4585B561315571

Alternatively you can also verify with the release with the SHA256 checksum.

Known missing features:

  • Android APK has no sound or notifications.

Docker Images

Coordinator Backend Image v0.5.3-alpha (Docker Hub)

docker pull recksato/robosats:v0.5.3-alpha

Client App Image v0.5.3-alpha (Docker Hub)

docker pull recksato/robosats-client:v0.5.3-alpha

See nodeapp/docker-compose.yml for an example docker-compose usage of the robosats-client image.

What's Changed

Full Changelog: v0.5.2-alpha...v0.5.3-alpha

v0.5.2-alpha

08 Sep 16:31
6f9adde
Compare
Choose a tag to compare

RoboSats v0.5.2 is now out! 🚀 RoboSats client apps before v0.5.1 might no longer be compatible!

Changes:

  • New language: Swahili. Thank you @turizspace!
  • Improved French and Italian translations. Thank you @LeoSpyke and @jinformatique !
  • Update CLN (core-lightning) plugin (@Daywalker91) and CLN base version to v23.08
  • Add verbose order logs to coordinator panel: a detailed timestamped record of every change to an order from creation to finalization.
  • Improved invoice descriptions.
  • New coordinator maintenance messages.
  • Small UI fixes.
  • Fix pinch to zoom Android.
  • Add bd taka as currency @dapsavoie /
  • Update communities links in client app.
  • Patch Android bogus "connected" chat status when connection is offline.
  • Date to date ranges added to /api/ticks.
  • New admin actions for dispute resolutions.
  • Force PGP signed invoices and onchain addresses (multi-coordinator security).
  • New RoboSats Federation basis v0.6.0~1
  • Fix allow auth header to carry pgp keys: easier authentication for federation from browser.

Android

Click to download universal RoboSats APK for Android
Smaller bundles for each CPU architecture available in the attachments.

Verify the app using GPG:

  1. Download the ascii armored signature

  2. Run this command on a directory that contains the apk file and and the ascii armored signature.
    gpg --verify robosats-v0.5.2.alpha-universal.apk.asc

  3. Verify the signer is actually Reckless-Satoshi (fingerprints match): B4AB5F19113D4125DDF217739C4585B561315571

Alternatively you can also verify with the release with the SHA256 checksum.

Known missing features:

  • Android APK has no sound or notifications.

Docker Images

Coordinator Backend Image v0.5.2-alpha (Docker Hub)

docker pull recksato/robosats:v0.5.2-alpha

Client App Image v0.5.2-alpha (Docker Hub)

docker pull recksato/robosats-client:v0.5.2-alpha

See nodeapp/docker-compose.yml for an example docker-compose usage of the robosats-client image.

What's Changed

New Contributors

Full Changelog: android-a5d33c6...v0.5.2-alpha

v0.5.1-alpha

29 May 18:36
f3a7701
Compare
Choose a tag to compare

RoboSats v0.5.1 is now out! 🚀

Changes:

  • CLN (core-lightning) can now be used as robosats coordinator node vendor. It is however, experimental, and not recommended in mainnet. Thank you for this great contribution @Daywalker91 !
  • Full rework of the Lnproxy feature by @shyfire131 . Thank you!
  • Chat now allows multiple line inputs by @shyfire131
  • RoboSats client should now work inside of Blixt's webln browser. Thank you @SynthLock for the tips and debugging!
  • API requests to POST /order that contain important information, i.e, the payout invoice or address, are now signed by the robot PGP key and validated by the coordinator. This way, on a multi coordinator set up, a robot can potentially be re-used across several coordinators without risk of identity stealing (auth token) by a rogue coordinator (alla man-in-the-middle).
  • New Keysend functionality. RoboSats coordinators can now, voluntarily, keysend devfund donations automatically for each trade they host.
  • Simplify coordinator updates. Now migrations are tracked and apply on first start-up. Static files are collected on start up as well.
  • New maker form switch for exact and range amounts thanks to @JooVLC
  • Fix negative premium field by @JooVLC
  • Self-hosted node app has been fully re-worked. It is now based on Alpine (size went down from 130MB to 7MB) and the ram-heavy dependencies have been dropped. The app is now lighter, and fully self-contained, as no part of the frontend depends on the existing coordinator anymore.
  • Overall update of Android app, slightly better performance and smaller size.
  • Sounds do work on the Android app now.
  • New reviews section to learn.robosats.com by @athena-alpha
  • New tutorial by @BitcoinQnA
  • Add new payment methods: Sinpe movil and Qiwi.

Android

Click to download universal RoboSats APK for Android
Smaller bundles for each CPU architecture available in the attachments.

Verify the app using GPG:

  1. Download the ascii armored signature

  2. Run this command on a directory that contains the apk file and and the ascii armored signature.
    gpg --verify robosats-v0.5.1.alpha-universal.apk.asc

  3. Verify the signer is actually Reckless-Satoshi (fingerprints match): B4AB5F19113D4125DDF217739C4585B561315571

Alternatively you can also verify with the release with the SHA256 checksum.

Known missing features:

  • Android APK has no sound or notifications.

Docker Images

Coordinator Backend Image v0.5.1-alpha (Docker Hub)

docker pull recksato/robosats:v0.5.1-alpha

Client App Image v0.5.1-alpha (Docker Hub)

docker pull recksato/robosats-client:v0.5.1-alpha

See nodeapp/docker-compose.yml for an example docker-compose usage of the robosats-client image.

What's Changed

New Contributors

Full Changelog: v0.5.0-alpha...v0.5.1-alpha

v0.5.0-alpha

10 May 10:01
a5d0550
Compare
Choose a tag to compare

First release of the v0.5 minor version. 🚀 This one comes with a lot of the pre-requisites needed for a coordinator backend that is fully enabled for the federated frontend. We are now ~80% in our development towards the MVP federation, soon initiating the decentralization RoboSats!

Important

TLDR; Existing robots will stop working on the next release if you do not update ASAP your client to v0.5.0. In addition, other robots will see your status as "Inactive" (red dot) until you update. The referral system is now deprecated. Using a url like .../robot/<param> will now generate a new robot on-the-fly (but if you use an old referral link you will not be able to generate a new robot).

Robot authentication has been upgraded. New robots will use a token based auth (instead of sessionid+csrf). New authentications for never seen before auth tokens base91(sha256(robot_token)) will generate a new robot identity on-the-fly. Existing robots without an auth token, will be upgraded to the new auth method on their first login attemp if the frontend client has been updated to v0.5.0. Therefore, updating your client to v0.5.0 is highly recommended! Existing robots will stop working in next releases if they are not upgrade as the sessionid+csrf authentication method will be phased out. In addition, robot status active | seen recently | inactive is computed based on the last time the auth token was used: therefore those who do not update their client will be seen as inactive by other users.

What's new:

Mechanics

  • Referral reward system has been eliminated. The referral system is not compatible with a multi-coordinator system. Maybe in the future we can come up with ideas to implement a new referral system for the new many-clients/many-coordinators model.
  • Fairer bond slashing. When a maker bond is slashed on an order where the taker took a smaller order size (range orders), part of the slashed bond is rewarded back to the maker. This solves the issue with uneven stakes for orders with large amount range size where the taker takes an amount smaller than the maximum. Therefore, the max range size can now be safely increased for more versatile orders. It has now been increased from x8 to x15.
  • Max allowed mining fee for onchain payouts is raised from 100 Sats/vByte to 500 Sats/vByte. This limit is intended only to prevent fat-fingers mistakes. However, current mempool conditions do require of fees larger than 100 Sats/vByte.
  • Some easy disputes (e.g. your peer never shows up) are solved automatically. This increases speed and lowers custody risks. Helps with one of the main reason for disputes: robot token lost.

Backend:

  • Bump to django 4.2 from django 3. Bump to channels, daphne, drf and drf-spectacular.
  • New middlewaMechanicsre for authentication RobotTokenSHA256 . Builds over django-rest-framework token auth. Uses the sha256(robot.token) encoded as base91 as authentication token. Never seen before tokens will get a new user and robot generated on-the-fly, existing tokens are logged in (updated last_login field).
  • Disable CSRF.
  • Upgraded Coordinator panel. Improved tools, simplified search functions, dark model, renamed models and headers. There is still a lot of work to do, but this is the first part of the work towards making the coordinator panel more accessible to new coordinators.
  • Super optimized the size of the coordinator Docker image from 687 MB to 313 MB. In the spirit of making a RoboSats coordinator easier to run.

Frontend

  • Japanese is now available (Go to Settings -> Languages). Contributed by @aaroniumii.
  • Authentication now only based on base91(sha256(token)). This will enable many cool things down the road, but right now it should allow, for example, having multiple tabs with different robots. (Note, your garage will not be consistent across tabs! everytime a new tab is opened, the current state of the garage is loaded from the browser local storage, then on any garage change it will overwrite the object in your browser storage (potentially overwritting robots created on another browser tab).
  • The OrderDetails page shows a preliminary summary (click the expand button) with Satoshis to be sent/receive on the order amount row. This value is on preliminary, as the final trade price is only acquired at the moment the taker bond is locked.
  • There is a new helper text with an approximate amount in Satoshis that you are taking just below the text input for orders with range.
  • Trade summary export button also includes payment_hash and preimage of the lightning payment or address and txid of the onchain payment (only for buyers).
  • The token entropy (bits entropy and shannon entropy) is now computed in the frontend. If the token does not look complex enough (>128 bits of entropy and >4 shannon entropy), the frontend will not allow creating the robot for the safety of the user. You can see your robot's entropy value by downloading the json of the token garage.
  • Visiting the route domain/robot/<robot_token> will directly log you into that robot. This is the new use for that route param after deprecating the referral codes.
  • New payment icons: Advcash, Rakuten Pay.
  • It is now possible to have regular QR codes (dark dots over white background) while using the dark theme. Head to Settings and use the new switch for light/dark QR codes.
  • Many small maintainability and consistency improvements: e.g, navigation bar tabs and / browser router is now better linked. currentOrder is better linked with browser router params.

Android

Click to download universal RoboSats APK for Android
Smaller bundles for each CPU architecture available in the attachments.

Verify the app using GPG:

  1. Download the ascii armored signature

  2. Run this command on a directory that contains the apk file and and the ascii armored signature.
    gpg --verify robosats-v0.5.0.alpha-universal.apk.asc

  3. Verify the signer is actually Reckless-Satoshi (fingerprints match): B4AB5F19113D4125DDF217739C4585B561315571

Alternatively you can also verify with the release with the SHA256 checksum.

Known missing features:

  • Android APK has no sound or notifications.

Docker Images

Coordinator Backend Image v0.5.0-alpha (Docker Hub)

docker pull recksato/robosats:v0.5.0-alpha

Client App Image v0.5.0-alpha (Docker Hub)

docker pull recksato/robosats-client:v0.5.0-alpha

See nodeapp/docker-compose.yml for an example docker-compose usage of the robosats-client image.

What's Changed

Read more

v0.4.3-alpha

10 Apr 17:52
bdd0174
Compare
Choose a tag to compare

RoboSats v0.4.3-alpha is now out! 🚀

This release has many small fixes and new features:

  • Support for Iranian Toman (IRT) by @HT696
  • Order book performance improved by ~50%
  • Android app now launches your Telegram client or LN wallet when tapping on the QR codes.
  • Fix "no robot" error on Android app
  • Add multi-architecture builds for Android (size of APK down from ~120MB to ~30MB)
  • Improved order book column management (DataGrid updated to MUI-X v6)
  • Up-to-date Spanish translation by @Gravity2106
  • Up-to-Data Catalan translation by @BlueLynx21
  • Fix Tinkoff payment method collision by @dirtyroom969
  • Coordinator allows all origins (prerequisite for further Federation-enabled clients testings)
  • Improved handling of stray locked HTLCs
  • Improved handling of payout invoices that are "holded" or get stuck
  • Improved resource efficienty of celery tasks.
  • Fixed celery tasks to check on outgoing stuck payments consuming all celery worker threads.
  • Improved visuals on Telegram notifications ( ...have EmOjIs...)
  • New telegram notifications for first in-app chat message from peer and any subsequent message that has a gap of >5min

Android

Click to download universal RoboSats APK for Android
Smaller bundles for each CPU architecture available in the attachments.

Verify the app using GPG:

  1. Download the ascii armored signature

  2. Run this command on a directory that contains the apk file and and the ascii armored signature.
    gpg --verify robosats-v0.4.3.alpha-universal.apk.asc

  3. Verify the signer is actually Reckless-Satoshi (fingerprints match): B4AB5F19113D4125DDF217739C4585B561315571

Alternatively you can also verify with the release with the SHA256 checksum.

Known missing features:

  • Android APK has no sound or notifications.

Docker Images

Coordinator Backend Image v0.4.3-alpha (Docker Hub)

docker pull recksato/robosats:v0.4.3-alpha

Client App Image v0.4.3-alpha (Docker Hub)

docker pull recksato/robosats-client:v0.4.3-alpha

See nodeapp/docker-compose.yml for an example docker-compose usage of the robosats-client image.

Changelog

New Contributors

Full Changelog: v0.4.2-alpha...v0.4.3-alpha