diff --git a/concept-amendments.html b/concept-amendments.html index 042c15e7d3..fe720efe5f 100644 --- a/concept-amendments.html +++ b/concept-amendments.html @@ -1,137 +1,152 @@ - - - - -Amendments - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
- -
-
-

Amendments

+ + + +
+ +
+
+

Amendments

(New in version 0.31.0)

The Amendments system provides a means of introducing new features to the decentralized Ripple consensus network without causing disruptions. The amendments system works by utilizing the core consensus process of the network to approve any changes by showing continuous support before those changes go into effect. An amendment normally requires 80% support for two weeks before it can apply.

When an Amendment has been enabled, it applies permanently to all ledger versions after the one that included it. You cannot disable an Amendment, unless you introduce a new Amendment to do so.

@@ -316,54 +331,61 @@ TrustSetAuth

Introduces Tickets as a way to reserve a transaction sequence number for later execution. Creates the Ticket ledger node type and the transaction types TicketCreate and TicketCancel.

This amendment is still in development.

-
-
-
+
+
+
+ diff --git a/concept-fee-voting.html b/concept-fee-voting.html index 819271ddf7..deb5b7f094 100644 --- a/concept-fee-voting.html +++ b/concept-fee-voting.html @@ -1,137 +1,152 @@ - - - - -Fee Voting - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
- -
-
-

Fee Voting

+ + + +
+ +
+
+

Fee Voting

Validators can vote for changes to basic transaction cost as well as reserve requirements. If the preferences in a validator's configuration are different than the network's current settings, the validator expresses its preferences to the network periodically. If a quorum of validators agrees on a change, they can apply a change that takes effect thereafter. Validators may do this for various reasons, especially to reflect long-term changes in the value of XRP.

Operators of rippled validators can set their preferences for the transaction cost and reserve requirements in the [voting] stanza of the rippled.cfg file. Caution: insufficient requirements could expose the Ripple peer-to-peer network to denial-of-service attacks. The parameters you can set are as follows:

