* Fetch relay list from official lnproxy repo
My changes have been merged on the lnproxy.org repo, so RoboSats must not fetch from my fork of lnproxy anymore.
* Grant workflow job write perms
By default, the GITHUB_TOKEN only has read permissions. Write is required in order to update the list of relays.
* Update to latest version of checkout action
---------
Co-authored-by: +shyfire131 <shyfire131@shyfire131.net>
* Use new lnproxy API
- Use POST instead of GET, so create and send a body parameter
- Path is /spec/ instead of /api/, and list of relays from lnproxy will contain /spec already, so path parameter for ApiClient.post() is an empty string
* add lnproxy sync workflow
* Use new lnproxy JSON structure
* Remove virtualenv
doing this so that the “scripts” subfolder in .github/workflows can be added
* Move workflow script to subfolder
* Add translation support
Locale strings not added yet
* Simplify coordinator updates, automatic migrations and collect statics (#583)
* Delete commited proto files
* Run sync workflow weekly instead of hourly
* Tweak display name for relays
* Update sync script to be append-only
* Use new naming convention for relays
* Fix bitcoinNetwork hydration
* PR Feedback
- Change hook deps from settings.network to settings
- routing_msat param updates for lnproxy API
* Actually set host in settings
* Updated parsing of LnProxy response
---------
Co-authored-by: +shyfire131 <shyfire131@shyfire131.net>
Co-authored-by: Reckless_Satoshi <90936742+Reckless-Satoshi@users.noreply.github.com>
Co-authored-by: Reckless_Satoshi <reckless.satoshi@protonmail.com>
* Refactor fetchRobot
* Add appcontext
* Robot recovery fixes
* Add usecontext on maker and settings forms
* Add usecontext to booktable
* Add useContext to order page and main dialogs
* Small fixes
* Remove unused imports in python files
* Add black and isort dependencies
Also added pyproject.toml for isort config, but later can be used to
configure various other python tools
* Add flake8 in requirements.txt
* Add py-linter workflow
* Add android build workflow
* Initial webview on tsx template
* Insert ReactJS app from local
* Add Android app icon by @red_purdy (#174)
* Add files via upload
* Add files via upload
* Add files via upload
* Add files via upload
* Add files via upload
* Add files via upload
Co-authored-by: RedPurdy <104675727+RedPurdy@users.noreply.github.com>
* Fix local reactjs
* Add setup guide. Bundled dev main.js
* Add react native tor
* Move Android CHANGELOG.md to /mobile
* Add torified webview in react-native (#247)
* Add android build workflow
* Android Tor Requests
* Fetching internal files (i18n)
* react-native-tor does not implement PUT
* Get Files from Tor
* Revert "Add android build workflow"
This reverts commit 340bcf8d1c.
* Fix Rebase Removals
* External sources
* react-native-tor crashes
* Last Refactor
* Fix/revert setup guide
* Add /mobile as volume to npm-dev container
On the fully dockerized dev environment the npm process cannot save files outside of /frontend directory. Now it can also save the builds to /mobile
* Fix UsafeAlert
* Run prettier
* Run lint:fix
* Main Profile Image fix
* Remove Tor Requests limitation
Co-authored-by: Reckless_Satoshi <reckless.satoshi@protonmail.com>
Co-authored-by: RedPurdy <104675727+RedPurdy@users.noreply.github.com>
Co-authored-by: KoalaSat <yv1vtrul@duck.com>
- Motivation
1) It is widely recognized that one of the main attack vectors for the Bitcoin network is the ability of states to control the fiat on/off-ramps.
2) While there exists peer-to-peer alternatives to centralized exchanges, these are rather technical, slow and more costly.
3) Most users prefer the convenience of a centralized exchange at the cost of a difficult of the risk for their privacy and a difficult initial setup (ID, selfie-video, etc).
- Opportunities
Using the Lightning Network and hodl invoices it is possible to create a more user friendly, faster and cheaper peer-to-peer market. This vision was first enacted by @grunch on the p2plnbot telegam bot project.
- Challenges
1) Ideally the seller hodl invoice and the payment to the buyer invoice would be atomic. Given that this is not technically possible, the proposed concept relies on the need of trust on the service provider.
There are reasons to believe that challenging centralized solutions both in user experience and cost is possible.
This commit adds a rough concept for thefrontend, backend and design.
This project, tentatively named RoboSats (short for Robotic Satoshis) and licensed at launch under AGPL3.0.
