Event payload: include amounts only where non-indexable needed

[1nonlypiece]

Description

Review payload sizes vs Soroban event limits; minimize redundant data.

Requirements and context

• Tests assert event emission

• Must be secure, tested, and documented

• Must be secure, fully tested, and documented

• Should be efficient and easy to review for auditors and integrators

Suggested execution

1. Fork the repository and create a branch: git checkout -b feature/event-payload-audit
2. Implement the changes listed below
3. Open a draft PR early for design feedback

Implement

• Implement or document per issue scope
• Add tests where behavior is normative

Tests and documentation

• Add or extend automated tests: src/lib.rs, tests/create_vault.rs
• Add or update documentation: vesting.md or README.md
• Add Rustdoc (///) on public contract APIs where applicable (NatSpec-style)
• Validate stated security assumptions explicitly in PR description

Test and commit

1. Run the full contract test suite (e.g. cargo test, Soroban local sandbox if applicable)
2. Cover edge cases called out in this issue
3. Attach test output summary and short security notes in the PR
4. Ensure minimum 95% line coverage for touched modules (cargo tarpaulin / project standard)

Example commit message

chore(soroban): feature event-payload-audit

Guidelines

Item	Target
Test coverage	≥ 95% on changed code
Documentation	Clear, versioned, matches on-chain behavior
Timeframe	96 hours from assignment

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[OnyemaAnthony]

@OnyemaAnthony has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

maintainer please assign me

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

[drips-wave]

@1nonlypiece OnyemaAnthony could not be assigned to this issue because they have reached the maximum of 4 accepted assignments per organization in the current wave of the Stellar Wave Program.

The assignee has been removed. Please choose a different contributor.

[drips-wave]

@1nonlypiece OnyemaAnthony could not be assigned to this issue because they have reached the maximum of 4 accepted assignments per organization in the current wave of the Stellar Wave Program.

The assignee has been removed. Please choose a different contributor.

[Joeltabe]

@Joeltabe has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi Maintainer,
Can I work on this issue

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

[githoboman]

@githoboman has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

hello let me clear all issue before deadline

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