SC-W8-14: Per-Entrypoint Resource Budget Assertions

[Cedarich]

Labels: Soroban, Stellar Wave, contract, gas, performance
Complexity: Medium (150)

Description
A benchmark gate landed in an earlier wave, but budgets are aggregate. A regression in one entrypoint can hide beneath overall headroom, and an entrypoint that quietly grows past the transaction budget only fails on-chain.

Acceptance Criteria

• Each public entrypoint has a recorded CPU and memory budget.
• Tests fail when an entrypoint exceeds its budget beyond a documented tolerance.
• Budget changes require an explicit, reviewable update rather than passing silently.
• The report names the entrypoint and the delta on failure.

[Kingsilva36]

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

I would love to work on this professionally, please assign it to me

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

[eliJah790]

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

I would like to work on this

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

[fatimat252525-commits]

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

Pls boss I'll like to work on this issue I've reviewed the issue

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

[testimonyblockchain]

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

I’d like to work on this issue. I have experience with Solidity and Foundry, including writing tests and working with smart-contract resource constraints. I’ll implement the per-entrypoint budget assertions, add the necessary tests, and verify everything with the existing test suite.

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

[Chrisland58]

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

hi maintainer i will like to work ont his issue please

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

[Andy8370]

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

Hello, this issue caught my interest, and after reviewing the requirements, I believe I can make the necessary changes. Please consider assigning it to me.

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

[sunnykid-02]

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

I’d like to work on this issue because enforcing per-entrypoint resource budget assertions is important for keeping smart contract execution predictable, efficient, and resistant to resource exhaustion. Explicit limits can help detect regressions early and ensure individual entrypoints remain within the project’s expected compute and storage budgets.

I have experience working with smart contracts, automated testing, and performance-sensitive backend systems.

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

[0xApana]

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

Hi, maintainer i'll like to work on this.

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