Add a quorum threshold configuration input on the creator dashboard governance settings

[Chucks1093]

Summary

Creators who use governance have no UI to configure the quorum threshold for their proposals. A quorum input on the creator dashboard governance tab should let creators set the minimum participation percentage between 1% and 50% and submit the set_quorum_bps contract call.

Scope

• Add a Quorum Settings section to the governance tab on the creator dashboard
• Show the current quorum percentage fetched from the key detail API (quorumBps)
• Render a percentage slider from 1% to 50% pre-set to the current value
• Display the current value as both a percentage and in basis points below the slider
• Submit via the set_quorum_bps contract function and show a success toast on confirmation

Acceptance Criteria

• Slider pre-set to current quorum value on mount
• Slider constrained between 1% and 50%
• bps value displayed correctly below the slider
• Success toast shown after contract confirmation
• Updated quorum reflected in the slider without a page reload

ETA: 12 hours

---

Coordinate on Telegram

[Tobi-8]

please maintainer, i have the experience to solve this issue, be generous and assign me

[payfoxX]

@payfoxX has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I love to fix this issue, kindly assign it to me. Thanks

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

[DanbabaJr]

@DanbabaJr has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi,
I would love to work on this issue

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

[Muyideen-js]

@Muyideen-js has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I can fix this

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

[Halimatyemisi]

@Halimatyemisi has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, after going through the issue and its requirements, I’m confident I can implement a suitable solution that meets the expected criteria. Kindly consider assigning it to me.

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

[dedukpe]

@dedukpe has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Please assign

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

[samjay8]

@samjay8 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I can fix this

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

[drips-wave]

Congratulations, @DanbabaJr! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@DanbabaJr's PR #906 was approved and merged by @Chucks1093.

🏆 @DanbabaJr: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (35 total points). Track your full progress on GrantFox.

👏 Great work, @DanbabaJr! Keep contributing to accesslayerorg.