Label: Transaction Sending

Pages about sending transactions in the XRP Ledger.

Concepts

  • Accounts Tickets

    Send transactions in non-sequential order.

  • Payment System Basics Transaction Basics

    Transactions are the only way to change the XRP Ledger. Understand what forms they take and how to use them.

  • Transaction Basics Transaction Cost

    The transaction cost is a small amount of XRP destroyed to send a transaction, which protects the ledger from spam. Learn how the transaction cost applies.

  • Transaction Basics Finality of Results

    Learn when the outcome of a transaction is final and immutable.

  • Consensus Network Transaction Queue

    Understand how transactions can be queued before reaching consensus.

  • Consensus Network About Canceling a Transaction

    Understand when and how it's possible to cancel a transaction that has already been sent.

  • Consensus Network Transaction Malleability

    Be aware of ways transactions could be changed to have a different hash than expected.

Tutorials

References

  • Ledger Object Types Ticket

    A Ticket tracks an account sequence number that has been set aside for future use.

  • Transaction Reference Transaction Common Fields

    These common fields can be provided on any XRP Ledger transaction.

  • Transaction Types TicketCreate

    Set aside one or more sequence numbers as Tickets.

  • Transaction Reference Transaction Results

    Learn how to interpret rippled server transaction results.

  • Transaction Results tec Codes

    tec codes indicate that the transaction failed, but it was applied to a ledger to deduct the transaction cost.

  • Transaction Results tef Codes

    tef codes indicate that the transaction failed and was not included in a ledger, but the transaction could have succeeded in some theoretical ledger.

  • Transaction Results tel Codes

    tel codes indicate an error in the local server processing the transaction.

  • Transaction Results tem Codes

    tem codes indicate that the transaction was malformed, and cannot succeed according to the XRP Ledger protocol.

  • Transaction Results ter Codes

    ter codes indicate that the transaction failed, but it could apply successfully in the future, usually if some other hypothetical transaction applies first.

  • Transaction Results tes Success

    tesSUCCESS is the only code that indicates a transaction succeeded.

  • XRP Ledger Protocol Reference Serialization Format

    Conversion between JSON and canonical binary format for XRP Ledger transactions and other objects.

  • Transaction Methods submit

    Send a transaction to the network.

  • Transaction Methods submit_multisigned

    Send a multi-signed transaction to the network.

  • Transaction Methods transaction_entry

    Retrieve info about a transaction from a particular ledger version.

  • Transaction Methods tx

    Retrieve info about a transaction from all the ledgers on hand.

  • Signing Methods sign

    Cryptographically sign a transaction.

  • Signing Methods sign_for

    Contribute to a multi-signature.