Implement Investor KYC and Investment Limits

[Baskarayelu]

Description
Implement investor KYC submission, admin verify/reject, investment limits, and limit enforcement on place_bid.

Requirements and context

• Must be secure, tested, and documented
• Bids must not exceed investor limit
• Smart contracts only (Soroban/Rust)

Suggested execution

1. Fork the repo and create a branch
   git checkout -b feature/investor-kyc-limits
2. Implement changes
   • Implement: src/verification.rs (investor KYC, limits)
   • Add tests: src/test_investor_kyc.rs, src/test_limit.rs
   • Document in docs/contracts/verification.md
3. Test and commit
   • Run cargo test
   • Cover limit boundary, unverified/rejected bid rejection
   • Include test output and security notes

Example commit message
feat: implement investor KYC and investment limits with tests and docs

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Cyberking99]

@Cyberking99 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello,

I’m a smart contract and full-stack developer interested in contributing to this issue. I am experienced with hands-on experience in Rust, Soroban, Cairo, Solidity, and TypeScript.

I am passionate about building secure and scalable blockchain solutions, with a strong focus on writing clean, maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I would appreciate the opportunity to contribute and help move this forward.

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

[drips-wave]

Congratulations, @Cyberking99! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Cyberking99: 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 issued 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 🌊

[Cyberking99]

Hello @Baskarayelu , PR #464 has been merged but this issue hasn't been closed.
Please can you help close it as completed? 🙏

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Cyberking99 as part of the Stellar Wave Program's 2nd Wave 🥳

Moderator's reason: All work was completed and merged in PR: #464

😎 @Cyberking99: You earned 200 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.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.