From d4df84536cdfaf0cd6d9f5e99a3d43bcf2522641 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Thu, 28 Aug 2014 18:02:14 -0700 Subject: [PATCH] [FIX] rippled wallet_propose, time links, gatewayd architecture image links --- gatewayd.md | 4 ++-- websocket_api.md | 10 +++++----- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/gatewayd.md b/gatewayd.md index 7d2dd393dd..321acf0ebe 100644 --- a/gatewayd.md +++ b/gatewayd.md @@ -42,7 +42,7 @@ Gatewayd has effectively 4 queues: an inbox and outbox for transactions going fr You can visualize Gatewayd's architecture according to the following diagram: -![Gatewayd Architecture](img/gatewayd_architecture.png) +[![Gatewayd Architecture](img/gatewayd_architecture.png)](img/gatewayd_architecture.png) ### External Connector ### @@ -79,7 +79,7 @@ You can get a list of services and their status by running the following command One of the key aspects of Gatewayd is that it keeps records of all the transactions that go in and out of the gateway, which get persisted to the database. Gatewayd is intentionally designed so that you can manually view and modify the database records if you want to. The important data models are defined as in the following diagram: -![Data Models chart](img/gatewayd-datamodel_current.png) +[![Data Models chart](img/gatewayd-datamodel_current.png)](img/gatewayd-datamodel_current.png) In short, the key data models are: External Account, Ripple Address, User, External Transaction, and Ripple Transaction. It's important to note that incoming and outgoing transactions of the same type (Ripple or External) are persisted to a single, shared database table. diff --git a/websocket_api.md b/websocket_api.md index eb324e4c21..043f279bfd 100644 --- a/websocket_api.md +++ b/websocket_api.md @@ -1101,14 +1101,14 @@ The response follows the [standard format](#response-formatting), with a success | Field | Type | Description | |-------|------|-------------| -| master_seed | String | The [master seed|https://ripple.com/wiki/Master_Key] from which all other information about this account is derived, in Ripple's base-58 encoded string format. | +| master_seed | String | The [master seed](https://ripple.com/wiki/Master_Key) from which all other information about this account is derived, in Ripple's base-58 encoded string format. | | master_seed_hex | String | The master seed, in hex format. | | master_key | String | The master seed, in [RFC 1751](http://tools.ietf.org/html/rfc1751) format. | | account_id | String | The public address of the account. | | public_key | String | The public key of the account, in encoded string format. | | public_key_hex | String | The public key of the account, in hex format. | -The key generated by this method can also be used as a regular key for an account if you use the [SetRegularKey transaction type|https://ripple.com/wiki/index.php/API_Example_Transactions#Set_Regular_Key] to do so. +The key generated by this method can also be used as a regular key for an account if you use the [SetRegularKey transaction type](https://ripple.com/wiki/index.php/API_Example_Transactions#Set_Regular_Key) to do so. # Managing Ledgers # @@ -1193,7 +1193,7 @@ The response follows the [standard format](#response-formatting), with a success |-------|------|-------------| | accepted | Boolean | This designation is for internal protocol use, and should not be used. It does *not* mean the same as `validated` | | account_hash | String | Hash of all account state information in this ledger, as hex | -| close_time | Integer | The time this ledger was closed, in seconds since the [Ripple Epoch](https://ripple.com/wiki/JSON_format#time) | +| close_time | Integer | The time this ledger was closed, in seconds since the [Ripple Epoch](#specifying-time) | | close_time_human | String | The time this ledger was closed, in human-readable format | | close_time_resolution | Integer | Approximate number of seconds between closing one ledger version and closing the next one | | closed | Boolean | Whether or not this ledger has been closed | @@ -4462,7 +4462,7 @@ The fields from a ledger stream message are as follows: | fee_ref | Unsigned Integer | Cost of the 'reference transaction' in 'fee units'. (See [Transaction Fee Terminology](https://ripple.com/wiki/Transaction_Fee#Fee_Terminology) | | ledger_hash | String | Unique hash of the ledger that was closed, as hex | | ledger_index | Unsigned Integer | Sequence number of the ledger that was closed | -| ledger_time | Unsigned Integer | The time this ledger was closed, in seconds since the Ripple Epoch | +| ledger_time | Unsigned Integer | The time this ledger was closed, in seconds since the [Ripple Epoch](#specifying-time) | | reserve_base | Unsigned Integer | The minimum reserve, in drops of XRP, that is required for an account | | reserve_inc | Unsigned Integer | The increase in account reserve that is added for each item the account owns, such as offers or trust lines | | txn_count | Unsigned Integer | Number of transactions newly included in this ledger | @@ -4833,7 +4833,7 @@ The `state` object may have some arrangement of the following fields: | server_state | String | A string indicating to what extent the server is participating in the network. See [Possible Server States](#possible-server-states) for more details. | | validated_ledger | Object | Information about the fully-validated ledger with the highest sequence number (the most recent) | | validated_ledger.base_fee | Unsigned Integer | Base fee, in drops of XRP, for propagating a transaction to the network. -| validated_ledger.close_time | Number | Time this ledger was closed, in seconds since the Ripple Epoch | +| validated_ledger.close_time | Number | Time this ledger was closed, in seconds since the [Ripple Epoch](#specifying-time) | | validated_ledger.hash | String | Unique hash of this ledger version, as hex | | validated_ledger.reserve_base | Unsigned Integer | Minimum amount, in drops of XRP, necessary for every account to keep in reserve | | validated_ledger.reserve_inc | Unsigned Integer | Amount, in drops of XRP, that is added to the account reserve for each item the account owns in the ledger. |