

Fields every transaction has
Four fields every transaction carries, and the signature that proves who sent it.
Key points
- Every transaction names its Account, TransactionType, Fee and Sequence.
- The signature proves the account's key holder approved these exact fields.
- Change one field after signing, and the signature no longer fits.
The lesson
A is a signed note asking the ledger to change something. Send XRP, set up a trust line, make an offer: each is a transaction.
Every one carries the same four fields, like the boxes on a form:
- : who sends it.
- TransactionType: what it does, such as
Payment. - Fee: the transaction cost, in drops. The ledger burns it.
- Sequence: the account's next number in line.
Then the sender signs it with their secret key. The signature is like a wax seal. It proves the key holder approved these exact fields. Change one letter, and the seal breaks.
Signing happens on your own device. Only the signed result goes to a server.
Each transaction also gets a hash, a fingerprint of the signed form. Use it to look the transaction up later.
Required on every :
Field Meaning AccountThe sending address TransactionTypeThe action, such as Payment,TrustSet,OfferCreateFeeDrops to burn, as a string. 10 drops for a standard transaction at minimum load SequenceThe account's next sequence number, or 0when a Ticket is usedSigning fields, added when it is signed:
SigningPubKey: the public key that signed.TxnSignature: the signature itself.Signers: used instead for a multi-signed transaction, withSigningPubKeyempty.
Common optional fields:
LastLedgerSequence: the last ledger it may land in. Strongly recommended.Flags: options for this type.Memos: free notes, public forever.SourceTag,DestinationTag: numbers that route a payment inside a shared address.TicketSequence: the Ticket used in place of a .NetworkID: required on networks with an ID above 1024. Mainnet is 0, Testnet 1, Devnet 2.
The transaction's identifying hash is a SHA-512Half of the signed binary. Sign offline or on a device you control; send only the signed blob, never the secret.
Related: Fees and burn, Regular keys and multi-signing.

