ed062416db
* 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
1.7 KiB
| layout | title | permalink | toc | toc_sticky | sidebar | src | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| single | Exchange Limits | /docs/limits/ | true | true |
|
_pages/docs/03-understand/08-limits.md |
RoboSats is built on the Lightning Network, a micropayment network. Therefore, amounts sent and received over the Lightning Network must be small enough to successfully find a suitable route.
The maximum single trade size is {{site.robosats.max_trade_limit}} Sats and the minimum single trade size is {{site.robosats.min_trade_limit}} Sats.
However, there are no limits to the quantity of trades you can make/take on RoboSats (although it is strongly recommended to limit one order per robot identity). Generate and manage multiple robot identities using the Robot Garage feature. Just be certain to securely back up your secret robot tokens!
Why Have Limits?
The reason for having a limit on the amount of Sats you can send/receive with RoboSats is due minimizing Lightning routing failure. This makes the end-user experience with RoboSats much smoother to ensure funds get reliably paid out.
The more Sats you try to push through LN, the harder it is to find a path. If there were no limits on an order, then a user might try to receive sats that will never find a suitable route.
To reduce headaches and streamline the experience, a limit is in place that is sensible to the realities of the average channel capacity across the Lightning Network. For example, trying to receive 10M Sats might never payout when the network's average channel capacity is well below 10M Sats.
{% include improve %}