No resource-cost benchmark comparing release vs refund paths

[yusuftomilola]

Soroban charges based on resource consumption; there's no benchmark documenting the relative CPU/memory cost of release() vs refund() on payment_escrow, which would help the backend estimate fees. Add a simple benchmark harness.

[guptakumarranjeet150]

Hello team,

I can tackle No resource-cost benchmark comparing release vs refund paths. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in DistinctCodes/ManageHub
• Core Implementation: Deliver a clean, well-tested implementation for No resource-cost benchmark comparing release vs refund paths following DistinctCodes/ManageHub conventions.
• Quality Assurance: Validate end-to-end functionality before submitting the PR.

I am ready to start immediately—please feel free to assign this to me!

[guptakumarranjeet150]

Hi there,

I can tackle No resource-cost benchmark comparing release vs refund paths. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in DistinctCodes/ManageHub
• Core Implementation: Deliver a clean, well-tested implementation for No resource-cost benchmark comparing release vs refund paths following DistinctCodes/ManageHub conventions.
• Quality Assurance: Include automated test coverage verifying the implementation meets expected requirements.

Excited to work on this—please assign to me and I will submit a clean PR shortly!

[Douglas366]

📋 Grainlify Application

@Douglas366 has applied to work on this issue as part of the Grainlify program.

Hello Maintainers,
I’m experienced in frontend, backend, and Web3 development. I’m interested in contributing to this project and would be happy to help improve its existing functionality.

---

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