ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-04 11:55:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Migrate old callout syntax

Browse Source
This commit is contained in:
mDuo13
2024-10-09 15:26:34 -07:00
parent 4d3d3edece
commit f42bb6c813
364 changed files with 607 additions and 603 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
blog/2016/flowv2-voting.md
View File

@@ -18,7 +18,7 @@ The FlowV2 Engine also makes it easier to improve and expand the payment engine
If you operate a `rippled` server, you should upgrade to version 0.32.1 by Wednesday, 2016-08-24 for the best performance.
**Note:** A previous version of this post incorrectly stated that backend software must be updated to construct transactions for the new payment processing engine. The process of creating and submitting transactions for the FlowV2 payment engine is the same as for the previous payment engine.
{% admonition type="info" name="Note" %}A previous version of this post incorrectly stated that backend software must be updated to construct transactions for the new payment processing engine. The process of creating and submitting transactions for the FlowV2 payment engine is the same as for the previous payment engine.{% /admonition %}
## Impact of Not Upgrading

2
blog/2019/labeling-the-internet-of-value.md
View File

@@ -95,7 +95,7 @@ unl = "https://vl.ripple.com"
Finally, the list of accounts. I added an `[[ACCOUNTS]]` entry for each of the XRP Ledger addresses whose keys I have saved. As a result of doing various tests and experiments, I have a few more accounts than a normal person needs, and I honestly don't even remember what some of these were for. I added a description `desc` field to the accounts where I remembered their purpose, most importantly for the "primary" address where I want to receive XRP if, for example, people want to send me tips. I also tagged that one explicitly as being on the main network just to be sure. (Some of my addresses are in use on both the test net and the production network; that's not a good practice to follow, but I'm stuck with it.)
**Tip:** I love sending XRP tips to people who contribute to the XRP Ledger Dev Portal. If you open a PR to the dev portal, make your XRP Ledger address known and I might just send some XRP your way! You could even just provide your domain if you serve an `xrp-ledger.toml` file with your preferred address there.
{% admonition type="success" name="Tip" %}I love sending XRP tips to people who contribute to the XRP Ledger Dev Portal. If you open a PR to the dev portal, make your XRP Ledger address known and I might just send some XRP your way! You could even just provide your domain if you serve an `xrp-ledger.toml` file with your preferred address there.{% /admonition %}
My accounts list:

2
blog/2019/testnet-reset.md
View File

