Implement Deterministic Pseudo-Randomness Abstraction

[Jagadeeshftw]

Description:

Create a deterministic pseudo-randomness abstraction for use in contracts that require contest winner selection or randomized assignment, ensuring results are verifiable and not manipulable by a single party.

Requirements and context:

• Bounty or contest flows may need random selection
• Full randomness is hard on-chain; need deterministic, seed-based approach
• Design must be verifiable and avoid miner/submitter bias as much as possible
• Component locations:
  • Bounty/program escrow modules that select winners
  • Shared randomness helper

Suggested execution:

1. Fork the repo and create a branch

   git checkout -b feat/deterministic-pseudorandomness-abstraction

2. Implement changes

   • Design randomness source (e.g. hash of known values: block id, escrow id, commit hashes)
   • Provide helper function to derive pseudo-random indices
   • Integrate into at least one contract flow that needs selection
   • Document security trade-offs

3. Test and commit

   • Add tests verifying deterministic outputs for given seeds
   • Include adversarial examples in documentation

Example commit message:

feat: add deterministic pseudo-randomness abstraction for selection flows

Guidelines:

• Assignment required before starting
• PR description must include: Closes #[issue_id]

[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

[Chucks1093]

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

I am capable of implementing the issue immediately. I will make sure I follow updates on my PR till its merged.

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

[drips-wave]

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

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

[drips-wave]

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

Moderator's reason: Issue was resolved and merged in PR: #693

😎 @Chucks1093: 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.