xrpl.js 2: update many mentions, more code

This commit is contained in:
mDuo13
2021-10-08 18:33:45 -07:00
parent 6fc9afbd7e
commit 64e915eeb2
22 changed files with 219 additions and 242 deletions

View File

@@ -62,11 +62,7 @@ The serialization processes described here are implemented in multiple places an
- In JavaScript in the [`ripple-binary-codec`](https://github.com/ripple/ripple-binary-codec/) package.
- In Python 3 in [this repository's code samples section]({{target.github_forkurl}}/blob/{{target.github_branch}}/content/_code-samples/tx-serialization/serialize.py).
Additionally, the following libraries also provide serialization support:
{% include '_snippets/libs-snippet.md' %}
These implementations are all provided with permissive open-source licenses, so you can import, use, or adapt the code for your needs.
Additionally, many [client libraries](client-libraries) provide serialization support under permissive open-source licenses, so you can import, use, or adapt the code for your needs.

View File

@@ -46,7 +46,7 @@ The `AccountTxnID` field cannot be used on transactions that use [Tickets](ticke
## Auto-fillable Fields
Some fields can be automatically filled in before a transaction is signed, either by a `rippled` server or by a library used for signing such as [ripple-lib][]. Auto-filling values requires an active connection to the XRP Ledger to get the latest state, so it cannot be done offline. Both [ripple-lib][] and `rippled` can automatically provide the following values:
Some fields can be automatically filled in before a transaction is signed, either by a `rippled` server or by a [client library](client-libraries.html). Auto-filling values requires an active connection to the XRP Ledger to get the latest state, so it cannot be done offline. The details can vary by library, but auto-filling always provides suitable values for at least the following fields:
* `Fee` - Automatically fill in the [Transaction Cost][] based on the network.