okada-blue ed062416db Edit Multiple docs (#712)
* Update 01-development.md

Update Communication Channels channels to reflect removal of Twitter and Telegram, and emphasize SimpleX, Nostr, and Matrix chats

* Update 02-languages.md

Update Telegram verbiage to reference SimpleX instead.

* Update 04-guides.md

Update Telegram verbiage to reference SimpleX instead.

* Update 05-art.md

Update Telegram verbiage to reference SimpleX instead.

* Update 06-outreach.md

Update Twitter verbiage and reference Nostr instead

* Update 00-quicks-start-guide.md

Update verbiage slightly. Add more info and links.

* Update 01-lightning.md

Add rough draft to provide overview of Lightning Network and its relation to RoboSats

* Update 02-tor.md

Provide rough draft of introduction to TOR.

* Update 03-access.md

Add access method via Android app APK. Adjust slight typos and some wording for clarity.

* Update 01-trade-pipeline.md

Add TOC, swap steps and pictures placement, adjust small typos and wording.

Picture was swapped with the steps because I think the picture can be slightly overwhelming versus a simple list of steps. The pictures are great but they are a lot to throw at someone right when they open the very first doc under "Understand" to learn about RoboSats.

* Update 02-robots.md

Clean up hyperlinks, adjust grammar slightly.

* Update 03-premium.md

Update verbiage, adjust grammar slightly.

* Update 03-premium.md

Add paragraphs on advice for choosing a premium

* Update 04-bonds.md

Various changes to verbiage and adding/updating information. Grammar fixes, remove reference to Telegram.

* Update 05-trade-escrow.md

Clean up hyperlinks, adjust some wording

* Update 06-disputes.md

Rough draft of disputes section. Committed changes are a placeholder for a longer and more detailed version of the dispute process.

* Update 07-wallets.md

Fix typos, grammar edits, add new section at bottom

* Update 08-limits.md

Rough draft of new content in the limits docs

* Update 09-swaps.md

Adjust "on-chain" to "on chain" and "sats" to "Sats" for consistency across other docs. Slight grammar fixes.

* Update 10-telegram.md

Small grammar fixes, clean up formatting and add table of contents

* Update 12-prices.md

Add verbiage note about explicit pricing method, clean up hyperlinks

* Update 13-fees.md

Clean up hyperlinks, small spelling fixes

* Update 14-on-chain-payouts.md

Add table of contents, small grammar fixes, adjust formatting

* Update 07-wallets.md

Change "on chain" to "on-chain"

* Update 09-swaps.md

Change "on chain" to "on-chain"

* Update 02-tor.md

Add note when using TOR and experiencing connection issues
2023-07-24 17:50:17 +00:00

7.4 KiB

layout title permalink toc toc_sticky sidebar src
single Maker and Taker Bonds /docs/bonds/ true true
title nav
<img id="side-icon-verybig" src="/assets/vector/ticket-simple.svg"/>Bonds docs
_pages/docs/03-understand/04-bonds.md

The fidelity bond is a small deposit that the user "locks" which will become unlocked after the trade is completed; however, users can lose their bond if they fail to follow the obligations of the contract.

The RoboSats trade pipeline utilizes fidelity bonds to incentivize both the order maker and taker to play by the rules and not cheat their fellow robot. More specifically, the bonds are hold invoices using the Lightning Network; it's the tech that makes RoboSats possible! Refer to Understand > Trade Escrow > What is a Hold Invoice? for understanding how hold invoices work in practice.

By default, the bond is {{site.robosats.default_bond_size}}% of the total trade amount. Alternatively, order makers can customize this amount to be anywhere from {{site.robosats.min_bond_size}}% to {{site.robosats.max_bond_size}}%. Larger bonds mean more "skin in the game" that is required to trade.

The bond does not leave your Lightning wallet, but please know some wallets play nicer with RoboSats than others due to the nature of the Lightning hold invoice mechanic. Refer to Understand > Wallets for additional information.

Note: The option allowing "Bondless Takers" is not available.

How to Lock a Bond

First, refer to Understand > Wallets for compatible Lightning wallets that will help make using RoboSats a smoother experience. Depending on the wallet, the invoice might show as a payment that is in transit, frozen, or even appearing to fail. Check the wallet compatability list!

Bonds are not linked to orders. You can use any Sats to fund the bond invoice. There is no link between the bond and your order, nor any link between the bond and your payout invoice.

Read the relevant guide depending on if you are making or taking the order:

  • Maker: Select "Make Order" and modify the order conditions to your liking. The order can be customized to require a fidelity bond other than the default {{site.robosats.default_bond_size}}% of the total trade amount, ranging anywhere from {{site.robosats.min_bond_size}}% to {{site.robosats.max_bond_size}}%. Once complete, confirm with "Create Order" and then use the QR code presented to you with your Lightning wallet to lock the indicated amount of Sats for your fidelity bond. You can always cancel the untaken order while it is live and the bond will automatically unlock; however, if you try to cancel the order after it gets taken, you will forfeit your bond. Note: Be prepared with your wallet beforehand because the order box expires in ten minutes.
  • Taker: Browse the order book and find an order to your liking. Simply select the "Take Order" option and then use the QR code presented to you with your Lightning wallet to lock the indicated amount of sats for your fidelity bond. Note: Be prepared with your wallet beforehand because the order box expires in four minutes. If you do not proceed, the taken order is made public again.

After the trade is completed and both robots held up to their end of the deal, the maker and taker bonds are unlocked. Technically, the locked bond never left your wallet; but take heed, if you fail to follow the contract obligations by trying to cheat or cancelling unilaterally, you will forfeit your fidelity bond.

Your wallet may take a while for funds to show as unlocked on your account balance. Some wallets have difficulty with recognizing the Lightning hold invoice as a temporary hold on your funds.

If the issue persists, please reach out to the RoboSats SimpleX group; but beware of scammers that may directly contact you and impersonate RoboSats staff! RoboSats staff will never directly contact you first. See Contribute > Code > Communication Channels for the public SimpleX support group.

Losing Your Bond

There are basically four conditions that causes a user to lose their bond:

  • Cheat or deceive your peer (and lose the order dispute)
  • Unilaterally cancel the order without your peer's collaboration during the peer-to-peer chat stage
  • Fail to submit the escrow invoice (seller) or payment invoice (buyer) within the given time limit
  • Fail to confirm the fiat was received as the bitcoin seller

Note that you do not lose your bond as an order maker if you cancel your order before it has been taken by a peer. The conditions above are expanded upon in additional detail below.

If the time limit for submitting the invoice (buyer) or locking the escrow (seller) runs out, then the order will expire and the robot who did not hold up to their end of the deal will lose the bond. Half of the lost bond goes to the honest robot as compensation for wasted time.

Therefore, don't forget about your order because once a robot takes it and locks their fidelity bond, you could lose your bond since the timer might expire. Take care to remember your order and back up your robot's unique token! Keep in mind this token is only known by you and, without it, your unique robot avatar is not recoverable.

If you received fiat but neglect to click "Confirm Fiat Received" on your end, then you risk losing your bond since a dispute is automatically opened and the RoboSats staff will find you failed to follow the rules of the contract.

Due to the time limits involved in the order process, it is recommended to use instant fiat payment methods which help reduce the chances of losing your bond. Refer to Best Practices > Payment Methods for additional information.

Opening a dispute just to cancel an order is not recommended because one of the two traders will lose their fidelity bond, barring exceptional cases that are up to the discretion of the RoboSats staff.

For orders that allow takers to choose from a range, peers only risk losing an amount of Sats proportional to the amount of Sats taken in the order.

As a sidenote, if RoboSats suddenly vanished or was shutdown, then bonds are automatically unlocked since they technically never left your wallet.

Don't Have Any Bitcoin for Bonds?

Because the bonds require a Lightning hold invoice, what are you to do if you have no bitcoin to begin with? Even though the bond is typically just {{site.robosats.default_bond_size}}% of your total trade amount, this presents a real barrier to using RoboSats for the first time if your Sat stack is non-existent.

Currently, bondless takers are not available but are in consideration for a future update. Bondless takers present a greater risk to the order maker since the taker has no skin in the game. It would be reasonable to expect higher premiums on orders that allow bondless takers.

There are a myriad of available apps and services where very small amounts of bitcoin can be earned. RoboSats does not endorse a specific app, but users have reported success with apps like Stacker News, Fountain, Bitcoin Magazine App, THNDR, etc.

Since the bond is just a temporary hold on funds, you could have a friend cover the fidelity bond by paying the QR code for you. The bond is instantly unlocked following a successful trade!

{% include improve %}