@@ -171,54 +186,61 @@
  • Flag ledger +1: Validators insert SetFee pseudo-transaction into their proposed ledgers.
  • Flag ledger +2: New settings take effect, if a SetFee psuedotransaction achieved consensus.
    • - - - + + + + diff --git a/concept-fees.html b/concept-fees.html index 5bfbbb2269..1ec2d80aad 100644 --- a/concept-fees.html +++ b/concept-fees.html @@ -1,137 +1,152 @@ - - - - -Fees (Disambiguation) - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Fees (Disambiguation)

    + + + +
    + +
    +
    +

    Fees (Disambiguation)

    The Ripple Consensus Ledger is a decentralized ledger, secured by cryptography and operated by a distributed peer-to-peer network of servers. This means that no one party, not even Ripple, can require a fee for access to the network.

    However, the rules of the Ripple Consensus Ledger include several types of fees, including neutral fees which protect the ledger against abuse. These neutral fees are not paid to anyone. There are also several optional ways that users can collect fees from each other, both inside and outside the Ripple Consensus Ledger.

    In the Ledger

    @@ -144,54 +159,61 @@

    Outside the Ledger

    Although the fees described above are the only fees built into the Ripple Consensus Ledger, people can still invent ways to charge fees associated with the ledger. For example, gateways commonly charge their customers to send money into and out of the Ripple Consensus Ledger.

    Many other fees are also possible. Businesses might charge for access to a client application, maintenance of non-Ripple accounts, exchange services (especially when buying XRP on a private market instead of directly within the Ripple Consensus Ledger) and any number of other services. Always be aware of the fee schedule before doing business with any gateway or other financial institution.

    -
    -
    -
    +
    +
    +
    + diff --git a/concept-freeze.html b/concept-freeze.html index 82a83f75f6..e2d1956e74 100644 --- a/concept-freeze.html +++ b/concept-freeze.html @@ -1,137 +1,152 @@ - - - - -Freeze - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Freeze Features

    + + + +
    + +
    +
    +

    Freeze Features

    The Ripple Consensus Ledger gives accounts the ability to freeze non-XRP balances, which can be useful to comply with regulatory requirements, or while investigating suspicious activity. There are three settings related to freezes:

    The Ripple Consensus Ledger cannot force a gateway to honor the obligations that its issued funds represent, so giving up the ability to enable a Global Freeze cannot protect customers. However, giving up the ability to disable a Global Freeze ensures that the Global Freeze feature is not used unfairly against some customers.

    The No Freeze setting applies to all currencies issued to and from an account. If you want to be able to freeze some currencies but not others, you should use different accounts for each currency.

    -

    You can only enable the No Freeze setting with a transaction signed by your account's master key. You cannot use a Regular Key or a multi-signed transaction to enable No Freeze.

    +

    You can only enable the No Freeze setting with a transaction signed by your account's master key. You cannot use a Regular Key or a multi-signed transaction to enable No Freeze.

    Technical Details

    Enabling or Disabling Individual Freeze

    Using rippled

    @@ -815,54 +830,61 @@ api.connect().then(() => {
  • Gateway Bulletin GB-2014-02 New Feature: Balance Freeze
  • Freeze Code Samples
    • -
    -
    -
    +
    +
    +
    + diff --git a/concept-issuing-and-operational-addresses.html b/concept-issuing-and-operational-addresses.html index b46336f472..2c8bf1bb72 100644 --- a/concept-issuing-and-operational-addresses.html +++ b/concept-issuing-and-operational-addresses.html @@ -1,130 +1,145 @@ - - - - -Issuing and Operational Addresses - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Issuing and Operational Addresses

    + + + +
    + +
    +
    +

    Issuing and Operational Addresses

    All non-XRP currency balances (issuances) in the Ripple Consensus Ledger (RCL) are tied to accounting relationships between two Ripple addresses. To control an address in the RCL, you only need the secret key mathematically connected to that address. Since no party can unilaterally prevent transactions or correct the ledger, financial institutions typically use multiple Ripple ledger addresses to minimize the risk associated with a compromised secret key. Ripple strongly recommends the following separation of roles:

    • One issuing address, also known as a "cold wallet." This address is the hub of the financial institution's accounting relationships in the ledger, but sends as few transactions as possible.
      • @@ -153,54 +168,61 @@

      As with operational addresses, a standby address must have an accounting relationship with the issuing address, and not with customers or partners. All precautions that apply to operational addresses also apply to standby addresses.

      Standby Address Compromise

      If a standby address is compromised, the results are similar to an operational address being compromised. A malicious actor can steal any balances possessed by the standby address, and the financial institution can change to a new standby address with no action from customers and partners.

      -
    -
    -
    +
    +
    +
    + diff --git a/concept-paths.html b/concept-paths.html index 6825135c6b..8e7d6bbc34 100644 --- a/concept-paths.html +++ b/concept-paths.html @@ -1,137 +1,152 @@ - - - - -Paths - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Paths

    + + + +
    + +
    +
    +

    Paths

    In the Ripple Consensus Ledger, paths define a way for payments to flow through intermediary steps on their way from sender to receiver. Paths enable cross-currency payments by connecting sender and receiver via market makers. Paths also enable complex settlement of offsetting debts.

    A single Payment transaction in the Ripple Consensus Ledger can use multiple paths, combining liquidity from different sources to deliver the desired amount. Thus, a transaction includes a path set, which is a collection of possible paths to take. The paths in a path set must start and end with the same currency.

    Since XRP can be sent directly to any address, an XRP-to-XRP transaction does not use any paths.

    @@ -240,54 +255,61 @@
    -
    -
    -
    +
    +
    +
    + diff --git a/concept-reserves.html b/concept-reserves.html index 6fa4721fd8..b21084d7ba 100644 --- a/concept-reserves.html +++ b/concept-reserves.html @@ -1,137 +1,152 @@ - - - - -Reserves - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Reserves

    + + + +
    + +
    +
    +

    Reserves

    The Ripple Consensus Ledger applies reserve requirements, in XRP, to protect the shared global ledger from growing excessively large as the result of spam or malicious usage. The goal is to constrain the growth of the ledger to match Moore's Law so that a current commodity-level machine can always fit the current ledger in RAM and the full ledger history on disk.

    Each account in the shared global ledger must hold a minimum of XRP in order to submit transactions, and it cannot send this XRP to other accounts. You cannot create a new account unless you send enough XRP to meet the minimum reserve requirement.

    The current minimum reserve requirement is 20 XRP. (This is the cost of an account that owns no additional objects in the ledger.)

    @@ -157,54 +172,61 @@

    Exception: When an account is below the reserve requirement, it can send new OfferCreate transactions to acquire more XRP, or other currencies on its existing trust lines. These transactions cannot create new trust lines, or Offer nodes in the ledger, so they can only execute trades that consume Offers that are already in the order books.

    Changing the Reserve Requirements

    The Ripple Consensus Ledger has a mechanism for changing the reserve requirements in order to account for long-term changes in the value of XRP. Any changes have to be approved by the consensus process. See Fee Voting for more information.

    -
    -
    -
    +
    +
    +
    + diff --git a/concept-stand-alone-mode.html b/concept-stand-alone-mode.html index fe489e3c20..489a75be34 100644 --- a/concept-stand-alone-mode.html +++ b/concept-stand-alone-mode.html @@ -1,137 +1,152 @@ - - - - -Stand-Alone Mode - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Stand-Alone Mode

    + + + +
    + +
    +
    +

    Stand-Alone Mode

    You can run rippled in stand-alone mode without a consensus of trusted servers. In stand-alone mode, rippled does not communicate with any other servers in the Ripple peer-to-peer network, but you can do most of the same actions on your local server only. Stand-alone provides a method for testing rippled behavior without being tied to the live network. For example, you can test the effects of Amendments before those Amendments have gone into effect across the decentralized network.

    When you run rippled in stand-alone mode, you have to tell it what ledger version to start from:

      @@ -188,54 +203,61 @@

      In stand-alone mode, rippled makes no distinction between a "closed" ledger version and a "validated" ledger version. (For more information about the difference, see The Ripple Ledger Consensus Process.)

      Whenever rippled closes a ledger, it reorders the transactions according to a deterministic but hard-to-game algorithm. (This is an important part of consensus, since transactions may arrive at different parts of the network in different order.) When using rippled in stand-alone mode, you should manually advance the ledger before submitting a transaction that depends on the result of a previous transaction. Otherwise, the second transaction might be executed before the first transaction when you manually advance the ledger. Note: You can safely submit multiple transactions from a single address to a single ledger, because rippled sorts transactions from the same address in ascending order by Sequence number.

      -
    -
    -
    +
    +
    +
    + diff --git a/concept-transaction-cost.html b/concept-transaction-cost.html index 0fa0efff1b..02bd94e628 100644 --- a/concept-transaction-cost.html +++ b/concept-transaction-cost.html @@ -1,137 +1,152 @@ - - - - -Transaction Cost - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Transaction Cost

    + + + +
    + +
    +
    +

    Transaction Cost

    In order to protect the Ripple Consensus Ledger from being disrupted by spam and denial-of-service attacks, each transaction must destroy a small amount of XRP. This transaction cost is designed to increase along with the load on the network, making it very expensive to deliberately or inadvertently overload the network.

    Every transaction must specify how much XRP it will destroy in order to pay the transaction cost.

    Current Transaction Cost

    @@ -230,54 +245,61 @@ Transactions that do not meet the open ledger cost are FeeEscalation amendment is enabled, rippled prioritizes key reset transactions above other transactions even though the nominal transaction cost of a key reset transaction is zero.

    Changing the Transaction Cost

    In addition to short-term scaling to account for load, the Ripple Consensus Ledger has a mechanism for changing the minimum transaction cost in order to account for long-term changes in the value of XRP. Any changes have to be approved by the consensus process. See Fee Voting for more information.

    -
    -
    -
    +
    +
    +
    + diff --git a/concept-transfer-fees.html b/concept-transfer-fees.html index 744056c8ea..37b430ccd9 100644 --- a/concept-transfer-fees.html +++ b/concept-transfer-fees.html @@ -1,137 +1,152 @@ - - - - -Transfer Fees - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Transfer Fees

    + + + +
    + +
    +
    +

    Transfer Fees

    The TransferRate setting in the Ripple Consensus Ledger allows issuing gateways to charge users a transfer fee for sending that gateway's issuances to other users. When a gateway sets a transfer fee, it costs extra to send a transfer of that gateway's issuances. The sender of the transfer is debited an extra percentage based on the transfer fee, while the recipient of the transfer is credited the intended amount. The difference is the transfer fee, which becomes the property of the issuing gateway, and is no longer tracked in the Ripple Consensus Ledger. The transfer fee does not apply when sending or receiving directly to and from the issuing account, but it does apply when transferring from a hot wallet to another user.

    XRP never has a transfer fee, because it never has an issuer.

    For example, ACME Gateway might set the transfer fee to 0.5% for ACME issuances. In order for the recipient of a payment to get 2 EUR.ACME, the sender must send 2.01 EUR.ACME. After the transaction, ACME's outstanding obligations in Ripple have decreased by 0.01€, which means that it is no longer obliged to hold that amount in the account backing its Ripple issuances.

    @@ -156,54 +171,61 @@

    In rippled's JSON-RPC and WebSocket APIs, the transfer fee is specified in the TransferRate field, as an integer which represents the amount you must send in order for the recipient to get 1 billion units of the same currency. A TransferRate of 1005000000 is equivalent to a transfer fee of 0.5%. By default, the TransferRate is set at 1000000000, indicating no fee. The value of TransferRate cannot be less than 1000000000 or more than 2000000000. However, value 0 is special: it is equivalent to 1000000000, meaning no fee.

    A gateway can submit an AccountSet transaction from its cold wallet to change the TransferRate for its issuances.

    You can check an account's TransferRate with the account_info command. If the TransferRate is omitted, then that indicates no fee.

    -
    -
    -
    +
    +
    +
    + diff --git a/content/concept-freeze.md b/content/concept-freeze.md index bf3025deb7..3450c0e03f 100644 --- a/content/concept-freeze.md +++ b/content/concept-freeze.md @@ -61,7 +61,7 @@ The Ripple Consensus Ledger cannot force a gateway to honor the obligations that The No Freeze setting applies to all currencies issued to and from an account. If you want to be able to freeze some currencies but not others, you should use different accounts for each currency. -You can only enable the No Freeze setting with a transaction signed by your account's master key. You cannot use a [Regular Key](reference-transaction-format.html#setregularkey) or a [multi-signed transaction](https://wiki.ripple.com/Multisign) to enable No Freeze. +You can only enable the No Freeze setting with a transaction signed by your account's master key. You cannot use a [Regular Key](reference-transaction-format.html#setregularkey) or a [multi-signed transaction](reference-transaction-format.html#multi-signing) to enable No Freeze. # Technical Details # diff --git a/content/reference-rippled.md b/content/reference-rippled.md index f89e309979..5cc1e8b27d 100755 --- a/content/reference-rippled.md +++ b/content/reference-rippled.md @@ -540,6 +540,7 @@ The `owner_info` command is deprecated. Use [`account_objects`](#account-objects * [`connect` - Force the rippled server to connect to a specific peer](#connect) * [`consensus_info` - Get information about the state of consensus as it happens](#consensus-info) * [`feature` - Get information about protocol amendments](#feature) +* [`fee` - Get information about transaction cost](#fee) * [`fetch_info` - Get information about the server's sync with the network](#fetch-info) * [`get_counts` - Get statistics about the server's internals and memory usage](#get-counts) * [`ledger_accept` - Close and advance the ledger in stand-alone mode](#ledger-accept) diff --git a/data-api-v2-tool.html b/data-api-v2-tool.html index 26bc275e0c..ef4ddaac23 100644 --- a/data-api-v2-tool.html +++ b/data-api-v2-tool.html @@ -1,200 +1,222 @@ - - - - -Data API v2 Tool - Ripple Developer Portal - - - - - - - - - - - + + + + + Data API v2 Tool - Ripple Developer Portal + + + + + + + + + + + + + + + + + + + - -
    - -
    -
    -
    -
    -
    -
    -
    -

    REST Request

    - -
    -

    -

    -
    Invalid JSON
    -
    -

    https://data.ripple.com

    -
    -
    - -
    -
    -

    Response

    -
    - - -
    -
    -
    -
    -
    -
    -
    -
    - -
    -
    + + + - - - - - - - - + + + + + + + + + + diff --git a/index.html b/index.html index c3d088bf1f..5805f04ae7 100644 --- a/index.html +++ b/index.html @@ -1,226 +1,252 @@ - - - - -Overview - Ripple Developer Portal - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + - - - - -
    -
    - - -
    -
    -
    -
    -
    - -
    -
    -

    Welcome to the Developer Center

    -

    + + + + + + + + +

    + + +
    +
    + + + +
    +
    +
    +
    +
    + +
    +
    +

    Welcome to the Developer Center

    +

    Ripple’s distributed settlement network is built on open-source technology that anyone can use. Here are the tools developers can use to build solutions around the open-source platform.

    -
    -
    -
    -
    -
    - - -
    -
    -
    - -
    -
    - -
    -
    - -
    -
    - -
    -
    - -
    -
    -
    -
    -
    +
    +
    +
    +
    +
    + + + +
    +
    +
    + +
    +
    + +
    +
    + +
    +
    + +
    +
    + +
    +
    +
    + +
    +
    + diff --git a/reference-data-api.html b/reference-data-api.html index 4c32a369c0..f4ab1ad275 100644 --- a/reference-data-api.html +++ b/reference-data-api.html @@ -1,133 +1,148 @@ - - - - -Ripple Data API v2 - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Ripple Data API v2

    + + + +
    + +
    +
    +

    Ripple Data API v2

    The Ripple Data API v2 provides access to information about changes in the Ripple Consensus Ledger, including transaction history and processed analytical data. This information is stored in a database for easy access, which frees rippled servers to maintain fewer historical ledger versions. Additionally, the Data API v2 acts as data source for applications such as Ripple Charts and ripple.com.

    Ripple provides a live instance of the Data API with as complete a transaction record as possible at the following address:

    https://data.ripple.com

    @@ -5513,54 +5528,61 @@ $ node import/live 
    // get ledgers #1,000,000 to #2,000,000 (inclusive) and store in HBase
 node import/hbase/backfill --startIndex 2000000 --stopIndex 1000000
    -
    -
    -
    +
    +
    +
    + diff --git a/reference-ledger-format.html b/reference-ledger-format.html index beed515048..9e89d80e8c 100644 --- a/reference-ledger-format.html +++ b/reference-ledger-format.html @@ -1,133 +1,148 @@ - - - - -Ledger Format - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    The Ledger

    + + + +
    + +
    +
    +

    The Ledger

    The point of the Ripple software is to maintain a shared, global ledger that is open to all, so that individual participants can trust the integrity of the ledger without having to trust any single institution to manage it. The rippled server software accomplishes this by maintaining a ledger database that can only be updated according to very specific rules. Each instance of rippled maintains a full copy of the ledger, and the peer-to-peer network of rippled servers distributes candidate transactions among themselves. The consensus process determines which transactions get applied to each new version of the ledger. See also: The Consensus Process.

    Diagram: Each ledger is the result of applying transactions to the previous ledger version.

    The shared global ledger is actually a series of individual ledgers, or ledger versions, which rippled keeps in its internal database. Every ledger version has a ledger index which identifies the order in which ledgers occur. Each closed ledger version also has an identifying hash value, which uniquely identifies the contents of that ledger. At any given time, a rippled instance has an in-progress "current" open ledger, plus some number of closed ledgers that have not yet been approved by consensus, and any number of historical ledgers that have been validated by consensus. Only the validated ledgers are certain to be accurate and immutable.

    @@ -1097,54 +1112,61 @@

    When processing a multi-signed transaction, the server dereferences the Account values with respect to the ledger at the time of transaction execution. If the address does not correspond to a funded AccountRoot node, then only the master secret associated with that address can be used to produce a valid signature. If the account does exist in the ledger, then it depends on the state of that account. If the account has a Regular Key configured, the Regular Key can be used. The account's master key can only be used if it is not disabled. A multi-signature cannot be used as a component of another multi-signature.

    SignerLists and Reserves

    A SignerList contributes to its owner's reserve requirement. The SignerList itself counts as two objects, and each member of the list counts as one. As a result, the total owner reserve associated with a SignerList is anywhere from 3 times to 10 times the reserve required by a single trust line (RippleState) or Offer node in the ledger.

    -
    -
    -
    +
    +
    +
    + diff --git a/reference-rippleapi.html b/reference-rippleapi.html index 8d4f751e40..a77f212ebe 100644 --- a/reference-rippleapi.html +++ b/reference-rippleapi.html @@ -1,133 +1,148 @@ - - - - -RippleAPI - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Updated for version 0.16.10

    + + + +
    + +
    +
    +

    Updated for version 0.16.10

    Introduction

    RippleAPI is the official client library to the Ripple Consensus Ledger. Currently, RippleAPI is only available in JavaScript. Using RippleAPI, you can:

    @@ -5309,54 +5324,61 @@ return api.computeLedgerHash(ledger); } }); -
    -
    -
    +
    +
    +
    + diff --git a/reference-rippled.html b/reference-rippled.html index 9e60715aeb..a11bfaa512 100644 --- a/reference-rippled.html +++ b/reference-rippled.html @@ -1,133 +1,148 @@ - - - - -rippled - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    rippled

    + + + +
    + +
    +
    +

    rippled

    The core peer-to-peer server that operates the Ripple Network is called rippled. Each rippled server connects to the Ripple Network, relays cryptographically signed transactions, and maintains a local copy of the complete shared global ledger. The source code for rippled is written in C++, and is available on GitHub under an open-source license.

    -
    -
    -
    +
    +
    +
    + diff --git a/reference-transaction-format.html b/reference-transaction-format.html index 206b7ba4e3..4aea5740df 100644 --- a/reference-transaction-format.html +++ b/reference-transaction-format.html @@ -1,133 +1,148 @@ - - - - -Transaction Format - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Transactions

    + + + +
    + +
    +
    +

    Transactions

    A Transaction is the only way to modify the Ripple Ledger. All transactions have certain fields in common:

    -
    -
    +
    +
    +
    + diff --git a/ripple-api-tool.html b/ripple-api-tool.html index a747aca3f8..93750a0296 100644 --- a/ripple-api-tool.html +++ b/ripple-api-tool.html @@ -1,229 +1,249 @@ - - - - -WebSocket API Tool - Ripple Developer Portal - - - - - - - - - - - + + + + + WebSocket API Tool - Ripple Developer Portal + + + + + + + + + + + + + + + + + + + - -
    - -
    -
    -
    Offline
    -
    -
    -
    -
    -
    -

    WebSocket Request

    - -
    -

    server_info

    -

    -
    Invalid JSON
    -

    JSON

    -
    -
    -
    Send request
    -
    -
    -
    -

    Response

    -
    - -
    -

    -
    -
    -
    -

    Stream output

    -
      -
    • show
      • -
    • pause
      • -
    -

    -
    -
    -
    -
    -
    -
    -
    -
    + + + +
    + +
    +
    +
    Offline
    +
    +
    +
    +
    +
    +

    WebSocket Request

    + +
    +

    server_info

    +

    +
    Invalid JSON
    +

    JSON

    +
    +
    +
    Send request
    +
    +
    +
    +

    Response

    +
    + +
    +

    +
    +
    +
    +

    Stream output

    +
      +
    • show
      • +
    • pause
      • +
    +

    +
    +
    +
    +
    +
    +
    +
    +
    + - - - - - - - + + + + + + + diff --git a/tool-jsonrpc.html b/tool-jsonrpc.html index 442c28d2a8..95065a8b56 100644 --- a/tool-jsonrpc.html +++ b/tool-jsonrpc.html @@ -1,200 +1,222 @@ - - - - -rippled JSON-RPC Tool - Ripple Developer Portal - - - - - - - - - - - + + + + + rippled JSON-RPC Tool - Ripple Developer Portal + + + + + + + + + + + + + + + + + + + - -
    - -
    -
    -
    -
    -
    -
    -
    -

    REST Request

    - -
    -

    -

    -
    Invalid JSON
    -
    -

    http://localhost/rippled

    -
    -
    - -
    -
    -

    Response

    -
    - - -
    -
    -
    -
    -
    -
    -
    -
    - -
    -
    + + + - - - - - - - - + + + + + + + + + + diff --git a/tutorial-gateway-guide.html b/tutorial-gateway-guide.html index f132d1a945..0e037f686a 100644 --- a/tutorial-gateway-guide.html +++ b/tutorial-gateway-guide.html @@ -1,130 +1,145 @@ - - - - -Gateway Guide - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Becoming a Ripple Gateway

    + + + +
    + +
    +
    +

    Becoming a Ripple Gateway

    If you have an existing online financial system, you can expand it to act as a gateway in the the Ripple Consensus Ledger (RCL). Gateways are the businesses that link the Ripple Consensus Ledger to the rest of the world. By becoming a Ripple gateway, existing online financial services, such as payment systems and digital currency exchange, can gain several advantages:

    • By enabling its customers to send and receive value in the Ripple Consensus Ledger, the business increases its value proposition to customers.
      • @@ -687,54 +702,61 @@ Content-Type: application/json

      ripple.txt

      The ripple.txt standard provides a way to publish information about your gateway so that automated tools and applications can read and understand it.

      For example, if you run a validating rippled server, you can use ripple.txt to publish the public key of your validating server. You can also publish information about what currencies your gateway issues, and which Ripple addresses you control, to protect against impostors or confusion.

      -
    -
    -
    +
    +
    +
    + diff --git a/tutorial-multisign.html b/tutorial-multisign.html index 5477428e40..24b0be0706 100644 --- a/tutorial-multisign.html +++ b/tutorial-multisign.html @@ -1,132 +1,147 @@ - - - - -Multi-Signing Transactions - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    How to Multi-Sign

    + + + +
    + +
    +
    +

    How to Multi-Sign

    Multi-signing is one of three ways to authorize transactions for the Ripple Consensus Ledger, alongside signing with regular keys and master keys. You can configure your address to allow any combination of the three methods to authorize transactions.

    Benefits of multi-signing include:

      @@ -662,54 +677,61 @@ Connecting to 127.0.0.1:5005 } } -
    -
    -
    +
    +
    +
    + diff --git a/tutorial-reliable-transaction-submission.html b/tutorial-reliable-transaction-submission.html index 5d528f8201..28447e3c91 100644 --- a/tutorial-reliable-transaction-submission.html +++ b/tutorial-reliable-transaction-submission.html @@ -1,132 +1,147 @@ - - - - -Reliable Transaction Submission - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Reliable Transaction Submission

    + + + +
    + +
    +
    +

    Reliable Transaction Submission

    Gateways and back-end applications should use the best practices described here to ensure that transactions are validated or rejected in a verifiable and timely fashion. You should submit transactions to trusted (locally operated) rippled servers.

    The best practices detailed in this document allow applications to submit transactions to the Ripple network while achieving:

      @@ -515,54 +530,61 @@
    1. Overview of Ripple Ledger Consensus Process
    2. Reaching Consensus in Ripple
      3. -
    -
    -
    +
    +
    +
    + diff --git a/tutorial-rippleapi-beginners-guide.html b/tutorial-rippleapi-beginners-guide.html index fef709893c..42ab71bca3 100644 --- a/tutorial-rippleapi-beginners-guide.html +++ b/tutorial-rippleapi-beginners-guide.html @@ -1,132 +1,147 @@ - - - - -RippleAPI Beginners Guide - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    RippleAPI Beginners Guide

    + + + +
    + +
    +
    +

    RippleAPI Beginners Guide

    This tutorial guides you through the basics of building a simple Ripple-connected application using Node.js and RippleAPI, a simple JavaScript API for accessing the Ripple Consensus Ledger.

    The scripts and configuration files used in this guide are available in the Ripple Dev Portal GitHub Repository.

    Environment Setup

    @@ -460,54 +475,61 @@ npm WARN notsup Not compatible with your operating system or architecture: fseve <body></body> </html> -
    -
    -
    +
    +
    +
    + diff --git a/tutorial-rippled-setup.html b/tutorial-rippled-setup.html index bb8f52b4ac..1bc9679580 100644 --- a/tutorial-rippled-setup.html +++ b/tutorial-rippled-setup.html @@ -1,132 +1,147 @@ - - - - -rippled Setup - Ripple Developer Portal - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - + + + + + + - -
    - -
    -
    -

    Operating rippled Servers

    + + + +
    + +
    +
    +

    Operating rippled Servers

    The core server of the Ripple peer-to-peer network is rippled. Anyone can run their own rippled server that follows the network and keeps a complete copy of the Ripple ledger. You can even have your server perform validations and participate in the consensus process.

    This page contains instructions for:

      @@ -379,54 +394,61 @@ ssdecohJMDPFuUPDkmG1w4objZyp4
    • Add the public keys (for peer communication) of each of your other servers under the [cluster_nodes] section.
    -
    -
    -
    +
    +
    +
    +