You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Remove the 'stub' contract ID and synthetic proposal IDs from POST /treasury/propose #654
Branch: Open your PR against dev. PRs targeting main are closed automatically.
Description: POST /treasury/propose stores contractId: process.env.GROUP_TREASURY_CONTRACT_ID ?? 'stub' and proposalId: `prop-${Date.now()}` , so the database rows cannot be matched to on-chain proposals. Require the contract ID from config and accept the on-chain proposal ID from the client, which gets it from propose_withdraw.
Acceptance criteria:
GROUP_TREASURY_CONTRACT_ID is added to the config schema; the route never writes 'stub'
The request body accepts the on-chain proposalId (validated as a non-negative integer string), and the route stores it
@Stanley-Owoh has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
Good day maintaner, please i would like to work on this, I have gone through the description and am sure i can handle this task
I can work on it immediatly with clean code and positive result please assign this issue to me
Thank you
Congratulations, @bandanadivya! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @bandanadivya: 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.
😎 @bandanadivya: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.
Activity
ayandipe commentedon Oct 22, 2026
@ayandipe 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 @ayandipe to this issue.
Tonychris127 commentedon Oct 22, 2026
@Tonychris127 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 @Tonychris127 to this issue.
Starlitecrypto commentedon Oct 22, 2026
@Starlitecrypto 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 @Starlitecrypto to this issue.
shotundeibrahimoluwaseyifunmi-ship-it commentedon Oct 22, 2026
@shotundeibrahimoluwaseyifunmi-ship-it 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 @shotundeibrahimoluwaseyifunmi-ship-it to this issue.
fablo12 commentedon Oct 22, 2026
@fablo12 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 @fablo12 to this issue.
Wumi65 commentedon Oct 22, 2026
@Wumi65 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 @Wumi65 to this issue.
bandanadivya commentedon Oct 22, 2026
@bandanadivya 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 @bandanadivya to this issue.
Stanley-Owoh commentedon Oct 22, 2026
@Stanley-Owoh 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 @Stanley-Owoh to this issue.
Temibell commentedon Oct 22, 2026
@Temibell 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 @Temibell to this issue.
drips-wave commentedon Oct 22, 2026
Congratulations, @bandanadivya! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @bandanadivya: 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 🌊
github-actions commentedon Oct 22, 2026
Closed by #686, merged into
dev.drips-wave commentedon Oct 22, 2026
This issue has been completed by @bandanadivya as part of the Stellar Wave Program's 10th Wave 🥳
😎 @bandanadivya: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.