[Mike] 74. Standard memo convention for escrow ops

[mikewheeleer]

Implement Standard memo convention for escrow ops

Description

Convention for operation memos to aid block explorers and support.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Repository scope: Talenttrust/Talenttrust-Contracts only
• Keep implementation aligned with existing project architecture and coding standards

Suggested execution

• Fork the repo and create a branch
• git checkout -b feature/contracts-74-standard-memo-convention-for-escrow-ops
• Implement changes
  • Write code in: contracts/escrow/src/lib.rs and related modules as needed
  • Write comprehensive tests: contracts/escrow/src/test.rs plus new focused test modules
  • Add documentation: README.md and docs/escrow/ as appropriate for this change
  • Include NatSpec-style comments where applicable (or equivalent structured doc comments)
  • Validate security assumptions and threat scenarios

Test and commit

• Run tests (cargo test)
• Cover edge cases and failure paths
• Include test output and security notes in the pull request description

Example commit message

feat: implement standard memo convention for escrow ops with tests and docs

Guidelines

• Target minimum 95% test coverage for impacted modules
• Clear documentation with reviewer-focused structure
• Timeframe: 96 hours

[Risktaker001]

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

Hi. I would love to work on this issue

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

[Ryjen1]

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

Kindly assign

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