deploy: daff0fb

pr-preview/dex_trade_uc/algorithmic-trading.html

@@ -260,6 +260,7 @@ <h4>In this document</h4>
         <li class="nav-item level-2"><a class="nav-link" href="#trading-strategies">Trading Strategies</a></li>
         <li class="nav-item level-2"><a class="nav-link" href="#background-reading">Background Reading</a></li>
         <li class="nav-item level-2"><a class="nav-link" href="#testing-and-common-mistakes">Testing and Common Mistakes</a></li>
+        <li class="nav-item level-2"><a class="nav-link" href="#taxes-and-licensing">Taxes and Licensing</a></li>
         <li class="nav-item level-2"><a class="nav-link" href="#technical-details">Technical Details</a></li>
         <li class="nav-item level-3"><a class="nav-link" href="#placing-trades">Placing Trades</a></li>
         <li class="nav-item level-3"><a class="nav-link" href="#reading-trade-data">Reading Trade Data</a></li>
@@ -335,6 +336,8 @@ <h2 id="testing-and-common-mistakes">Testing and Common Mistakes<a aria-hidden="
 <li>Not accounting for rare events. Even setting aside unprecented ("black swan") events, your calculations can be very skewed by individual outliers which don't occur regularly. As one example (which is a true story), a trader reported that, when calculating the potential profits of a given strategy in a specific time range, over 80% of the profits came from a single "fat-fingered" transaction where another user had accidentally added an extra zero to their price. The same strategy was far less profitable when calculated against time ranges that didn't include the outlier transaction.</li>
 <li>Not reading transaction flags. The flags of an XRP Ledger transaction can have significant impacts on the way that transaction is processed and when the protocol marks it as "successful". For example, the flags of "Offer" transactions can make it a "fill or kill" order that only trades if the full amount can be obtained immediately; the flags of "Payment" transactions can make them <a href="partial-payments.html">partial payments</a> that succeed even if they can't deliver the full amount to the intended destination. You need to do bitwise math to parse the <code>Flags</code> field of a transaction, but your expectations can be totally wrong if you skip doing so.</li>
 </ul>
+<h2 id="taxes-and-licensing">Taxes and Licensing<a aria-hidden="true" class="hover_anchor" href="#taxes-and-licensing"><i class="fa fa-link"></i></a></h2>
+<p>The legal requirements for trading on a blockchain vary by jurisdiction. In many cases, there are no licensing or other legal barriers to getting started, but you may be required to report your profits for tax purposes, especially if your gains or losses are over some thresholds. In the United States, you typically report profits (or losses) from trading as capital gains, which means you need to calculate the cost basis for the assets you buy at the time you acquire them. There are various tools out there that may be able to help track your trading activity or even generate the appropriate tax forms, depending on your individual situation. Depending on which assets you are trading and your trading strategies, the details may vary. Be sure to do your research or consult with a tax professional before you get started with algorithmic trading.</p>
 <h2 id="technical-details">Technical Details<a aria-hidden="true" class="hover_anchor" href="#technical-details"><i class="fa fa-link"></i></a></h2>
 <h3 id="placing-trades">Placing Trades<a aria-hidden="true" class="hover_anchor" href="#placing-trades"><i class="fa fa-link"></i></a></h3>
 <p>Buying and selling <em>fungible</em> tokens and XRP within the XRP Ledger's decentralized exchange typically involves sending <a href="offercreate.html">OfferCreate transactions</a>. For a detailed walkthrough of the code and technical steps to place a trade this way, see <a href="trade-in-the-decentralized-exchange.html">Trade in the Decentralized Exchange</a>. It is also possible to exchange currencies using the <a href="payment.html">Payment transaction type</a>. You could send a <a href="cross-currency-payments.html">cross-currency payment</a> to another user or even send it back to yourself, using a long <a href="paths.html">path</a> to link arbitrage opportunities together into a single operation.</p>

pr-preview/dex_trade_uc/ja/algorithmic-trading.html

@@ -264,6 +264,7 @@ <h4>目次</h4>
         <li class="nav-item level-2"><a class="nav-link" href="#trading-strategies">Trading Strategies</a></li>
         <li class="nav-item level-2"><a class="nav-link" href="#background-reading">Background Reading</a></li>
         <li class="nav-item level-2"><a class="nav-link" href="#testing-and-common-mistakes">Testing and Common Mistakes</a></li>
