Mirror/robosats
1
0
Fork 0
mirror of https://github.com/RoboSats/robosats.git synced 2024-12-13 02:46:28 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

FIx collection of typos

Browse Source
This commit is contained in:
Reckless_Satoshi 2022-01-22 09:01:57 -08:00
parent fb5cb8fb4a
commit 28abd0380f
No known key found for this signature in database
GPG Key ID: 9C4585B561315571
4 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -39,7 +39,7 @@ Alice wants to buy satoshis privately:
See [CONTRIBUTING.md](CONTRIBUTING.md)
## Original idea
The concept of a simple custody-minimized lightning exchange using hold invoices is heavily inspired by [P2PLNBOT](https://github.com/grunch/p2plnbot) by @grunch
The concept of a simple custody-minimized lightning exchange using hold invoices is heavily inspired in [P2PLNBOT](https://github.com/grunch/p2plnbot) by @grunch
## License

2
api/management/commands/clean_orders.py
View File

@ -22,7 +22,7 @@ class Command(BaseCommand):
Order.Status.DIS, Order.Status.CCA,
Order.Status.PAY, Order.Status.SUC,
Order.Status.FAI, Order.Status.MLD,
Order.Status.TLD]
Order.Status.TLD, Order.Status.WFR]
while True:
time.sleep(5)

4
api/models.py
View File

@ -175,12 +175,12 @@ class Order(models.Model):
8 : 60*int(config('INVOICE_AND_ESCROW_DURATION')), # 'Waiting only for buyer invoice'
9 : 60*60*int(config('FIAT_EXCHANGE_DURATION')), # 'Sending fiat - In chatroom'
10 : 60*60*int(config('FIAT_EXCHANGE_DURATION')), # 'Fiat sent - In chatroom'
11 : 10*24*60*60, # 'In dispute'
11 : 1*24*60*60, # 'In dispute'
12 : 0, # 'Collaboratively cancelled'
13 : 24*60*60, # 'Sending satoshis to buyer'
14 : 24*60*60, # 'Sucessful trade'
15 : 24*60*60, # 'Failed lightning network routing'
16 : 24*60*60, # 'Wait for dispute resolution'
16 : 10*24*60*60, # 'Wait for dispute resolution'
17 : 24*60*60, # 'Maker lost dispute'
18 : 24*60*60, # 'Taker lost dispute'
}

14
frontend/src/components/InfoDialog.js
View File

@ -24,13 +24,13 @@ export default class InfoDialog extends Component {
Both have to post a small bond using lightning to prove they are real
robots. Then, Alice posts the trade collateral also using a lightning
hold invoice. <i>RoboSats</i> locks the invoice until Alice confirms she
received the fiat. Then the satoshis to Bob. Enjoy your satoshis,
received the fiat, then the satoshis are released to Bob. Enjoy your satoshis,
Bob!</p>
<p>At no point, AdequateAlice01 and BafflingBob02 have to trust the
bitcoin to each other. In case they have a conflict, <i>RoboSats</i> staff
will help resolving the dispute. You can find an step-by-step
description of the trade pipeline on our GitHub <a href='https://github.com/reckless-satoshi/robosats'>Readme</a></p>
will help resolving the dispute. You can find a step-by-step
description of the trade pipeline in <a href='https://github.com/Reckless-Satoshi/robosats/blob/main/README.md#how-it-works'>'How it works'</a></p>
</Typography>
<Typography component="h5" variant="h5">What payment methods are accepted?</Typography>
@ -79,10 +79,10 @@ export default class InfoDialog extends Component {
In addition, disputes are solved by the <i>RoboSats</i> staff.
</p>
<p> Trust requirements are minimized, however there is still one way
<i>RoboSats</i> could run away with your satoshis, by not releasing
the satoshis to the buyer. It could be argued that such move is not on
<i>RoboSats</i> interest as it would damage thereputation for a small payout.
<p> Trust requirements are minimal, however there is still one way <i>RoboSats</i>
could run away with your satoshis: by not releasing
the satoshis to the buyer. It could be argued that such move is not on <i>RoboSats</i>
interest as it would damage the reputation for a small payout.
However, you should hesitate and only trade small quantities at a
time. For large amounts use an onchain escrow service such as <i>Bisq</i>
</p>