Repository navigation
Describe callora-admin limits scope and consumers #1248
Description
Summary
The callora-admin crate ships per-account caps for bets, positions and subscriptions, concepts absent from the API-marketplace contracts, and no contract depends on it.
Why this matters
Readers cannot tell whether these limits protect real Callora flows or are copied scaffolding, making audit scoping harder.
Scope
Document which contracts are meant to consume callora-admin, what 'bet' and 'position' mean in Callora terms, or mark the module experimental.
Relevant code in CalloraOrg/Callora-Contracts:
contracts/admin/src/limits.rscontracts/admin/docs/storage.mdcontracts/admin/docs/PR_IMPLEMENTATION_SUMMARY.md
Priority
Low
Acceptance criteria
- Crate-level docs state purpose and consumers
- storage.md lists all keys used by limits.rs
- Unused concepts either justified or flagged
- Doc explains relation to
contracts/yieldlimits which duplicate the concept
Validation
cargo doc -p callora-admin --no-deps
Non-goals
- Typo-only, formatting-only, or cosmetic changes.
- Unrelated refactors, dependency upgrades, or broad rewrites.
- Removing safeguards or weakening validation to make tests pass.
Contributor application
Before coding, describe the affected modules, proposed state/invariant changes, test strategy, compatibility considerations, and an estimate. Wait for assignment before starting implementation.
PR requirements
Use a feature branch and include Closes #<issue-number>. Address every criterion, map criteria to code and tests, explain security and failure-mode handling, and ensure CI passes.
Quality review
A maintainer will assess correctness, completeness, test depth, compatibility, observability, and adverse-case handling. A substantive implementation is required; merge or CI status alone does not guarantee reward eligibility.
Generated by Claude Code
Activity
[-]Keep leaderboard rank pages deterministic[/-][+]Add focused test coverage for contracts/topics/src/events.rs[/+][-]Add focused test coverage for contracts/topics/src/events.rs[/-][+]Describe callora-admin limits scope and consumers[/+]olaams-tech commentedon Sep 27, 2026
@olaams-tech has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @olaams-tech to this issue.
drips-wave commentedon Sep 29, 2026
Congratulations, @olaams-tech! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @olaams-tech: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
docs(admin): state limits.rs purpose, consumers and yield duplication (…
grantfox-oss commentedon Sep 29, 2026
🎉 This issue has been marked as completed on GrantFox!
@olaams-tech's PR #1295 was approved and merged by @greatest0fallt1me.
🏆 @olaams-tech: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (331 total points). Track your full progress on GrantFox.
👏 Great work, @olaams-tech! Keep contributing to CalloraOrg.
drips-wave commentedon Sep 29, 2026
This issue has been completed by @olaams-tech as part of the Stellar Wave Program's 9th Wave 🥳
😎 @olaams-tech: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
13 remaining items
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…
docs(admin): state limits.rs purpose, consumers and yield duplication (…