You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After almost 1.5 years, Lokun has grown and so has lokun-record. It is time to split it up into two projects, lokun-record for the RESTLike API with users and nodes, and lokun-billing for everything billing related.
The text was updated successfully, but these errors were encountered:
BTCAddr object. The new lokun-billing would keep a record of username and BTC addr pairs
Database
Table btcaddrs if BTCAddr is moved
Table paymentbot
Table deposit
Files
Bankmail.py
dalpay.py, encryption.py and hashing.py need to be copied over, but maintained in lokun-record (save for some git magic)
exchanges.py and update_btcprices.py if lokun-billing should keep track fo BTC prices (not sure)
paymentbot.py but is deprecated
mailchecker.py
Changes in lokun-record
restapi
Add POST /user/<username>/deposit or POST /user/<username/credit_isk that requires key auth from a key starting with payment- or billing-
Add GET /user/<username>/user1 to create the user1 string in our DalPay protocol. Requires user auth. Maybe the entire DalPay object will be created in record. This functionality is now in lokun-site, but I want this code to be part of lokun-record and that way the site can go back to being a dumb site again
After almost 1.5 years, Lokun has grown and so has
lokun-record
. It is time to split it up into two projects,lokun-record
for the RESTLike API with users and nodes, andlokun-billing
for everything billing related.The text was updated successfully, but these errors were encountered: