mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-21 20:25:51 +00:00
update various broken links
This commit is contained in:
mDuo13
@@ -40,7 +40,7 @@ If you are looking to try out some methods on the Ripple Consensus Ledger, you c
|
||||
|
||||
#### Request Formatting ####
|
||||
|
||||
After you open a WebSocket to the `rippled` server, you can send commands as a [JSON](http://www.w3schools.com/json/) object, with the following attributes:
|
||||
After you open a WebSocket to the `rippled` server, you can send commands as a [JSON](https://en.wikipedia.org/wiki/JSON) object, with the following attributes:
|
||||
|
||||
* Put command name in top-level `"command"` field
|
||||
* All the relevant parameters for the command are also in the top level
|
||||
@@ -72,7 +72,7 @@ Always include a `Content-Type` header with the value `application/json`.
|
||||
|
||||
If you plan on making multiple requests, use [Keep-Alives](http://tools.ietf.org/html/rfc7230#section-6.3) so that you do not have to close and re-open the connection in between requests.
|
||||
|
||||
Send request body as a [JSON](http://www.w3schools.com/json/) object with the following attributes:
|
||||
Send request body as a [JSON](https://en.wikipedia.org/wiki/JSON) object with the following attributes:
|
||||
|
||||
* Put the command in the top-level `"method"` field
|
||||
* Include a top-level `"params"` field. The contents of this field should be **a one-item array** containing only a nested JSON object with all the parameters for the command.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Transactions Overview #
|
||||
|
||||
A _Transaction_ is the only way to modify the Ripple Ledger. Transactions are only valid if signed, submitted, and accepted into a validated ledger version following the [consensus process](https://ripple.com/build/ripple-ledger-consensus-process/). Some ledger rules also generate _[pseudo-transactions](#pseudo-transactions)_, which aren't signed or submitted, but still must be accepted by consensus. Transactions that fail are also included in ledgers because they modify balances of XRP to pay for the anti-spam [transaction cost](concept-transaction-cost).
|
||||
A _Transaction_ is the only way to modify the Ripple Ledger. Transactions are only valid if signed, submitted, and accepted into a validated ledger version following the [consensus process](https://ripple.com/build/ripple-ledger-consensus-process/). Some ledger rules also generate _[pseudo-transactions](#pseudo-transactions)_, which aren't signed or submitted, but still must be accepted by consensus. Transactions that fail are also included in ledgers because they modify balances of XRP to pay for the anti-spam [transaction cost](concept-transaction-cost.html).
|
||||
|
||||
* [Authorizing Transactions](#authorizing-transactions)
|
||||
* [Common Fields of All Transactions](#common-fields)
|
||||
|
||||
@@ -134,8 +134,6 @@ If a financial institution suspects that funds may be related to criminal activi
|
||||
|
||||
See also:
|
||||
|
||||
- [SAR guidance for US-based financial institutions](https://www.fincen.gov/news_room/rp/sar_guidance.html)
|
||||
|
||||
- [FATF Recommendation 16: Reporting of suspicious transactions and compliance](http://www.un.org/en/sc/ctc/docs/bestpractices/fatf/40recs-moneylaundering/fatf-rec16.pdf)
|
||||
|
||||
### Travel Rule
|
||||
|
||||
@@ -266,7 +266,7 @@
|
||||
<h3 id="websocket-api">WebSocket API</h3>
|
||||
<p>If you are looking to try out some methods on the Ripple Consensus Ledger, you can skip writing your own WebSocket code and go straight to using the API at the <a href="ripple-api-tool.html">Ripple WebSocket API Tool</a>. Later on, when you want to connect to your own <code>rippled</code> server, you can <a href="https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API/Writing_WebSocket_client_applications">build your own client in the browser</a> or <a href="https://www.npmjs.com/package/ws">in Node.js</a>.</p>
|
||||
<h4 id="request-formatting">Request Formatting</h4>
|
||||
<p>After you open a WebSocket to the <code>rippled</code> server, you can send commands as a <a href="http://www.w3schools.com/json/">JSON</a> object, with the following attributes:</p>
|
||||
<p>After you open a WebSocket to the <code>rippled</code> server, you can send commands as a <a href="https://en.wikipedia.org/wiki/JSON">JSON</a> object, with the following attributes:</p>
|
||||
<ul>
|
||||
<li>Put command name in top-level <code>"command"</code> field</li>
|
||||
<li>All the relevant parameters for the command are also in the top level</li>
|
||||
@@ -303,7 +303,7 @@
|
||||
<p>To make a JSON-RPC request, send an HTTP <strong>POST</strong> request to the root path (<code>/</code>) on the port and IP where the <code>rippled</code> server is listening for JSON-RPC connections. You can use HTTP/1.0 or HTTP/1.1. If you use HTTPS, you should use TLS v1.2. For security reasons, <code>rippled</code> <em>does not support</em> SSL v3 or earlier.</p>
|
||||
<p>Always include a <code>Content-Type</code> header with the value <code>application/json</code>.</p>
|
||||
<p>If you plan on making multiple requests, use <a href="http://tools.ietf.org/html/rfc7230#section-6.3">Keep-Alives</a> so that you do not have to close and re-open the connection in between requests.</p>
|
||||
<p>Send request body as a <a href="http://www.w3schools.com/json/">JSON</a> object with the following attributes:</p>
|
||||
<p>Send request body as a <a href="https://en.wikipedia.org/wiki/JSON">JSON</a> object with the following attributes:</p>
|
||||
<ul>
|
||||
<li>Put the command in the top-level <code>"method"</code> field</li>
|
||||
<li>Include a top-level <code>"params"</code> field. The contents of this field should be <strong>a one-item array</strong> containing only a nested JSON object with all the parameters for the command.</li>
|
||||
|
||||
@@ -202,7 +202,7 @@
|
||||
<main class="main" role="main">
|
||||
<div class='content'>
|
||||
<h1 id="transactions-overview">Transactions Overview</h1>
|
||||
<p>A <em>Transaction</em> is the only way to modify the Ripple Ledger. Transactions are only valid if signed, submitted, and accepted into a validated ledger version following the <a href="https://ripple.com/build/ripple-ledger-consensus-process/">consensus process</a>. Some ledger rules also generate <em><a href="#pseudo-transactions">pseudo-transactions</a></em>, which aren't signed or submitted, but still must be accepted by consensus. Transactions that fail are also included in ledgers because they modify balances of XRP to pay for the anti-spam <a href="concept-transaction-cost">transaction cost</a>.</p>
|
||||
<p>A <em>Transaction</em> is the only way to modify the Ripple Ledger. Transactions are only valid if signed, submitted, and accepted into a validated ledger version following the <a href="https://ripple.com/build/ripple-ledger-consensus-process/">consensus process</a>. Some ledger rules also generate <em><a href="#pseudo-transactions">pseudo-transactions</a></em>, which aren't signed or submitted, but still must be accepted by consensus. Transactions that fail are also included in ledgers because they modify balances of XRP to pay for the anti-spam <a href="concept-transaction-cost.html">transaction cost</a>.</p>
|
||||
<ul>
|
||||
<li><a href="#authorizing-transactions">Authorizing Transactions</a></li>
|
||||
<li><a href="#common-fields">Common Fields of All Transactions</a></li>
|
||||
|
||||
@@ -336,8 +336,9 @@ known_broken_links:
|
||||
# Strangely, Python doesn't like the cert here. Firefox is OK with it.
|
||||
- https://validators.ripple.com
|
||||
|
||||
# rippled 0.33.0 is not released yet:
|
||||
- https://github.com/ripple/rippled/releases/tag/0.33.0
|
||||
# These PDFs download OK in a browser
|
||||
- http://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX%3A32015R0847
|
||||
- http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2006:345:0001:0009:EN:PDF
|
||||
|
||||
# Style Checker Config ------------------------------------------------------ #
|
||||
|
||||
|
||||
@@ -299,12 +299,7 @@
|
||||
<p>If a financial institution suspects that funds may be related to criminal activity, the institution must file a Suspicious Activity Report (SAR) with the appropriate regulatory authority. Failure to report suspicious activity may result in in penalties for the institution.</p>
|
||||
<p>See also:</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://www.fincen.gov/news_room/rp/sar_guidance.html">SAR guidance for US-based financial institutions</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="http://www.un.org/en/sc/ctc/docs/bestpractices/fatf/40recs-moneylaundering/fatf-rec16.pdf">FATF Recommendation 16: Reporting of suspicious transactions and compliance</a></p>
|
||||
</li>
|
||||
<li><a href="http://www.un.org/en/sc/ctc/docs/bestpractices/fatf/40recs-moneylaundering/fatf-rec16.pdf">FATF Recommendation 16: Reporting of suspicious transactions and compliance</a></li>
|
||||
</ul>
|
||||
<h3 id="travel-rule">Travel Rule</h3>
|
||||
<p>The Travel Rule is a Bank Secrecy Act (BSA) rule requiring funds-transmitting financial institutions to forward certain information to the next financial institution if the funds transmittal equals or exceeds the USD equivalent of $3,000. The following information must be included in the transmittal order:</p>
|
||||
@@ -315,7 +310,7 @@
|
||||
<li>The identity of the transmittor's financial institution,</li>
|
||||
<li>The amount of the transmittal order,</li>
|
||||
<li>The execution date of the transmittal order, and</li>
|
||||
<li>The identity of the recipient's financial institution;</li>
|
||||
<li>The identity of the recipient's financial institution.</li>
|
||||
</ul>
|
||||
<p>See also:</p>
|
||||
<ul>
|
||||
|
||||
Reference in New Issue
Block a user