[Hard] Add credential performance benchmarks

[Josie123-Dev]

Task Description

Create credential contract performance benchmarks:

• Measure gas costs
• Benchmark execution time
• Test with high load
• Optimize bottlenecks
• Document performance

Requirements

• Gas measurement
• Time benchmarking
• Load testing
• Optimization
• Documentation

Acceptance Criteria

• Gas is measured
• Time is benchmarked
• Load is tested
• Bottlenecks are optimized
• Performance is documented

[nanlebenthel-web]

Benchmarking is one of those tasks where the methodology decides whether the numbers mean anything, and that's exactly why I'd like to take this on. I work across smart contract platforms, both Soroban/Rust and Solidity/EVM with Foundry, so I'm comfortable with the performance tooling on either side.

First thing I'd pin down is the credential contract's platform, because it sets the whole approach. If it's Soroban, the real cost model is the host budget, CPU instructions and memory plus the resource fees, measured through the cli rather than an EVM-style gas number. If it's a Foundry/Solidity contract, it's forge snapshot and the gas report per function. I'd confirm that before writing the harness so the numbers map to the actual on-chain cost rather than a proxy.

The discipline I'd hold to: establish a reproducible baseline before touching anything. Pinned toolchain, fixed inputs, repeated runs, and I'd report per-entry-point cost for the credential operations (issue, verify, revoke and so on) rather than one aggregate figure, since the bottlenecks hide at the operation level. I'd also keep on-chain gas/resource cost, which is deterministic, separate from wall-clock execution time, which is noisy and needs warmup and percentiles to be honest.

For load, the question I care about isn't just throughput, it's how cost scales: does verifying against a growing credential set stay flat, grow linearly, or go superlinear as state grows? That scaling curve is usually where credential contracts actually hurt. Only once the baseline shows real bottlenecks would I optimize, targeting the hot paths and proving each change with a before/after delta rather than asserting it got faster. I'd land it as a checked-in, re-runnable benchmark harness plus a results doc that records the methodology, and ideally a gas/resource snapshot in CI so regressions get caught later.

This is the hard track and the issue is light on specifics, so I'd be glad to confirm the platform and scope the harness with you before I start.

[grantfox-oss]

🦊 GrantFox — @nanlebenthel-web has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #100)
2. Your PR will be reviewed by the GuardZero144 maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@nanlebenthel-web's PR #111 was approved and merged by @Josie123-Dev.

🏆 @nanlebenthel-web: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (153 total points). Track your full progress on GrantFox.

👏 Great work, @nanlebenthel-web! Keep contributing to GuardZero144.