Add structured log for ownership read model update after each indexed trade event

[Chucks1093]

Summary

When the indexer updates the ownership read model after a buy or sell, a structured log entry confirms the update happened and shows the balance change, making it easier to trace balance discrepancies without a full database audit.

Scope

• Emit a structured debug log after each ownership update with fields: creator_id, wallet_address (masked), previous_balance, new_balance, event_type (buy or sell), ledger_sequence
• Wallet address masked to first 4 and last 4 characters
• Log emitted only on successful write

Acceptance Criteria

• Debug log emitted after every successful ownership update
• All six fields present with correct values
• Wallet address is masked in all log output
• No log emitted if the write fails (separate error log handles that)

ETA: 12 hours

---

Coordinate on Telegram

[dorisadams]

I would love to work on this issue, please assign the issues to me so i Can work on it ASAP

[Demilade10]

@Demilade10 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Demilade10 to this issue.

[sudo-robi]

@sudo-robi has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer I'm a full stack developer and smart contract developer let me help you resolve this issue and I assure you it will be thoroughly done neatly as I have seen my way around the issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @sudo-robi to this issue.

[Kaycee276]

@Kaycee276 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, can i work on this issue?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Kaycee276 to this issue.

[10xwhoman]

@10xwhoman has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello i would love to work on this.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @10xwhoman to this issue.

[Danto1606]

@Danto1606 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Danto1606 to this issue.

[drips-wave]

Congratulations, @10xwhoman! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @10xwhoman: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🦊 GrantFox — @10xwhoman has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #492)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

This issue has been completed by @10xwhoman as part of the Stellar Wave Program's 6th Wave 🥳

😎 @10xwhoman: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.