+        <li class="nav-item level-2"><a class="nav-link" href="#taxes-and-licensing">Taxes and Licensing</a></li>
         <li class="nav-item level-2"><a class="nav-link" href="#technical-details">Technical Details</a></li>
         <li class="nav-item level-3"><a class="nav-link" href="#placing-trades">Placing Trades</a></li>
         <li class="nav-item level-3"><a class="nav-link" href="#reading-trade-data">Reading Trade Data</a></li>
@@ -342,6 +343,8 @@ <h2 id="testing-and-common-mistakes">Testing and Common Mistakes<a aria-hidden="
 <li>Not accounting for rare events. Even setting aside unprecented ("black swan") events, your calculations can be very skewed by individual outliers which don't occur regularly. As one example (which is a true story), a trader reported that, when calculating the potential profits of a given strategy in a specific time range, over 80% of the profits came from a single "fat-fingered" transaction where another user had accidentally added an extra zero to their price. The same strategy was far less profitable when calculated against time ranges that didn't include the outlier transaction.</li>
 <li>Not reading transaction flags. The flags of an XRP Ledger transaction can have significant impacts on the way that transaction is processed and when the protocol marks it as "successful". For example, the flags of "Offer" transactions can make it a "fill or kill" order that only trades if the full amount can be obtained immediately; the flags of "Payment" transactions can make them <a href="partial-payments.html">partial payments</a> that succeed even if they can't deliver the full amount to the intended destination. You need to do bitwise math to parse the <code>Flags</code> field of a transaction, but your expectations can be totally wrong if you skip doing so.</li>
 </ul>
+<h2 id="taxes-and-licensing">Taxes and Licensing<a aria-hidden="true" class="hover_anchor" href="#taxes-and-licensing"><i class="fa fa-link"></i></a></h2>
+<p>The legal requirements for trading on a blockchain vary by jurisdiction. In many cases, there are no licensing or other legal barriers to getting started, but you may be required to report your profits for tax purposes, especially if your gains or losses are over some thresholds. In the United States, you typically report profits (or losses) from trading as capital gains, which means you need to calculate the cost basis for the assets you buy at the time you acquire them. There are various tools out there that may be able to help track your trading activity or even generate the appropriate tax forms, depending on your individual situation. Depending on which assets you are trading and your trading strategies, the details may vary. Be sure to do your research or consult with a tax professional before you get started with algorithmic trading.</p>
 <h2 id="technical-details">Technical Details<a aria-hidden="true" class="hover_anchor" href="#technical-details"><i class="fa fa-link"></i></a></h2>
 <h3 id="placing-trades">Placing Trades<a aria-hidden="true" class="hover_anchor" href="#placing-trades"><i class="fa fa-link"></i></a></h3>
 <p>Buying and selling <em>fungible</em> tokens and XRP within the XRP Ledger's decentralized exchange typically involves sending <a href="offercreate.html">OfferCreate transactions</a>. For a detailed walkthrough of the code and technical steps to place a trade this way, see <a href="trade-in-the-decentralized-exchange.html">Trade in the Decentralized Exchange</a>. It is also possible to exchange currencies using the <a href="payment.html">Payment transaction type</a>. You could send a <a href="cross-currency-payments.html">cross-currency payment</a> to another user or even send it back to yourself, using a long <a href="paths.html">path</a> to link arbitrage opportunities together into a single operation.</p>

pr-preview/dex_trade_uc/style_report.txt

@@ -3,13 +3,13 @@ Spell Checker
 -------------
 Found 72 possible spelling errors:
 <Page 'Privacy Policy' (privacy-policy.html)> Unknown Words:
-  gifs: gibs, gins, ifs
+  gifs: gips, gifu, gifts
   ringtee: 
   kuressaare: 
   lõõtsa: 
 
 <Page 'What is the XRP Ledger?' (what-is-xrpl.html)> Unknown Words:
-  livenet: livener, livened
+  livenet: livened, livener
 
 <Page 'What is XRP?' (what-is-xrp.html)> Unknown Words:
   opencoin: 
@@ -27,11 +27,11 @@ Found 72 possible spelling errors:
   requiremen: requirement
 
 <Page 'Restricting Deposits' (restricting-deposits-uc.html)> Unknown Words:
-  deposite: deposit, deposita, depositee
+  deposite: depositee, deposito, deposits
   unathorized: unauthorized
 
 <Page 'Stablecoin Issuer' (stablecoin-issuer.html)> Unknown Words:
