mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-20 11:45:50 +00:00
IA: fix new See Also links
This commit is contained in:
@@ -16,7 +16,7 @@ When an issuer enables, disables, or changes the `TickSize`, Offers that were pl
|
|||||||
- **References:**
|
- **References:**
|
||||||
- [AccountSet transaction][]
|
- [AccountSet transaction][]
|
||||||
- [book_offers method][]
|
- [book_offers method][]
|
||||||
- [CreateOffer transaction][]
|
- [OfferCreate transaction][]
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@@ -51,6 +51,7 @@ As with operational addresses, a standby address must have an accounting relatio
|
|||||||
|
|
||||||
If a standby address is compromised, the consequences are like an operational address being compromised. A malicious actor can steal any balances possessed by the standby address, and the financial institution can change to a new standby address with no action from customers and partners.
|
If a standby address is compromised, the consequences are like an operational address being compromised. A malicious actor can steal any balances possessed by the standby address, and the financial institution can change to a new standby address with no action from customers and partners.
|
||||||
|
|
||||||
|
|
||||||
## See Also
|
## See Also
|
||||||
|
|
||||||
- **Concepts:**
|
- **Concepts:**
|
||||||
@@ -64,3 +65,9 @@ If a standby address is compromised, the consequences are like an operational ad
|
|||||||
- [account_info method][]
|
- [account_info method][]
|
||||||
- [SetRegularKey transaction][]
|
- [SetRegularKey transaction][]
|
||||||
- [AccountRoot object](accountroot.html)
|
- [AccountRoot object](accountroot.html)
|
||||||
|
|
||||||
|
|
||||||
|
<!--{# common link defs #}-->
|
||||||
|
{% include '_snippets/rippled-api-links.md' %}
|
||||||
|
{% include '_snippets/tx-type-links.md' %}
|
||||||
|
{% include '_snippets/rippled_versions.md' %}
|
||||||
|
|||||||
@@ -77,7 +77,7 @@ From a relatively high level, the XRP Ledger's transaction processing engine app
|
|||||||
- [Payment System Basics](payment-system-basics.html)
|
- [Payment System Basics](payment-system-basics.html)
|
||||||
- **Tutorials:**
|
- **Tutorials:**
|
||||||
- [Send XRP (Interactive Tutorial)](send-xrp.html)
|
- [Send XRP (Interactive Tutorial)](send-xrp.html)
|
||||||
- [Monitor Incoming Payments with WebSocket](Monitor Incoming Payments with WebSocket)
|
- [Monitor Incoming Payments with WebSocket](monitor-incoming-payments-with-websocket.html)
|
||||||
- **References:**
|
- **References:**
|
||||||
- [Payment transaction][]
|
- [Payment transaction][]
|
||||||
- [Transaction Results](transaction-results.html)
|
- [Transaction Results](transaction-results.html)
|
||||||
|
|||||||
@@ -71,9 +71,9 @@ When you run `rippled` in stand-alone mode, you have to tell it what ledger vers
|
|||||||
- [Configure `rippled`](configure-rippled.html)
|
- [Configure `rippled`](configure-rippled.html)
|
||||||
- [Run `rippled` as a Validator](run-rippled-as-a-validator.html)
|
- [Run `rippled` as a Validator](run-rippled-as-a-validator.html)
|
||||||
- [Use rippled in Stand-Alone Mode](use-stand-alone-mode.html):
|
- [Use rippled in Stand-Alone Mode](use-stand-alone-mode.html):
|
||||||
- [Start a New Genesis Ledger in Stand-Alone Mode](start-a-new-genesis-ledger-in-standalone-mode.html)
|
- [Start a New Genesis Ledger in Stand-Alone Mode](start-a-new-genesis-ledger-in-stand-alone-mode.html)
|
||||||
- [Load a Saved Ledger in Stand-Alone Mode](load-a-saved-ledger-in-standalone-mode.html)
|
- [Load a Saved Ledger in Stand-Alone Mode](load-a-saved-ledger-in-stand-alone-mode.html)
|
||||||
- [Advance the Ledger in Stand-Alone Mode](advance-the-ledger-in-standalone-mode.html)
|
- [Advance the Ledger in Stand-Alone Mode](advance-the-ledger-in-stand-alone-mode.html)
|
||||||
|
|
||||||
|
|
||||||
<!--{# common link defs #}-->
|
<!--{# common link defs #}-->
|
||||||
|
|||||||
Reference in New Issue
Block a user