Back to Treasurer
Executed
#323 Proof of Concept - Using the Scheduler on the Treasurer Track
Proposer:
HqRc...fVZn
in Democracy
14th Dec '23
(Edited)
Description
AI Summary
Votes Bubble
Timeline
Evaluation
On Chain Info
Stats
Quote
Share
Copy
Dear community,
This referendum seeks to test use of the scheduler on the Treasurer track by scheduling actions through the lifecycle of a bounty i.e. approving, funding, assigning a curator and closing.
It is important to note that after a bounty is approved, it does not become funded until an independent spend period is completed. On Kusama this spend period cycles every 6 days. Only after the bounty is funded then a curator can be assigned, this required delay is the reason why approving a bounty and assigning a curator can not be successfully executed in one batch.
When the bounty is funded and if there is no major objection, I would like to disburse funds to Gch4VxQ79WhjgQqHomvJbqF3Woza5g5cYgM8SVQdDb9szz1
which is used by a public validator payout bot as well as my clean up referendum deposits script for OpenGov and the Fellowship.
Walk through:
Call data - 0x18020c2301681d048051010000ff23026800e8b2603f6baee5bc32a9b9e4eee9168499fa553d35edb56aef0035ff7e1f165e001d0440db020000ff230768
The referendum batches three (3) extrinsics using batchAll, meaning that all three must execute successfully or the overall call would fail and all actions, successful or not would be rolled back. The calls are:
- bounty.approve(26) - This action approves bounty 26 which is the bounty in question with 25 KSM
- schedule.ScheduleAfter - This schedules an action of assigning a curator (myself) after 86,400 blocks. I took the inefficient but risk-free approach of delaying the call to the exact time frame of the spend period i.e. (6 days x 24 hrs x 60 mins x 60 sec)/ blocktime 6s
- schedule.SchedulerAfter - This schedules closing the bounty after 14 days, this gives a 7 day window after assignment of a curator in which the bounty can be claimed (a 4 day wait in itself).
I hope this brief write-up helps others who may wish to avoid using two extrinsics to make use of their bounty. Timings can also be adjusted to reduce the lag after the bounty is funded and curator assigned. If you are using a tighter timeframe, I suggest you use schedule.schedule and target a block_height.
The floor is opened to questions or comments
Regards, Will | Paradox | Builder of extrinsics
Show More
Please Log In to comment
Users are saying...
Based on all comments and repliesOverall 66 % of users are feeling optimistic. This project promises a bright future, potentially revolutionizing bounty establishment through efficient scheduling. Its innovative use of the scheduler is fascinating and could significantly impact its field. The initiator's pioneering efforts are appreciated, with many eagerly anticipating its success.
Overall 33 % of users are feeling neutral. A verified identity on the Kusama network has successfully completed two previous OpenGov TPs and currently does not have any active W3F grants. The individual's contact information includes an email, website, Twitter handle, and a Matrix chat room address. They also registered for Treasury-related proposals in the past but did not specify details about them.
AI-generated from comments
5Comments
0%
0%
40%
40%
20%
JFAr...nYVt
Quote
Share
Copy
Requester address: HqRcfhH8VXMhuCk5JXe28WMgDDuW9MVDVNofe1nnTcefVZn
Verified identity: Yes
When registered/verified: 26 Feb 2021 / 26 Feb 2021
EMAIL: paradoxxx@gmail.com WEBSITE: https://ParaNodes.io TWITTER: @ParaNodes RIOT: @paradoxxx:matrix.org
Previous OpenGov TPs from this account:
* https://kusama.polkassembly.io/referenda/108 (Bounty - passed)
* https://kusama.polkassembly.io/referenda/174 (tip for Polkachu - passed)
* Note: there were several other Treasury-related proposals, such as tests, from this account. I did not include these all here.
W3F Grants: None
GqC3...m8Jj
Voted Aye
Quote
Share
Copy
Fascinating! I didn't think anything other than root could utilize the scheduler. If this works it'll do wonders for establishing bounties with utmost efficiency!
Thank you for pioneering this. I will be closely watching to see if this will work.
Quote
Share
Copy
It's a good project in future 🚀🚀🚀🚀
Quote
Share
Copy
To the moon 🚀🚀🚀🚀
Quote
Share
Copy
It's a good project in future 🚀🚀🚀🚀
Discover similar proposals
#509
E5qF...tqrg
Deciding
KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
Quote
Share
Copy
See More
24th Mar '25
Treasurer
Treasurer
#509 KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
E5qF...tqrg
24th Mar '25
Quote
Share
Copy
This RFP was adapted over several weeks on AAG to turn a treasury proposal in discussion to an RFP with refined scope and oversight.
To apply for the prize pls fill out this form.
Prize Pool: $43,000
Finder’s Fee: $2,000 **
Supervisors: $5,000
Supervisors (Bounty Curators)
- Flipchan
- Byte (Erin)
- James Slusser
Excess or unused funds will be returned to the treasury by Bounty Curators.
Timeline
Monday, March 17 - AAG Discussion & this forum post! ✅
Monday, March 24 - Single-ref Bounty + Curators ✅
4 Weeks after Bounty Funding - Submission Deadline Thursday
July 31 - Project Completion (Pending Kusama Hub Launch)
Project Scope
Smart Contract Development
- A Solidity-based smart contract deployed on Kusama Hub
- ZK enabled for private deposits & withdrawals
- Compatibility with all Kusama Hub assets
User Interface
- Browser-based, mobile-ready UI hosted on IPFS
- Support for: Deposits, Withdrawals, Transfers, XCM Transfers
- Compatible with popular ecosystem wallets (Nova Wallet, Talisman, Subwallet)
Anti-correlation Attack Mitigations:
- Fixed deposit amounts (e.g. 1, 10, 100, 1000 units)
- Batch payouts for withdrawals to multiple users
Interoperability - Ability to receive assets via XCM from any Kusama-connected parachain and transfer them to Kusama Hub for use in shielded pool.
Open-Source Delivery
- All code (smart contracts and UI) published under the MIT license
- Publicly accessible repositories Project updates shared transparently via Polkassembly, Subsquare, or Polkadot Forum from Team with Milestone deliveries
- Developer & User documentation
Milestones
Milestone 1, Initial Pools & Basic UI:
$16,200 USD
1 month
- Tests - Smart contract test
- Smart contract - ZK shielded smart contract with KSM and multi asset support on Westend or Paseo
- Basic UI - A basic UI for interacting with the smart contract
Milestone 2, UI + XCM:
$9,900
1 month
- Tests - tests for all features
- User interface design - UI design
- XCM transfers - XCM transfer assets in UI
- Fixed amount transfer only - Allow fixed amount transfers in the UI
Milestone 3, Mainnet Deployment:
$16,900
1 - 1.5 months
- Contract Migration to Kusama Assethub - Migrate contract from Testnet to Kusama Hub
- Public documentation - Documentation for using Kusama shield and developer integration documentation
- Test - tests for contract
- V1 UI - User tested & something we can be proud of
** re: Finder’s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder’s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder’s Fee at completion of project.
See More
Deciding
#513
E5qF...tqrg
Deciding
KSM RFP #2 - RFP Launcher Dapp - $12k Total Prize!
Quote
Share
Copy
See More
4 days ago
Treasurer
Treasurer
#513 KSM RFP #2 - RFP Launcher Dapp - $12k Total Prize!
E5qF...tqrg
4 days ago
Quote
Share
Copy
This RFP was introduced on AAG to create a simple UI to launch RFPs in the style of ref below.
APPLY NOW - pls fill out this form.
Prize Pool: $10,000
Finder’s Fee: $1,000 **
Supervisors: $1,000
945 KSM Requested (Amount + 25%)
Supervisors (Bounty Curators)
- Leemo
- Jay Chrawnna
- Jose
Excess or unused funds will be returned to the treasury by Bounty Curators.
Timeline
Monday, March 31 - Single-ref Bounty + Curators ✅
2 Weeks after Bounty Funding - Submission Deadline
Saturday, May 31 - Project Completion
Project Scope
Dapp
- Connect popular Substrate wallets to app (Nova Wallet, Talisman, Subwallet)
User Interface
- Browser-based, mobile-ready UI hosted on IPFS
- User Manual
- Present fields for RFP proposes to fill in
- Checks balance for launching Treasurer track referendum & submitting Decision Deposit
Project Scope Fields
-
Funding Fields
-- Prize Pool
-- Finder’s Fee (Fixed 1k, 2k, 5k, 10k)
-- Supervisors’ Fee -
Supervisors (Bounty Curators)
-- Add addresses -
Timeline
-- Funds Expiry (if no submissions after n weeks following bounty funding)
-- Project Completion Deadline -
Project Scope
-- Text field to describe scope -
Milestones
-- Add Milestone Button
-- Text field
-- Amount
-- Check that Milestone amounts = “Prize Pool”
RFP Launcher
- Create multi-sig for Curators
- Create “One-shot” Bounty on Treasurer track with curators and scheduled payment. See example.
- Generate Markdown-ready text for Subsquare/Polkassembly
Open-Source Delivery
- All code published under the MIT license
- Publicly accessible repositories Project updates shared transparently via Polkassembly, Subsquare, or Polkadot Forum from Team with Milestone deliveries
- Developer & User documentation
Milestones
Milestone 1, Basic Dapp & UI:
$3,000 USD
1 week
- Connect Wallet
- RFP Creation Flow
- Total USD converted to KSM + 25%
- Validated by Supervisors
Milestone 2, RFP Creation:
$3,000 USD 1 week
- Chopsticks demonstration of on-chain Treasurer Track ref
- App checks balance for Multi-sig reserve deposit, Ref Launch & Decision Deposit
- Creation Multi-sig
- Scheduler Calculations for filling Bounty
- UI Integration
Milestone 3, Mainnet Deployment:
$4,000 USD 2 weeks
- Improved UI Design
- User Manual included
- Demonstration of RFP launching capabilities
- Documentation
re: Finder’s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder’s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder’s Fee at completion of project.
See More
Deciding
#508
EJgd...JGQZ
Submitted
Remove Gabe from the fellowship
Quote
Share
Copy
Members of the Fellowship Collective involved in projects flagged by the OG tracker should provide a proper explanation, return the funds to the Treasury, or face expulsion.
See More
24th Mar '25
Fellowship Admin
Fellowship Admin
#508 Remove Gabe from the fellowship
EJgd...JGQZ
24th Mar '25
Quote
Share
Copy
Members of the Fellowship Collective involved in projects flagged by the OG tracker should provide a proper explanation, return the funds to the Treasury, or face expulsion.
Invarch failed to provide the first two, so Gabe, a founding member of the team, does not meet the ethical standards required to have a voice in the Fellowship.
TENETS (extract from the fellowship manifesto)
"Members are expected to faithfully uphold the following tenets.
Clarifications to the rules should be in agreement with these tenets. Acting in clear breach of these tenets may be considered by voters as grounds for non-promotion, demotion or, in extreme cases, exclusion from the Fellowship.
(1) Sincerely uphold the interests of Polkadot and avoid actions which clearly work against it.
(2) Respect the philosophy and principles of Polkadot.
(3) Respect the operational procedures, norms and voting conventions of the Fellowship.
(4) Respect your fellow Members and the wider community"
See More
Submitted