Reduce the ledger storage footprint of admin_accrue_yield

[francisdouglas-ux]

Problem & Goal

Consolidate the storage keys read and written inside the body of admin_accrue_yield so a single invocation touches fewer ledger entries.

Context & Components

• Target Repository: escrow-contract
• Module/Component: admin_accrue_yield (Accrues interest into the stored yield total)

Implementation Details

1. Review the existing codebase inside the escrow-contract directory.
2. Locate the source files relating to admin_accrue_yield.
3. Implement the feature logic/validation rules step-by-step.
4. Ensure code conforms to codebase patterns (lints, formats, types).

Verification & Testing Requirements

• Validation check: Assert every existing test still passes unchanged while the number of distinct storage keys written by the call is reduced.
• Add comprehensive test cases matching these validation requirements.
• Ensure all other existing project tests continue to compile and pass.

---

Note: This issue is completely self-contained and does not block or require any other issues to be resolved.

[Meet-hybrid]

@Meet-hybrid has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Can I work on this please?

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

[divinemike019]

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

Hi! I'd like to contribute to this issue.

I have experience developing Rust/Soroban smart contracts with ledger storage optimization, state management, and test-driven refactoring. I'll inspect admin_accrue_yield and consolidate its storage reads/writes so a single invocation touches fewer distinct ledger entries while preserving the existing yield accrual behavior and validation rules.

I'll follow the contract's existing storage patterns, add focused tests that verify the optimized path produces the same state and results, and specifically validate that the number of distinct storage keys written is reduced. I'll also run the complete existing test suite and formatting/lint checks to ensure the optimization introduces no regressions.

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

[qa-eden]

@qa-eden has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer, I would work on this

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

[DevFaster]

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

hi repo maintainer. please assign me this issue . i will fix this issue correctly.

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

[onyemaechiezekiel9]

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

Hello boss, I've gone through the issue description and i'd love to work on this issue, kindly assign me

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