02Sheet 02.03.028 · Entries
SAC trust() on an existing trustline succeeds and changes nothing
Calling trust() again for bob, whose trustline exists, succeeds with no ledger change and no event: a reader must not create, duplicate or touch anything.
FIG. · Where it sits · inside LedgerCloseMetaCAP-0073 · H-D1
trust() on an existing trustline: success, no change
The shape
Calling trust() again for bob, whose trustline exists, succeeds with no ledger change and no event: a reader must not create, duplicate or touch anything.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 2,452 B | cebacafdd11d… |
p28-mainnet-generated | P28 | mainnet passphrase | generated by stellar-core v30.0.0 | 2,444 B | 8dfc60282ab0… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 2,452 B | ec9202ae8201… |
p28-testnet-generated | P28 | testnet passphrase | generated by stellar-core v30.0.0 | 2,444 B | 5316b8ad9f82… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The operation changes nothing. | length 0 | snapshot |
| No event is emitted either. | length 0 | snapshot |
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 sac.trust.noop-existing · compiled from catalog/sac.trust.noop-existing.json · entry.json
SAC trustline with no event
A contract call creates a classic trustline: no CHANGE_TRUST operation, no event, only a created ledger entry. Indexers that wait for either miss it.
An XLM SAC transfer creates a G account
Since CAP-0073 the native SAC can transfer to an account that does not exist: the transfer creates it with 25 XLM.