Welcome to our Collective FAQ thread! We’ve compiled answers to the most common questions about our grant program, voting system, and proposal process. If you don’t see your question answered here, please post it in the comments, and our team will make sure to answer it and potentially add it to this resource.
Q: Does the grant amount need to match the suggested tiers on the guidelines exactly?
A: No, the tiers are guidelines. You should request the amount that makes sense for your project’s scope, with clear justification for the requested funds.
Q: Can established projects apply for smaller grants?
A: Yes! We encourage established projects to apply for appropriately sized grants based on the specific integration or feature scope.
Q: Who verifies my milestone completion?
A: Milestone verification is handled by our community and delegates who review deliverables against your proposal’s stated objectives. For technical milestones, this may include code review, testing, or deployment verification.
Q: What happens if I miss a milestone deadline?
A: Communicate proactively about any delays. The community understands that development timelines can shift. Significant or unexplained delays may require a new proposal for remaining milestones.
Q: I’ve created a proposal off-chain, can I request changes to it after submission?
A: Minor clarifications can be added in comments, but we advise with substantial changes to withdraw and resubmit your proposal. We recommend thorough community discussion before formal submission on-chain. The dApp or on-chain proposal can not be edited once submitted.
Q: How detailed should my milestone breakdowns be?
A: Milestones should be specific, measurable, and tied to clear deliverables. Include technical details, expected timelines, and how you’ll demonstrate completion. The more specific, the easier verification will be.
Q: Is there a recommended format for proposals?
A: Yes, please follow the template provided in our Grant Guidelines V3.1. This ensures all necessary information is included and makes review more efficient.
Q: Can I use AI tools to help write my proposal?
A: We encourage using AI for correcting typos or improving narrative flow, but excessive AI-generated content that lacks authentic project voice or specific technical details will be flagged during review. The strongest proposals demonstrate genuine team expertise.
Q: Are U.S.-based projects eligible?
A: Currently, we cannot accept applications from U.S.-based companies or projects with U.S.-based Ultimate Beneficial Owners (UBOs).
Q: How many votes do I need for my proposal to pass?
A: Your proposal needs to satisfy two conditions:
Reach quorum - A minimum percentage of total stRIF supply must participate in the vote. Importantly, only YES and ABSTAIN votes count toward reaching quorum. This measures the level of participation in the vote.
Exceed support threshold - Once quorum is reached, the proposal passes if YES votes surpass the support threshold (typically set at 50%). ABSTAIN votes are disregarded when determining whether a proposal succeeds or not.
The specific quorum percentage is viewable on each proposal page. Remember that vote weight is based on stRIF holdings, not simply the number of voters.
As stated in our whitepaper: “Quorum computations take both YES and ABSTAIN votes into account. Once the quorum requirement is satisfied, the ultimate outcome of a vote is based on whether the YES votes surpass a Support threshold. ABSTAIN votes are disregarded and do not matter when determining whether a proposal succeeds or not.”
The specific quorum percentage is viewable on each proposal page.
Q: How long does the voting process take?
A: The voting period lasts 7 days. After a successful vote, there’s an additional 3-day timelock period before execution. This means from proposal submission to fund disbursement takes a minimum of 10 days, assuming immediate execution.
Q: What happens after my proposal passes the vote?
A: After the 7-day voting period:
If approved, your proposal enters a 3-day timelock queue
After the timelock, anyone can execute the proposal (usually our team or a community member)
Once executed, funds for your first milestone will be transferred to the chosen wallet (the one assigned by the user on the proposal wallet field).
Subsequent milestone funding requires verification of deliverables.
Q: Can I resubmit if my proposal doesn’t pass?
A: Absolutely! We encourage you to:
Gather feedback from community discussions
Address concerns raised during voting
Consider adjusting milestone structure or funding amounts
Resubmit with improvements clearly highlighted
Many successful projects passed on their second submission after incorporating community feedback.
Other
Q: What options do builders have for accessing or extracting data from Rootstock?
A: Builders can access Rootstock data through several methods:
Footprint Analytics - Our preferred analytics partner with pre-built dashboards
Direct RPC Node Queries - For custom data extraction needs
RSK Explorer API - For basic transaction and block data
TheGraph Subgraphs - Some protocols have deployed subgraphs for indexed data
We’re currently developing more comprehensive documentation for builders on data extraction methods.
Have doubts on Development? Check the official Rootstock Developer Portal: https://dev.rootstock.io/
Have a question that’s not covered here? Drop it in the comments below, and our team will provide an answer! We’re constantly updating this FAQ based on community inquiries to make the grant process as transparent and accessible as possible.
More about the Collective here:
Website:
dApp: