Add remaining state changes

[aditya1702]

What

• Add following state changes:

Balance Authorization

We generate a set of balance authorization state changes in different cases:

• SetTrustlineFlags operation: When trustline flags are updated, we generate state changes with category BALANCE_AUTHORIZATION and reason being SET/REMOVE based on the flags that are set and cleared.
• SAC contract events for set_authorized calls: We generate 2 state changes in this case
  • set_authorized = true: Two changes are generated with category BALANCE_AUTHORIZATION and a SET reason for authorized_flag and REMOVE reason for authorized_to_maintain_liabilities.
  • set_authorized = false: Two changes are generated with category BALANCE_AUTHORIZATION and a SET reason for authorized_to_maintain_liabilities and REMOVE reason for authorized_flag.

Change Trustline

Changes to trustlines generate state changes for the account involved. We use the effects processor to build these changes. There are 3 types of changes that are generated:

• ADD
  We record the account and asset and the trustline limit is added to a new colume trustline_limit which is a key-value JSONB string:

{
    limit: {
       new: value
    }
}

Additionally we also generate a BALANCE_AUTHORIZATION change by getting the default trustline flags that the issuer has set.

• REMOVE
  We only record the amount and asset since the limit is 0 when the trustlines are removed.
• UPDATE
  We record the account and asset and the trustline limit with old and new values::

{
    limit: {
        old: value
        new: value
    }
}

Why

Wallet backend indexer

Known limitations

N/A

Issue that this PR addresses

#310 #314 #315

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	github.com/​stellar/​go@​v0.0.0-20250822224526-9397ce4b6da2 ⏵ v0.0.0-20250903085211-00c0b06cd7cc	+1

View full report

[JakeUrban]

This looks like its almost there but I had some questions we should resolve before merging.

Also, I realized through reviewing this PR that SEP-41 doesn't have the set_authorized event -- I thought it did. This means we can't track authorization status for contract tokens, because the implementation is nonstandard and we wouldn't know how to parse it.

I still think its worth having separate state change categories for trustlines and balance authorizations though, because contract accounts can hold stellar assets, and contract accounts don't have trustlines but can be authorized/deauthorized.

[aditya1702]

This looks like its almost there but I had some questions we should resolve before merging.

Also, I realized through reviewing this PR that SEP-41 doesn't have the set_authorized event -- I thought it did. This means we can't track authorization status for contract tokens, because the implementation is nonstandard and we wouldn't know how to parse it.

I still think its worth having separate state change categories for trustlines and balance authorizations though, because contract accounts can hold stellar assets, and contract accounts don't have trustlines but can be authorized/deauthorized.

@JakeUrban I agree with you. It was a good idea to remove the trustline flags state change and combine it with balance authorization since that also helps us include the contract events for set_authorized.