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

Fix mostly transaction reference links

Browse Source
This commit is contained in:
mDuo13
2018-05-11 14:37:57 -07:00
parent cffb9edf60
commit 5520e0843d
22 changed files with 44 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/references/rippled-api/public-rippled-methods/transaction-methods/sign_for.md
View File

@@ -1,7 +1,7 @@
# sign_for
[[Source]<br>](https://github.com/ripple/rippled/blob/release/src/ripple/rpc/handlers/SignFor.cpp "Source")
The `sign_for` command provides one signature for a [multi-signed transaction](reference-transaction-format.html#multi-signing).
The `sign_for` command provides one signature for a [multi-signed transaction](multi-signing.html).
This command requires the [MultiSign amendment](known-amendments.html#multisign) to be enabled. [New in: rippled 0.31.0][]

4
content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md
View File

@@ -16,7 +16,7 @@ A submit-only request includes the following parameters:
| `Field` | Type | Description |
|:------------|:--------|:-----------------------------------------------------|
| `tx_blob` | String | Hex representation of the signed transaction to submit. This can be a [multi-signed transaction](reference-transaction-format.html#multi-signing). |
| `tx_blob` | String | Hex representation of the signed transaction to submit. This can be a [multi-signed transaction](multi-signing.html). |
| `fail_hard` | Boolean | (Optional, defaults to false) If true, and the transaction fails locally, do not retry or relay the transaction to other servers |
### Request Format
@@ -60,7 +60,7 @@ submit 1200002280000000240000000361D4838D7EA4C6800000000000000000000000000055534
## Sign-and-Submit Mode
This mode signs a transaction and immediately submits it. This mode is intended to be used for testing. You cannot use this mode for [multi-signed transactions](reference-transaction-format.html#multi-signing).
This mode signs a transaction and immediately submits it. This mode is intended to be used for testing. You cannot use this mode for [multi-signed transactions](multi-signing.html).
You can provide the secret key used to sign the transaction in the following ways:

2
content/references/rippled-api/public-rippled-methods/transaction-methods/submit_multisigned.md
View File

@@ -1,7 +1,7 @@
# submit_multisigned
[[Source]<br>](https://github.com/ripple/rippled/blob/release/src/ripple/rpc/handlers/SubmitMultiSigned.cpp "Source")
The `submit_multisigned` command applies a [multi-signed](reference-transaction-format.html#multi-signing) transaction and sends it to the network to be included in future ledgers. (You can also submit multi-signed transactions in binary form using the [`submit` command in submit-only mode](#submit-only-mode).)
The `submit_multisigned` command applies a [multi-signed](multi-signing.html) transaction and sends it to the network to be included in future ledgers. (You can also submit multi-signed transactions in binary form using the [`submit` command in submit-only mode](#submit-only-mode).)
This command requires the [MultiSign amendment](known-amendments.html#multisign) to be enabled. [New in: rippled 0.31.0][]

4
content/references/rippled-api/public-rippled-methods/transaction-methods/tx.md
View File

@@ -186,7 +186,7 @@ An example of a successful response:
<!-- MULTICODE_BLOCK_END -->
The response follows the [standard format][], with a successful result containing the fields of the [Transaction object](reference-transaction-format.html) as well as the following additional fields:
The response follows the [standard format][], with a successful result containing the fields of the [Transaction object](transaction-formats.html) as well as the following additional fields:
| `Field` | Type | Description |
|:---------------|:-----------------|:-----------------------------------------|
@@ -195,7 +195,7 @@ The response follows the [standard format][], with a successful result containin
| `ledger_index` | Unsigned Integer | The sequence number of the ledger that includes this transaction. |
| `meta` | Object | Various metadata about the transaction. |
| `validated` | Boolean | True if this data is from a validated ledger version; if omitted or set to false, this data is not final. |
| (Various) | (Various) | Other fields from the [Transaction object](reference-transaction-format.html) |
| (Various) | (Various) | Other fields from the [Transaction object](transaction-formats.html) |
## Possible Errors