17 Commits

Author SHA1 Message Date
0d4922a6e2 Add new payment method icons 2022-05-02 08:34:42 -07:00
e680f32f79 Remove built main.js from versioning (#102)
We should never version built files. This leads to conflicts when merging branches.

This commit deletes the main.js file and changes the .gitignore to prevent it from being added again
2022-04-21 13:03:42 +00:00
9f57667f36 Improve contribute icons readme. Add trademark usage disclaimer. Add 5 new payment methods 2022-04-16 08:31:42 -07:00
baf76025c2 Add autocomplete, icons, custom selector 2022-03-29 16:16:59 -07:00
ca79ea9914 Init accounting panel, add import/export 2022-03-20 16:32:25 -07:00
2cf10ce86b Switch to postgres dev environment 2022-02-19 17:13:51 -08:00
f830c4df15 Init dockerization of dev environment with docker-compose 2022-02-07 03:21:59 -08:00
14ae3d0c2e Prepare for collectstatic 2022-02-06 16:15:45 -08:00
7ba2fcc921 Add celery background and scheduled tasks. Add user cleansing task 2022-01-16 04:31:25 -08:00
8bc8f539d0 Work on LN bonds. Maker bond works. Yet, this is not the best way probably. 2022-01-11 12:49:53 -08:00
9c2f50dacf Init work on Lightning functionality 2022-01-10 15:27:48 -08:00
e493f22842 add lnd grpc 2022-01-10 10:47:16 -08:00
354e7fc5c7 Create user generation API
Endpoint request contains a token. Server checks whether it has enough entropy to be secure (at least 128 bits and >0.7 shannon heterogeneity). Server hashes the token (once as of now) and derives nickname and robohash avatar (goes into static/assets/avatars). Nickname is limited to only adjectives, nouns and 3 digits, restricted to 18 characters long max. The corpus of nicknames is 20 billion big (maybe not enough? nick collision chance can happen, but server will just reply with 400 unless the token matches perfectly too)
2022-01-02 09:15:09 -08:00
f0ac03e519 Add nick generator and robohash avatar generator 2022-01-02 07:19:49 -08:00
fe1ee48a9d Add main.js to .gitignore 2022-01-01 16:45:26 -08:00
76a45bc8d5 Create API endpoint for POST make order
Added the Order model with a rough approxiation to the fields needed. The field status can be read lineally as the progression trough the app pipeline. The view serves POSTs requests to enter new orders into the db.
2022-01-01 14:40:08 -08:00
2e3a32705b Add concept for BTC <> Fiat p2p swap using Lightning.
- 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.
2022-01-01 07:28:49 -08:00