@@ -53,4 +53,4 @@ If you run a `rippled` server [connected to the XRP Testnet](https://xrpl.org/co
# systemctl restart rippled.service
```
**Warning:** Be sure that you have not put any files you want to keep in the folder before you delete it. It is generally safe to delete all of a `rippled` server's database files, but you should only do this if the configured database folder is not used for anything other than `rippled`'s databases.
{% admonition type="danger" name="Warning" %}Be sure that you have not put any files you want to keep in the folder before you delete it. It is generally safe to delete all of a `rippled` server's database files, but you should only do this if the configured database folder is not used for anything other than `rippled`'s databases.{% /admonition %}

2
blog/2019/websocket-tool-update.md
View File

@@ -44,7 +44,7 @@ The new Permalink button, represented by a button with a chain-link icon, provid
Maybe you're more comfortable using the command line, or you're trying to figure out how to replicate a given thing using JSON-RPC. The new curl syntax button, represented by a `>_` icon, loads a popup with the current inputs of the request box translated into a JSON-RPC call you can make with [the `curl` utility](https://curl.haxx.se/). Copy-paste this into your command line or your bash scripts and see it go!
**Note:** The [`path_find`](/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find/) command isn't available over JSON-RPC, so the button is hidden when that command is selected. Some other commands may not work without modification on JSON-RPC; for example, the [`subscribe`](/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe/) and [`unsubscribe`](/docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe/) commands require an admin-only `url` callback field in JSON-RPC.
{% admonition type="info" name="Note" %}The [`path_find`](/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find/) command isn't available over JSON-RPC, so the button is hidden when that command is selected. Some other commands may not work without modification on JSON-RPC; for example, the [`subscribe`](/docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe/) and [`unsubscribe`](/docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe/) commands require an admin-only `url` callback field in JSON-RPC.{% /admonition %}
### Error Highlighting

2
blog/2020/developer-reflections-xrplorer.md
View File

@@ -16,7 +16,7 @@ Xrplorer was built by [Thomas Silkjaer](https://twitter.com/Silkjaer), a Danish
<!-- BREAK -->
**Note:** The Xrplorer project as described in this post has been deprecated, as forensics and other data are being combined with related efforts within the XRP Ledger Foundation. _(Updated October 2022)_
{% admonition type="info" name="Note" %}The Xrplorer project as described in this post has been deprecated, as forensics and other data are being combined with related efforts within the XRP Ledger Foundation. _(Updated October 2022)_{% /admonition %}
A primary benefit of the graph database is that the ledgers are not stored in their original binary form or JSON representations, which makes it easier to do more complex relational queries, apply graph algorithms, run fraud detection algorithms and integrate XRP Ledger data with machine learning.

2
blog/2020/fixcheckthreading-fixpaychanrecipientownerdir-lost-majority.md
View File

@@ -27,7 +27,7 @@ All XRP Ledger servers should continue to operate as normal for now. If any new
- If you operate a `rippled` server, please [upgrade](https://xrpl.org/install-rippled.html) to version 1.4.0.
**Caution:** Upgrading to v1.4.0 may take longer than usual because of SQL database cleanup the server performs the first time after upgrading. For more information, see [XRP Ledger version 1.4.0 Upgrade Advisory](https://xrpl.org/blog/2020/rippled-1.4.0-upgrade-advisory.html).
{% admonition type="warning" name="Caution" %}Upgrading to v1.4.0 may take longer than usual because of SQL database cleanup the server performs the first time after upgrading. For more information, see [XRP Ledger version 1.4.0 Upgrade Advisory](https://xrpl.org/blog/2020/rippled-1.4.0-upgrade-advisory.html).{% /admonition %}
- If you use the XRP Ledger APIs to list payment channels, such as using the [account_channels](https://xrpl.org/account_channels.html) method, be aware that the fixPayChanRecipientOwnerDir amendment affects the results of this API. Specifically, the method will list newly-created channels for which the specified account is the recipient. Previously, this method only listed channels for which the account is the sender. (Existing payment channels for which the specified account is the recipient will continue not to appear in the results. Only new channels, created after the amendment becomes enabled, are affected.)

2
blog/2020/requirefullycanonicalsig-fixqualityupperbound-flowcross-enabled.md
View File

@@ -22,7 +22,7 @@ With these amendments enabled, **version 1.5.0 is the minimum** server version t
For instructions on upgrading `rippled` on supported platforms, see [Install `rippled`](https://xrpl.org/install-rippled.html).
**Note:** As of 2020-08-04, [version 1.6.0 is in the release candidate process](https://github.com/ripple/rippled/commit/7b048b423e8ae08a54018a89231d050b9f562855), so the full 1.6.0 release is expected in the near future.
{% admonition type="info" name="Note" %}As of 2020-08-04, [version 1.6.0 is in the release candidate process](https://github.com/ripple/rippled/commit/7b048b423e8ae08a54018a89231d050b9f562855), so the full 1.6.0 release is expected in the near future.{% /admonition %}
- If you use a custom or very old (pre-2014) tool for signing XRP Ledger transactions using secp256k1, check that your tool produces _fully canonical_ signatures. All valid Ed25519 signatures are fully canonical. If your tool produces secp256k1 signatures that are not fully canonical (see [Alternate secp256k1 signatures](https://xrpl.org/transaction-malleability.html#alternate-secp256k1-signatures) for details), you must update your tool to continue sending XRP Ledger transactions.

2
blog/2021/five-upcoming-amendments.md
View File

@@ -26,7 +26,7 @@ Each amendment will become enabled if it maintains support from at least 80% of
If you operate an XRP Ledger (`rippled`) server, you should upgrade to **version 1.7.3** (or higher) as soon as possible, for service continuity.
**Note:** Version 1.8.0 is currently in the release candidate stage, and also supports these amendments. However, the amendments may go live before version 1.8.0 reaches full release, so you should not wait to upgrade.
{% admonition type="info" name="Note" %}Version 1.8.0 is currently in the release candidate stage, and also supports these amendments. However, the amendments may go live before version 1.8.0 reaches full release, so you should not wait to upgrade.{% /admonition %}
No action is needed for applications and integrations with the XRP Ledger. You may want to review how [Tickets](https://xrpl.org/tickets.html) work to see if you want to use them in your software, or enable your users to use them.

2
blog/2021/ripple-lib-drops-lodash-browsers.md
View File

@@ -31,7 +31,7 @@ Starting with 1.10.0, ripple-lib incorporates Lodash into the browser-ready Java
<script src="https://unpkg.com/ripple-lib@1.10.0/build/ripple-latest-min.js"></script>
```
**Tip:** You can safely update ripple-lib to 1.10.0 even if you haven't removed the Lodash script tag. The extra script tag is now an unnecessary extra download for most cases, but it doesn't cause errors if it's still there.
{% admonition type="success" name="Tip" %}You can safely update ripple-lib to 1.10.0 even if you haven't removed the Lodash script tag. The extra script tag is now an unnecessary extra download for most cases, but it doesn't cause errors if it's still there.{% /admonition %}
## Same Process on Node.js

8
blog/2022/introducing-xrpl-py-2.0.0beta.md
View File

@@ -76,7 +76,7 @@ OfferCancel(
),
```
**Tip:** You can also omit the `sequence` field and use `autofill` before signing your transaction.
{% admonition type="success" name="Tip" %}You can also omit the `sequence` field and use `autofill` before signing your transaction.{% /admonition %}
### Core Keypairs Seed Generation
@@ -93,7 +93,7 @@ DUMMY_BYTES = b"\x01\x02\x03\x04\x05\x06\x07\x08\t\n\x0b\x0c\r\x0e\x0f\x10"
seed = generate_seed(DUMMY_BYTES.hex())
```
**Note:** If your string is longer than 16 bytes, you must truncate it before passing it into `generate_seed()`
{% admonition type="info" name="Note" %}If your string is longer than 16 bytes, you must truncate it before passing it into `generate_seed()`{% /admonition %}
### Wallet Constructor
@@ -111,7 +111,7 @@ wallet = Wallet.from_seed("snoPBrXtMeMyMHUVTgbuqAfg1SUTb", algorithm="secp256k1"
// wallet.address: rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh
```
**Note:** If your seed previously used the secp256k1 algorithm to decode, and you don't specify it explicitly, `Wallet.from_seed()` returns a different classic address and public / private keys.
{% admonition type="info" name="Note" %}If your seed previously used the secp256k1 algorithm to decode, and you don't specify it explicitly, `Wallet.from_seed()` returns a different classic address and public / private keys.{% /admonition %}
## Start Building
@@ -121,7 +121,7 @@ You can install this beta version using pip:
pip install xrpl-py==2.0.0b0
```
**Note:** This beta does not include Automated Market-Maker (AMM) or Sidechains functionality. This is only for testing Wallet changes.
{% admonition type="info" name="Note" %}This beta does not include Automated Market-Maker (AMM) or Sidechains functionality. This is only for testing Wallet changes.{% /admonition %}
If you're just getting started using xrpl-py, see [Get Started Using Python](https://xrpl.org/get-started-using-python.html), the [xrpl-py source code repository](https://github.com/XRPLF/xrpl-py/tree/xrpl-py-2.0), or [reference documentation](https://xrpl-py.readthedocs.io/en/stable/).

2
blog/2022/rippled-1.8.4.md
View File

@@ -60,7 +60,7 @@ path=/var/lib/rippled/db/nudb
fast_load=1
```
**Caution:** When the server is 'fast loading' data, it does not open JSON-RPC and WebSocket interfaces until after the initial load is completed. Because of this, it may appear unresponsive or down.
{% admonition type="warning" name="Caution" %}When the server is 'fast loading' data, it does not open JSON-RPC and WebSocket interfaces until after the initial load is completed. Because of this, it may appear unresponsive or down.{% /admonition %}
## Security Fixes

2
blog/2023/data-api-v2-deprecated.md
View File

@@ -13,7 +13,7 @@ theme:
The Ripple Data API v2 was deprecated in 2021 with no additional support; it will be shut down on October 15, 2023.
**Note:** The [XRP Distribution endpoint](https://data.ripple.com/v2/network/xrp_distribution) will remain.
{% admonition type="info" name="Note" %}The [XRP Distribution endpoint](https://data.ripple.com/v2/network/xrp_distribution) will remain.{% /admonition %}
If you need information on the old Data API, see the [rippled-historical-database repository](https://github.com/ripple/rippled-historical-database).

2
blog/2023/upcoming-devnet-reset.md
View File

@@ -38,7 +38,7 @@ We plan to reset Devnet so that it has all the following amemdments enabled:
- Amendments currently enabled on Mainnet.
**Note:** For retired amendments, the Devnet will follow the amended behavior but the retired amendment's ID will not appear enabled in the on-ledger `Amendments` entry or the `feature` API method.
{% admonition type="info" name="Note" %}For retired amendments, the Devnet will follow the amended behavior but the retired amendment's ID will not appear enabled in the on-ledger `Amendments` entry or the `feature` API method.{% /admonition %}
- Amendments that are "open for voting" as of version 1.11.0, including FixNFTokenRemint and XRPFees.

12
blog/2023/xrpl-py-2.0-release.md
View File

@@ -91,7 +91,7 @@ response = send_reliable_submission(signed_tx, client)
response = submit_and_wait(tx, client, test_wallet)
```
**Tip:** You can also use `submit_and_wait` as a direct replacement for `send_reliable_submission` if you want to handle autofill and signing separately from transaction submission.
{% admonition type="success" name="Tip" %}You can also use `submit_and_wait` as a direct replacement for `send_reliable_submission` if you want to handle autofill and signing separately from transaction submission. {% /admonition %}
#### `submit_transaction` -> `submit`
@@ -205,7 +205,7 @@ Payment(
)
```
**Tip:** You can also omit the `sequence` field and use `autofill` before signing your transaction. The `submit_and_wait` method does this automatically when you give it an unsigned transaction.
{% admonition type="success" name="Tip" %}You can also omit the `sequence` field and use `autofill` before signing your transaction. The `submit_and_wait` method does this automatically when you give it an unsigned transaction.{% /admonition %}
#### `Wallet.classic_address` -> `Wallet.address`
@@ -227,7 +227,9 @@ Payment(
amount="10",
)
```
**Tip:** `classic_address` still exists as an alias, and both are now also read-only since they should never change.
{% admonition type="success" name="Tip" %}
`classic_address` still exists as an alias, and both are now also read-only since they should never change.
{% /admonition %}
### Other changes
@@ -262,7 +264,7 @@ DUMMY_BYTES = b"\x01\x02\x03\x04\x05\x06\x07\x08\t\n\x0b\x0c\r\x0e\x0f\x10"
seed = generate_seed(DUMMY_BYTES.hex())
```
**Note:** If your string is longer than 16 bytes, you must truncate it before passing it into `generate_seed()`. Previously, the method would quietly truncate it for you, but now it is explicit in order to raise errors when the wrong data type is provided.
{% admonition type="info" name="Note" %}If your string is longer than 16 bytes, you must truncate it before passing it into `generate_seed()`. Previously, the method would quietly truncate it for you, but now it is explicit in order to raise errors when the wrong data type is provided.{% /admonition %}
#### Sign (async -> sync)
@@ -362,7 +364,7 @@ You can install this version of xrpl-py using pip:
pip install xrpl-py
```
**Note:** The xrpl-py 2.0 release does not include Automated Market-Maker (AMM) or Sidechains functionality. Those are on separate beta branches.
{% admonition type="info" name="Note" %}The xrpl-py 2.0 release does not include Automated Market-Maker (AMM) or Sidechains functionality. Those are on separate beta branches.{% /admonition %}
If you're just getting started using xrpl-py, see [Get Started Using Python](https://xrpl.org/get-started-using-python.html), the [xrpl-py source code repository](https://github.com/XRPLF/xrpl-py), or [reference documentation](https://xrpl-py.readthedocs.io/en/stable/).