02Sheet 02.03.108 · Entries
BUMP_SEQUENCE jumps the sequence number by 1001
BUMP_SEQUENCE sets the source sequence far ahead; the next transaction must use bumpTo + 1.
FIG. · Where it sits · inside LedgerCloseMetaCAP-0001 · H-C11
BumpSequenceOp
The shape
BUMP_SEQUENCE sets the source sequence far ahead; the next transaction must use bumpTo + 1.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 3,064 B | b47bf0366d98… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 3,064 B | 10b6de8980ed… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| Operation 0 succeeds. | success | snapshotcorewalker |
| alice's sequence number becomes bumpTo. | some change where 1 fields match | snapshotcorewalker |
Check it yourself
make verify # schema, hashes, the byte-for-byte round trip and every fact above
make oracle # the facts' values, re-read by stellar-core and the schema walkerEntry id sequence.bump · compiled from catalog/sequence.bump.json · entry.json
Preconditions v2 with ledger bounds, min sequence and an extra signed-payload signer
CAP-0021 preconditions: ledger bounds, a minimum source sequence, and an extra signer that is a signed-payload key (P…) whose signature must be on the transaction.
MEMO_HASH mapped to to_muxed_id bytes
CAP-0067 renders MEMO_HASH in the transfer event as bytes, indistinguishable from MEMO_RETURN.