Repository navigation
feat(contracts): Implement configurable campaign participation fee in custom tokens #1371
Description
🎯 Problem Statement & Impact
Allow campaigns to charge a small token entry fee that gets added to the reward pool.
Directly improves smart contract safety, multi-asset security, and state persistence on Soroban.
🏗️ Technical Architecture & Affected Components
- Primary Component:
contracts/ (Soroban Rust Smart Contracts) - Integration Points: Ensures full backward compatibility across Soroban contracts, client SDKs, and backend services.
- Resource Management: Optimized memory utilization, efficient state storage keys, and extend_ttl rent management where applicable.
💻 Code Changes & Implementation Steps
- Refactor key modules in
contracts/ (Soroban Rust Smart Contracts)to fulfill standard code structure guidelines. - Implement explicit validation, error boundaries, and defensive checks.
- Export clean TypeScript bindings or standard Rust/JS interfaces.
- Verify end-to-end compatibility across all environment tiers (local testnet & mainnet).
🧪 Test Strategy & Verification Criteria
- Unit tests cover all primary control branches and edge cases cleanly.
- Integration tests verify contract/API boundaries without memory or balance leaks.
- Automated CI check passes clean linting, formatting, and security audits.
📈 Contribution to Project & Team Growth
Directly enhances platform scalability, user conversion, developer experience, or financial safety across the ecosystem.
Activity
frammawiliansyah commentedon Sep 30, 2026
PR #1406 opened addressing this requirement with Soroban unit tests for custom token participation fees.
Reference: #1406
Ranjeet2063 commentedon Oct 5, 2026
Hi maintainers,
I reviewed this issue and would like to contribute the fix.
Solution overview:
I can deliver a clean, tested PR within 24 hours. Please assign!
AbelOsaretin commentedon Oct 20, 2026
@AbelOsaretin has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @AbelOsaretin to this issue.
drips-wave commentedon Oct 20, 2026
Congratulations, @AbelOsaretin! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @AbelOsaretin: 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 🌊