-  xapps: lapps, capps, apps
+  xapps: lapps, apps, capps
 
 <Page 'NFT Marketplace Overview' (nft-mkt-overview.html)> Unknown Words:
   arweave: 
@@ -41,12 +41,12 @@ Found 72 possible spelling errors:
   tokentaxon: 
 
 <Page 'Algorithmic Trading' (algorithmic-trading.html)> Unknown Words:
-  arbitraging: arbitrating
   investopedia: 
+  arbitraging: arbitrating
   frontrunning: 
   unprecented: unprevented, unpresented
-  clob: cob, blob, clo
-  30d: 3d, 3rd, 3-d
+  clob: clou, clomb, chob
+  30d: 3rd, 3d, 3-d
 
 <Page 'Parallel Networks' (parallel-networks.html)> Unknown Words:
   0b0: 
@@ -55,28 +55,28 @@ Found 72 possible spelling errors:
   11d: 
 
 <Page 'Known Amendments' (known-amendments.html)> Unknown Words:
-  immediateofferkilled: 
+  fixuniversalnumber: 
   xrpfees: 
-  disallowincoming: 
+  immediateofferkilled: 
   fixnonfungibletokensv1_2: 
   depositpreauthamendment: 
-  fixuniversalnumber: 
+  disallowincoming: 
   nftokenoffers: nftokenoffer
   asfdisallowincomingpaychan: 
-  asfdisallowincomingnftoffer: 
   asfdisallowincomingcheck: 
+  asfdisallowincomingnftoffer: 
   asfdisallowincomingtrustline: 
-  30d: 3d, 3rd, 3-d
+  30d: 3rd, 3d, 3-d
 
 <Page 'Contribute Code to the XRP Ledger' (contribute-code-flow.html)> Unknown Words:
-  xlsd: lsd, xls
+  xlsd: xls, lsd
 
 <Page 'Ledger Structure' (ledger-structure.html)> Unknown Words:
   hexidecimal: hexadecimal
   slcf_noconsensustime: 
 
 <Page 'Finality of Results' (finality-of-results.html)> Unknown Words:
-  ooffers: doffers, offers, coffers
+  ooffers: offers, doffers, coffers
 
 <Page 'NFT Reserve Requirements' (nft-reserve-requirements.html)> Unknown Words:
   24n: 
@@ -97,13 +97,13 @@ Found 72 possible spelling errors:
 
 <Page 'NFT APIs' (nft-apis.html)> Unknown Words:
   nft_history: 
-  slas: ssas, stas, slag
+  slas: slae, sas, slask
 
 <Page 'Public Servers' (public-servers.html)> Unknown Words:
-  30d: 3d, 3rd, 3-d
+  30d: 3rd, 3d, 3-d
 
 <Page 'Create Time-based Escrows Using JavaScript' (create-time-based-escrows-using-javascript.html)> Unknown Words:
-  ripple8: rippler, ripple, ripplet
+  ripple8: ripplet, ripplex, rippled
   numofseconds: 
   offersequence: 
 
@@ -151,7 +151,7 @@ Found 72 possible spelling errors:
 -----------------------------
 Discouraged Words and Phrases
 -----------------------------
-Found 104 discouraged words/phrases:
+Found 105 discouraged words/phrases:
 Page: <Page 'FAQ' (faq.html)>
    Discouraged phrase: market maker (1 instances); suggest 'liquidity provider' instead.
 Page: <Page 'Privacy Policy' (privacy-policy.html)>
@@ -204,6 +204,7 @@ Page: <Page 'Digital Artist' (digital-artist.html)>
 Page: <Page 'Algorithmic Trading' (algorithmic-trading.html)>
    Discouraged word: therefore (1 instances); suggest 'so' instead.
    Discouraged word: will (2 instances); suggest '(avoid future tense)' instead.
+   Discouraged word: consult (1 instances); suggest 'see' instead.
 Page: <Page 'Amendments' (amendments.html)>
    Discouraged word: subsequent (1 instances); suggest 'later, next' instead.
 Page: <Page 'Known Amendments' (known-amendments.html)>
@@ -304,7 +305,7 @@ Page Length Metrics
 Average Page Length Metrics:
   Sentences: 54
   Words: 725
-  Characters: 4,503
+  Characters: 4,506
 
 Longest pages by character count:
 <Page 'Known Amendments' (known-amendments.html)> Length Metrics: