ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-12-06 09:18:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

IA: add more interlinking / 'See Also' to concepts

Browse Source
This commit is contained in:
mDuo13
2019-07-31 17:14:21 -07:00
parent 1c48e838b1
commit 1b16b460b6
11 changed files with 125 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
content/concepts/consensus-network/consensus.md
View File

@@ -176,6 +176,7 @@ Best practices for applications submitting transactions include:
- [consensus_info method][]
- [validator_list_sites method][]
- [validators method][]
- [consensus_info method][]
@@ -202,3 +203,9 @@ Best practices for applications submitting transactions include:
<a href="#from_footnote_9" id="footnote_9"><sup>9</sup></a> – In practice, the XRP Ledger runs more efficiently by starting a new round of consensus concurrently, before validation has completed.
<a href="#from_footnote_10" id="footnote_10"><sup>10</sup></a> – A `rippled` server can respond to API requests even without a complete ledger history. Interruptions in service or network connectivity can lead to missing ledgers, or gaps, in the server’s ledger history. Over time, if configured to, `rippled` fills in gaps in its history. When testing for missing transactions, it is important to verify against a server with continuous complete ledgers from the time the transaction was submitted until its LastLedgerSequence. Use the RPC server_state to determine which complete_ledgers are available to a particular server.
<!--{# common link defs #}-->
{% include '_snippets/rippled-api-links.md' %}
{% include '_snippets/tx-type-links.md' %}
{% include '_snippets/rippled_versions.md' %}