Thanks for the concerns and reservations,I believe they are all geared towards good and efficiency and accountable operations of our program,will get a consolidated updates for all the issues raised soon . Appreciate your feedbacks once again!
1 Like
Update and clarificationâ Rootstock Community Ghana
Hello. esteemed community!I would like to briefly update you on our proposal :Rootstock Community Ghana, and clarify a few points. I took some time over the past few days to check certain details with our local partners who helped us out during our previous meetup series, especially about transactions and logistical arrangements. We needed to take this step to make sure that the information we give to the community is accurate and documented correctly. Regarding the use of AI tools, we would like to clarify that they were only used to refine grammar and improve the clarity of our written communication. Our activitiesâ concepts, plans, and execution remain entirely ours. We have included the following materials in our update to increase transparency and provide a clearer picture of our progress thus far: A KPI table that shows our progress and milestone goals. A reconciliation of the budget that explains how the funds were used. The presentation of the technical guide that was used in our developer sessions . While developing a Rootstock ecosystem that is long-lasting in Ghana, our intention is to maintain openness and accountability to the community. The response and interest from the local community have been encouraging, despite our modest beginnings. The Rootstock ecosystem has been introduced to developers and enthusiasts through these early engagements, laying the groundwork for a growing community. We are steadfastly devoted to the goal of establishing a thriving Rootstock developer and user community in Ghana that will eventually help spread Rootstock adoption throughout Africa. We appreciate the communityâs continued support, guidance, and constructive feedback as we refine our approach and strengthen our activities.
Attached in this are the details of our KPI table,and target with the outcomes,budget reconciliation and a technical presentation on Rootstock our inhouse facilitator used .
We look forward to continuing the next phase of building Rootstock Community Ghana with clearer metrics, stronger engagement, and deeper collaboration with the ecosystem.
Thank you.
2 Likes
We appreciate the effort reflected in your updated PDF, particularly the improved clarity around budget usage. However, as @Kaf_Anode and @DAOstar_gov mentioned earlier, we still need further clarification on the KPI delivery, as it remains unclear. After reviewing your update, it does not appear to meet the originally promised targets.
So we would need more clarity on the proof of onboarding, as well as the reason why the educational posts were moved to the bootcamp phase, as raised in the questions below.
First, regarding onboarding â in your consolidated update, you mentioned achieving 60+ members. However, based on the two Luma event pages you shared, the combined registrations are around 67, which is still below the 150+ onboarding target.
That said, registration does not equal attendance, and attendance does not necessarily mean successful onboarding. Do you have a community channel (e.g., Telegram/Discord) where we can verify these onboarded members?
Second, we would like to understand the decision to move the 5 educational posts to the bootcamp phase. Based on the original plan, this was expected to be part of Milestone 1 delivery. Could you clarify the reasoning behind this change?
Lastly, we couldnât access the technical presentation file, so weâre not able to review the materials used to train the 30 users. Could you share a working link so we can take a proper look?
1 Like
Thank you for the detailed assessment and for recognizing the improvements in our updated submission. We appreciate the feedback and the opportunity to clarify key areas.
In terms of KPI delivery, we are aware that some of our initial goals, particularly the 150+ onboarding goal, were not entirely met. On hindsight, this was an overestimation for a first-phase activation within our local context. Our approach has instead prioritized organic growth and meaningful engagement, which we believe will result in stronger long-term retention and ecosystem participation.
We concur that registrations do not equate to successful onboarding when it comes to onboarding verification. Although there are approximately 67 registrations on the Luma pages, our primary goal has been to get join our activities and community .
On the educational posts, the shift to the bootcamp phase was intentional. Rather than early-stage, top-down content delivery, we chose to enable participants to create and share educational content themselves. This makes it possible for learning to be more experiential and practical, to increase engagement, and to spread across networks in a more genuine way. Even though this takes longer than the original timetable, we believe it will produce better results. We also believe that access to a more structured activity guide or presentation template from the Rootstock Collective would significantly improve our subsequent training sessions. Better alignment, consistency, and overall delivery quality would be made possible by this. Finally, we acknowledge the issue with the technical presentation link and will provide a working version for proper review.
Overall, Milestone 1 has provided useful insights that position us to deliver a more structured and measurable impact in the subsequent phase, despite the fact that some of its goals were not met. We are grateful for your ongoing support and remain committed to enhancing reporting and execution,as we take steps for our upcoming Bootcamping. â
Sorry the file for our technical guide was not complete,was due to uploading challenges.Please the uploaded link is herehttps://docs.google.com/presentation/d/1sXRGIDkyrl9F5bAe9AFtJNH51Ubkq6ZM/edit?usp=drivesdk&ouid=107881682257471987149&rtpof=true&sd=true
Please access opened for the technical guide.
Overall, weâre not fully satisfied with the work and delivery from the team so far. You mentioned that you
However, this remains a statement without supporting evidence. How do you expect ~67 people across your events to convert into active community members? At the moment, we only see proof of attendance, but not retention.
Regarding your approach of enabling participants to create and share educational content themselves. How do you ensure participants are effectively guided and supported? And what role does the team play in facilitating this process?
At this stage, we do not see a strong level of professionalism in execution, nor clear evidence of meaningful value being created for the Rootstock ecosystem. Therefore, we are not convinced to support the continuation of this project.
2 Likes
Hello esteemed community!I would like to remind all about our revised proposal and budget prior to onchain voting for our proposal ââBUILDING ROOTSTOCK COMMUNITY OF USERS AND DEVELOPERS IN GHANA â
RootstockCollective Ghana Revised Budget Proposal : Milestone 1: Community Activation & Setup
Budget: $1,800
Focus: Establishing the foundation, building awareness, and onboarding the initial community members"Allocation of Budget" * Community Events / Meetups (2 sessions): $600
- Branding & Educational Materials (posters, slides, guides): $250
- Facilitator Support & Coordination: $400
- Participant Incentives (small rewards, data support): $300 * Logistics & Miscellaneous (venue top-ups, transport): 1.Expected Results" * Official launch of RootstockCollective Ghana
- Onboarding and orientation of the first cohort of members
- Increased ecosystem visibility and early-stage
partnerships
Milestone 2: Developer & Builder Engagement*
Budget: $1,800*
Focus:* Transitioning from awareness to active participation through technical engagement and building
Budget Allocation*
*$700 for technical workshops and hack sessions * $250 Developer Resource Kits (including tutorials, tools, and test tokens) * Mentorship Stipends & Coordinator Support: $400
Community Engagement Incentives:* $250
- $200 for content creation (videos, recaps) and documentation. ### 1.Expected Outcomes**
2.Formation of an active developer and builder community
3.Initiation of early-stage prototype projects
4.Increased adoption of Rootstock tools and smart Bitcoin infrastructure
âMilestone 3: Sustainability and Community Projectsâ Budget: $1,800
Focus:Supporting community-led projects, ensuring sustainability, and showcasing impact
. Budget Allocation
1.$800 in microgrants for community projects
2. Demo Day / Final Showcase Event:$500
3. Operational Costs (coordination, reporting) $300
- Marketing & Expansion Materials: $200
. Expected Results
" * Launch and support of community-driven projects
- Public demonstration of solutions and achievements
- Strengthened long-term sustainability and ecosystem presence
Total Budget Summary*
$5,400 = $1,800 x 3 milestones
We hope you would support and help us move to our next phase as equip developers to build on ROOTSTOCK.
Thanks.
@Curia We appreciate the direct feedback and agree â attendance alone does not demonstrate impact. We take responsibility for not clearly showing retention or measurable value.
As we move into Milestone 2, our focus is on activating the community through a structured bootcamp approach, not just events.
We are implementing:
Structured onboarding into active community channels
Clear tracking of active participation, repeat engagement, and contributions
A guided pathway for members to engage with the Rootstock ecosystem
Our goal is to convert a strong portion of participants into active contributors, not just attendees.
Content creation will be structured and team-led, with clear templates, mentorship, and review to ensure quality and alignment with ecosystem needs.
We are also improving execution with standardized processes, clearer reporting, and transparent KPIs.
Our focus in Milestone 2 is simple: activate the community, drive participation, and deliver measurable ecosystem value.
Gm, @Oluman , we are so appreciative to you for all the responses and updates that you have provided recently. We want to reiterate that we are personally supportive of the mission to provide opportunities for youth in Ghana and to expand the Rootstock ecosystem into this region. The intent behind the project is exactly what we want to see in the Collective.
However, as a delegate, our responsibility is to ensure that DAO funds are distributed based on the successful completion of the agreed upon milestones. After reviewing your responses and the feedback from other delegates like @Curia and @Ignas , we have several concerns regarding your intented move to an on-chain vote for the Milestone 2 [1]payment ($1,800) at this stage. As we noted in an earlier comment, we would need to see a breakdown of successful execution of goals to deliverables, which we donât see. In addition, in that earlier comment, we had suggested that before you progress to Milestone 2 deliverables, that you complete all the Milestone 1 deliverables as you had proposed.
Some of our concerns regarding Milestone 1 are:
-
By your own admission in the KPI table, the primary onboarding target of 150+ members was missed by over 50% (achieving ~67 registrations), and the 5 educational posts (a core deliverable of M1) were unilaterally moved to the bootcamp phase. In a milestone based funding model, a milestone cannot be considered complete if the key performance indicators were significantly missed or deferred.
-
While 67 registrations on Luma are a start, registrations do not represent an active community. To verify the Community Activation phase, please provide a direct link to the Telegram or Discord channel where these members are currently engaging. We need to see that a foundation actually exists before funding the next level of engagement.
-
The âRootstock Dev Guideâ link has been a point of friction for several delegates. For us to verify the training of 30 users, the materials used must be robust and publicly accessible. We suggest moving these resources to a public GitHub repository or another stable document viewer rather than a restricted Google Drive link, to ensure the DAO can audit the quality of the education provided.
We want this project to succeed, but cannot support a full payment for an incomplete milestone. Before you move to an on-chain vote, we suggest one of the following:
- Publish the 5 educational posts and provide the community channel link now, rather than waiting for Milestone 2.
AND/OR - Pro-rated Request: Consider if a full $1,800 amount is appropriate given that significant portions of the work were deferred or missed.
We want to see the Ghana community thrive, but that requires a high standard of professional execution and reporting to ensure a successful execution and long term sustainability for not only Rootstock but for the Ghana community members who commit to this project. We look forward to your thoughts on how we can bridge this gap before the vote. Tks!
We had mistakenly noted this as an upcoming Milestone 1 payment for an on-chain vote. As noted by Tane ( Building rootstock collective community of developers and users in Ghana - #55 by Tane ), Milestone 1 has been previously approved for payment ( Tally | RootstockCollective | BUILDING ROOTSTOCK COMMUNITY OF DEVELOPERS AND USERS IN GHANA;This proposal aims to establish and grow a vibrant Rootstock (RSK) community in Ghana by onboarding new users, training local developers, and promoting real-world blockchain adoption. Through community events, workshops, developer meetups, and hands-on education, the project will create awareness of Rootstockâs Bitcoin-sidechain ecosystem. DiscourseLink:https://gov.rootstockcollective.xyz/t/building-rootstock-collective-community-of-developers-and-users-in-ghana/638 M1lestone:1 ) âŠď¸
1 Like
Thank you sincerely for the thoughtful feedback and for your continued support of the broader mission to grow the Rootstock ecosystem in Ghana. We genuinely appreciate the time and diligence taken by you and other delegates to review our progress.
We fully acknowledged the concerns raised regarding Milestone 1, particularly around KPI delivery, onboarding numbers, and the timing of certain deliverables. Itâs important to clarify that, given the realities on the ground and early community feedback, we made a conscious decision to adapt parts of our initial approach to prioritize deeper engagement over surface-level metrics. While this meant falling short on some numerical targets, it allowed us to begin forming a more committed and educable base.
That said, we understand that in a milestone-based framework, delivery must be both measurable and verifiable. We take responsibility for gaps in reporting clarity and the delays in making certain resources publicly accessible.
Regarding the technical guide, we have already removed restrictions to ensure full visibility. Additionally, we will be transitioning these materials to a more public and developer-friendly platform such as GitHub to improve auditability and long-term accessibility, as suggested by the delegates.
On the educational content, we respectfully maintain our position to deliver this during the bootcamp phase. We believe aligning the content rollout with the bootcamp will significantly improve its relevance, engagement, and practical impact, allowing participants to directly connect learning with hands-on experience.
We are also taking immediate steps to strengthen transparency by:
- Publishing the educational content initially scoped for Milestone 1
- Providing direct access to our community channels for verification of engagement
- Improving the structure and clarity of our reporting
Our core request, however, is for the opportunity to proceed with Milestone 2.
Milestone 2 is not just a continuationâit is a critical consolidation phase. It gives us the structure to:
- Properly activate and engage the existing community base
- Deliver the bootcamp experience that drives meaningful onboarding
- Improve transparency through clearer reporting and accessible resources
- Align more closely with DAO expectations in both execution and communication
In essence, Milestone 2 is where the foundation weâve started building becomes fully visible and impactful.
We respectfully ask the Collective to consider the intent, the groundwork already laid, and the potential ahead. With your support to move forward, we are confident we can address the current gaps, strengthen accountability, and deliver a far more robust outcome for both Rootstock and the Ghana community.
We remain fully committed to improving, adapting, and delivering at the standard expected.
Thank you again for your guidance and consideration.
1 Like
Hello @Oluman , thank you so much for the candid response and for acknowledging the gaps in Milestone 1 delivery. We truly appreciate and understand your unique locational perspective; navigating local nuances is always a challenge in global ecosystem growth.
However, we must be clear: as a delegate, we cannot support an on-chain vote for the full $1,800 payment for Milestone 2 [1]at this stage.
The purpose of milestone-based funding is to provide a âcheck and balanceâ for the DAO. If we approve a 100% payout for a milestone where the core deliverables (Educational Posts) were deferred and the primary KPI (Onboarding) was missed by over 50%, we undermine the governance framework of the Rootstock Collective, and that is not fair also to your potential for the success of this proposal.
To find a path forward that supports your work in Ghana while maintaining DAO accountability, we suggest the following:
- You mentioned taking steps to provide access to community channels. Please post the direct link to your Telegram or Discord channel in your reply. Seeing the 67 members interacting is the âProof of Lifeâ the delegates could make them feel more comfortable.
- The 5 educuational posts: If these are to be moved to Milestone 2, they must be treated as additional requirements for that phase, not a replacement for missed M1 work.
- Adjusted On-Chain Vote: If you proceed to a vote now for $1,800, we will unfortunately have to vote âNoâ based on the missed KPIs. However, we would be open to supporting a pro-rated payment (e.g., $1,000) for Milestone 1 to cover your initial logistical costs, with the remaining $800 being âunlockedâ only after the 5 educational posts and the 150-member target are actually verified during the next phase.
We want to empower the youth in Ghana, but we must do so through a professional framework that rewards completed deliverables. We want to work with you to bridge this gap so you can move into the Bootcamp phase with the full confidence of the Collective. Tks!
We had mistakenly noted this as an upcoming Milestone 1 payment for an on-chain vote. As noted by Tane ( Building rootstock collective community of developers and users in Ghana - #55 by Tane ), Milestone 1 has been previously approved for payment ( Tally | RootstockCollective | BUILDING ROOTSTOCK COMMUNITY OF DEVELOPERS AND USERS IN GHANA;This proposal aims to establish and grow a vibrant Rootstock (RSK) community in Ghana by onboarding new users, training local developers, and promoting real-world blockchain adoption. Through community events, workshops, developer meetups, and hands-on education, the project will create awareness of Rootstockâs Bitcoin-sidechain ecosystem. DiscourseLink:https://gov.rootstockcollective.xyz/t/building-rootstock-collective-community-of-developers-and-users-in-ghana/638 M1lestone:1 ) âŠď¸
1 Like
Thanks for the continued updates, @Oluman, and for the candid acknowledgment of the gaps in M1 delivery.
We want to provide some context on where we stand. When we first reviewed this proposal back in November, we were the first to suggest scaling Milestone 1 down to a small pilot in the $1,000-1,500 range to prove capability and demand before expanding scope. The community rallied behind that direction, and you revised the proposal to $1,800 per milestone with clearly defined KPIs. We supported that revised proposal, and voted in favor of M1 on-chain, specifically because the scope was small enough that clean execution would build mutual confidence for subsequent milestones.
With M1 now executed and the $1,800 distributed, the question is whether M1 delivery justifies progressing to M2. In our view, it does not.
By your own reporting, the 150+ onboarding target was missed by over 50%, the 5 educational posts were unilaterally deferred, and as @ChronoTrigger pointed out, the presentation slides appear to be AI-generated topic lists rather than actual training materials. The pattern of responses in this thread, including moving goalposts and promising to address concerns âin the next phase,â does not give us confidence that M2 execution would be materially different.
We echo the positions of @Kaf_Anode, @Curia, @DAOstar_gov, and @Ignas. Before we could consider supporting an M2 on-chain vote, we would need to see M1 deliverables actually completed first:
- All 5 educational posts published now, not deferred further
- Community channel link with verifiable active members, not just event registrations
- Honest KPI reconciliation with target vs. actual, acknowledging what was missed rather than reframing it as âprioritizing organic growthâ
The whole point of starting small was that a $1,800 milestone should be easy to deliver cleanly. If the bar was too high at this level, scaling up to a bootcamp and developer engagement phase carries significant risk. We are not in a position to support an M2 on-chain vote given the current state of M1 delivery.
We remain supportive of bringing Rootstock to Ghana and would genuinely like to see this project succeed. But that requires completing the work that was funded before requesting additional funds.
3 Likes
Hi @DAOstar_gov, just a note: the Milestone 1 on-chain proposal has already been voted on and executed, so the $1,800 has been distributed. The discussion around pro-rating the M1 payment or adjusting the on-chain vote amount is no longer actionable at this point.
The relevant question now is whether M1 was delivered to a standard that justifies supporting an M2 on-chain vote, which is where we think the conversation should focus.
3 Likes
Hello, @DAOstar_gov and crew! We are appreciative of the feedback that has been shared thus far and comprehend the concerns regarding Milestone 1. Our focus now is not to revisit whatâs already been executed, but to rebuild confidence and demonstrate stronger delivery in the next phase.
For Milestone 2, we are committed to a more open and hands-on approach that clearly displays progress, engagement, and actual ecosystem impact as it occurs. Weâre open to refining the scope and approach in line with the DAOâs expectations and would value your guidance on what would give members the confidence to support moving forward.
Because of this, it maintains its non-defensive, self-assured, collaborative nature, which is what DAO voters value.Thanks!
We donât want to come across as mean but most of your replies so far are lacking concrete evidence. For example, when we first asked you to provide evidence of community onboarding, such as a TG or Discord group, you replied by acknowledging the KPI was not met, mentioning an overestimation of the local context, and saying you were prioritizing organic growth for people who attended your events. This comes across more as an excuse rather than a real effort to provide proof or improve the results.
Even after DAOstar emphasized our point and asked for direct proof of onboarding through a link to the community channel, your response was:
This does not qualify as taking immediate steps, it reads more like an immediate reply. We donât think this should be allowed to pass easily, as this could create the wrong precedent for the DAO. The team clearly hasnât delivered the KPIs as promised and their responses do not demonstrate professional execution.
And yet they are still asking the community to support Milestone 2, despite Milestone 1 not being fully delivered. This raises a red flag for us.
2 Likes
Thank you so much, @tane for your help and especially for noticing our inconsistancy and incorrect reference of M1 for payment, which has already been paid. It was more of a confusion of what payments had been completed, and we really appreicate your help, thank you! Weâve updated our two prior comments (comments 1 & 2) above to indicate the correction of the Milestone 2 for on-chain vote and payment, and the addition of footnote comments with the reasoning for our correction. Thank you, and so appreciate your help!
2 Likes
Hello @Oluman , thank you for responding to all the delegates questions. For us, we fully support @Tane comments above that what would give us the confidence with a Vote in Favor of Milestone 2, is if you provided these requested deliverables of Milestone 1 as you had orginally proposed.
We believe that what Tane is recommending, and along with our prior requests for points 1 and 2 are very fair to request before any further funding. We also donât currently have confidence in your ability for execution of the Milestone 2 deliverables, if you cannot address these simplified requests below.
As weâve already stated a couple of times prior, we are very much in support of the intent of this program, itâs just that we require from all grant requestors simular proof of work requirements as the grantor proposes. And as we have previously mentioned in earlier comments, the recommendation was that you complete all M1 deliverables before progressing to M2 work.
We want to work with you, and have this program be successful, however, we need for your active participation with the PoW as the program manager.
The delivery of these three items as noted by @Tane below, would give us the confidence and a vote in favor for the Milestone 2 funding. Otherwise, we are currently in the position to vote against the Milestone 2 funding request without these deliverables.
1 Like
Hello @Oluman , Eren here from DAOplomats. As we stated during the initial review in November, milestones only work if they act as strict accountability gateways for the deployment of treasury funds. The DAO treasury cannot operate on a trust-based system when the agreed-upon Proof-of-Work, specifically the community onboarding links and educational materialsâremains conspicuously missing. Furthermore, what specific, verifiable metrics are you implementing right now to prevent this exact reporting failure in the future?
1 Like