Merge pull request #3371 from XRPLF/fix_src_links_admin_apis_etc

Update source links in admin api refs & elsewhere
This commit is contained in:
Rome Reginelli
2025-12-02 12:32:08 -08:00
committed by GitHub
28 changed files with 755 additions and 813 deletions

View File

@@ -1,11 +1,9 @@
---
html: create-custom-transactors.html
parent: contribute-code.html
seo:
description: Create custom transactors to interact with the XRP Ledger.
labels:
- Development
- Blockchain
- Development
- Blockchain
---
# Create Custom Transactors
@@ -78,8 +76,8 @@ The `preflight` function checks for errors in the transaction itself before acce
{% admonition type="info" name="Note" %}The `~` symbol returns an optional type.{% /admonition %}
- You can view ledger and transaction schemas here:
- [`LedgerFormats.cpp`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp)
- [`TxFormats.cpp`](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TxFormats.cpp)
- [`ledger_entries.macro`](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/detail/ledger_entries.macro)
- [`transactions.macro`](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/detail/transactions.macro)
- `rippled` summarizes transaction results with result codes. See: [Transaction Results](../../docs/references/protocol/transactions/transaction-results/index.md)
@@ -344,7 +342,7 @@ EscrowFinish::calculateBaseFee(ReadView const& view, STTx const& tx)
### `makeTxConsequences`
`rippled` uses a [`TxConsequences`](https://github.com/XRPLF/rippled/blob/master/src/ripple/app/tx/applySteps.h#L41-L44) class to describe the outcome to an account when applying a transaction. It tracks the fee, maximum possible XRP spent, and how many sequence numbers are consumed by the transaction. There are three types of consequences:
`rippled` uses a [`TxConsequences`](https://github.com/XRPLF/rippled/blob/70d5c624e8cf732a362335642b2f5125ce4b43c1/src/xrpld/app/tx/applySteps.h#L58) class to describe the outcome to an account when applying a transaction. It tracks the fee, maximum possible XRP spent, and how many sequence numbers are consumed by the transaction. There are three types of consequences:
- **Normal:** The transactor doesn't affect transaction signing and _only_ consumes an XRP fee. Transactions that spend XRP beyond the fee aren't considered normal.
- **Blocker:** The transactor affects transaction signing, preventing valid transactions from queueing behind it.