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

Japanese translation: fix all the broken links

Browse Source
This commit is contained in:
mDuo13
2019-11-05 18:32:59 -08:00
parent 7b188351c0
commit 2bfe9e574b
62 changed files with 196 additions and 132 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/references/rippled-api/transaction-formats/transaction-common-fields.md
View File

@@ -42,7 +42,9 @@ One situation in which this is useful is if you have a primary system for submit
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:
* `Fee` - Automatically fill in the [Transaction Cost][] based on the network.
**Note:** When using `rippled`'s [sign command][], you can limit the maximum possible auto-filled value, using the `fee_mult_max` and `fee_mult_div` parameters.)
* `Sequence` - Automatically use the next sequence number for the account sending the transaction.
For a production system, we recommend _not_ leaving these fields to be filled by the server. For example, if transaction costs become high due to a temporary spike in network load, you may want to wait for the cost to decrease before sending some transactions, instead of paying the temporarily-high cost.