mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-12-06 17:27:57 +00:00
inc'd feedback
This commit is contained in:
@@ -1799,15 +1799,25 @@ pages:
|
||||
targets:
|
||||
- local
|
||||
|
||||
- md: references/rippled-api/ledger-data-formats/ledger-object-types/ledger-object-types.md
|
||||
- md: references/rippled-api/ledger-data-formats/ledger-object-ids.md
|
||||
html: ledger-object-ids.html
|
||||
funnel: Docs
|
||||
doc_type: References
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
blurb: All objects in a ledger's state tree have a unique ID.
|
||||
targets:
|
||||
- local
|
||||
|
||||
- name: Ledger Object Types
|
||||
html: ledger-object-types.html
|
||||
funnel: Docs
|
||||
doc_type: References
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
subcategory: Ledger Object Types
|
||||
# template: template-landing-children.html #TODO: consider dropping the md since the page children handles this OK
|
||||
blurb: Specifications for the types of objects that can be stored in a ledger's state tree.
|
||||
template: template-landing-children.html #TODO: consider dropping the md since the page children handles this OK
|
||||
blurb: Each ledger's state tree consists of a set of ledger objects, which collectively represent all settings, balances, and relationships in the shared ledger. In the peer protocol that rippled servers use to communicate with each other, ledger objects are represented in their raw binary format. In the rippled API, ledger objects are represented as JSON objects.
|
||||
targets:
|
||||
- local
|
||||
|
||||
@@ -1818,7 +1828,7 @@ pages:
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
subcategory: Ledger Object Types
|
||||
# blurb: The settings, XRP balance, and other metadata for one account.
|
||||
blurb: The settings, XRP balance, and other metadata for one account.
|
||||
targets:
|
||||
- local
|
||||
|
||||
@@ -1829,7 +1839,7 @@ pages:
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
subcategory: Ledger Object Types
|
||||
# blurb: Singleton object with status of enabled and pending amendments.
|
||||
blurb: Singleton object with status of enabled and pending amendments.
|
||||
targets:
|
||||
- local
|
||||
|
||||
@@ -1840,7 +1850,7 @@ pages:
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
subcategory: Ledger Object Types
|
||||
# blurb: A check that can be redeemed for money by its destination.
|
||||
blurb: A check that can be redeemed for money by its destination.
|
||||
targets:
|
||||
- local
|
||||
|
||||
@@ -1851,7 +1861,7 @@ pages:
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
subcategory: Ledger Object Types
|
||||
# blurb: Contains links to other objects.
|
||||
blurb: Contains links to other objects.
|
||||
targets:
|
||||
- local
|
||||
|
||||
@@ -1862,7 +1872,7 @@ pages:
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
subcategory: Ledger Object Types
|
||||
# blurb: Contains XRP held for a conditional payment.
|
||||
blurb: Contains XRP held for a conditional payment.
|
||||
targets:
|
||||
- local
|
||||
|
||||
@@ -1873,7 +1883,7 @@ pages:
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
subcategory: Ledger Object Types
|
||||
# blurb: Singleton object with consensus-approved base transaction cost and reserve requirements.
|
||||
blurb: Singleton object with consensus-approved base transaction cost and reserve requirements.
|
||||
targets:
|
||||
- local
|
||||
|
||||
@@ -1884,7 +1894,7 @@ pages:
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
subcategory: Ledger Object Types
|
||||
# blurb: Lists of prior ledger versions' hashes for history lookup.
|
||||
blurb: Lists of prior ledger versions' hashes for history lookup.
|
||||
targets:
|
||||
- local
|
||||
|
||||
@@ -1895,7 +1905,7 @@ pages:
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
subcategory: Ledger Object Types
|
||||
# blurb: An order to make a currency trade.
|
||||
blurb: An order to make a currency trade.
|
||||
targets:
|
||||
- local
|
||||
|
||||
@@ -1906,7 +1916,7 @@ pages:
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
subcategory: Ledger Object Types
|
||||
# blurb: A channel for asynchronous XRP payments.
|
||||
blurb: A channel for asynchronous XRP payments.
|
||||
targets:
|
||||
- local
|
||||
|
||||
@@ -1917,7 +1927,7 @@ pages:
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
subcategory: Ledger Object Types
|
||||
# blurb: Links two accounts, tracking the balance of one currency between them. The concept of a trust line is an abstraction of this object type.
|
||||
blurb: Links two accounts, tracking the balance of one currency between them. The concept of a trust line is an abstraction of this object type.
|
||||
targets:
|
||||
- local
|
||||
|
||||
@@ -1928,7 +1938,7 @@ pages:
|
||||
supercategory: rippled API
|
||||
category: Ledger Data Formats
|
||||
subcategory: Ledger Object Types
|
||||
# blurb: A list of addresses for multi-signing transactions.
|
||||
blurb: A list of addresses for multi-signing transactions.
|
||||
targets:
|
||||
- local
|
||||
|
||||
|
||||
Reference in New Issue
Block a user