Every account object in the XRP Ledger has a Sequence number, which starts at 1.

server side form validating numbers asp-3server side form validating numbers asp-49server side form validating numbers asp-27

Different types of objects are uniquely identified in different ways: Accounts are identified by their Address, for example methods also accept a hexadecimal representation.

Transactions are identified by a Hash of the transaction's binary format.

Caution: If the request contained any account secrets, they are copied here!

Note: The request is re-formatted in Web Socket format, regardless of the request made.

The response format for commandline methods is the same as JSON-RPC responses, because they use the same interface.

It is impossible to list all the possible ways an error can occur.

If you are looking to try out some methods on the XRP Ledger, you can skip writing your own Web Socket code and go straight to using the API at the Ripple Web Socket API Tool. If you plan on making multiple requests, use Keep-Alives so that you do not have to close and re-open the connection in between requests.

Send request body as a JSON object with the following attributes: server or contract someone you trust to do so.

Many objects in the XRP Ledger, particularly transactions and ledgers, are uniquely identified by a 256-bit hash value.