[2508 Grant] Infrastructure VenturesPath to Ecosystem Growth

We have extensively reviewed the deliverables at the Milestone 1 and are very much impressed by the quality of the documents provided by the team; the documents that describe the selection process and its scoring are well-organized and easy to check. We are grateful to see the promising projects are selected to be ready for the acceleration cohort. We are looking forward to the upcoming updates!

One question on this platform; how do we, as a delegate/grant reviewer use this platform tool during the acceleration cohort and in upcoming milestone reviews?

2 Likes

Hi @Tane,
Thank you for your thorough review and for sharing such positive and encouraging feedback. I’m glad to hear that you are impressed with the quality of the documents and our selection process. It is incredibly rewarding to know that our work is meeting the expectations of the community.

That’s an excellent question regarding the platform. We designed it specifically to ensure this level of transparency and to allow for direct community involvement. Right now, you’re able to view its contents, but we can create individual accounts for delegates and community members who want to support these companies and follow their journey closely. With an account, you will be able to view the teams’ submissions, milestone reports, and progress updates directly on the platform. This will give you a clear and comprehensive view of their development throughout the acceleration cohort. Let us know if this is something that interests you.

1 Like

Hi @Francisco thank you for sharing your Milestone 1 deliverables. The 7 selected projects are impressive. There are a few heavy hitters such as Squid and Bungee, which I use regularly, and will be amazing to have them deploy on Rootstock. Their deployment on Rootstock would be highly impactful, with the potential to materially improve DeFi metrics and significantly increase the accessibility and usability of Rootstock tokens.

I have a few questions that would benefit from clarity:

  1. Which tokens, beyond RIF, will be included in your KPI tracking?
  2. Can you please elaborate on what you mean in your Milestone 2 output, when you write, “RIF treasury strategies developed for each project”?
  3. In Milestone 5, one of your goals is “≥1M RIF tokens staked”. This implies that you are encouraging these projects to participate in governance?
  4. Which roles on the selected project’s team will be completing the accelerator course?
  5. Have you thought about a fast-track path for the mature projects? These projects don’t necessarily need to go through the basic learning in the accelerator, but rather we should be focused on bringing them up to speed quickly on how to deploy on Rootstock and support Rootstock’s tokens (see question 1).

Separately, the Collective, alongside Infrastructure Ventures, should proactively plan growth campaigns around these new deployments. Several of these projects bring meaningful distribution and user reach. A coordinated incentive strategy—potentially with matching incentives from both the Collective and the projects—could help maximize impact. Tagging @PGov and @Kaf_Anode, who have experience executing similar initiatives in other ecosystems.

3 Likes

Thanks @404Gov; really thoughtful feedback, and glad to hear the Milestone 1 cohort resonates.
We think these questions are the right ones to pressure-test whether this turns into measurable ecosystem outcomes versus just “logos”.

Some thoughts:

  • Which assets we’re actually optimizing for (beyond RIF)
  • What “RIF treasury strategies per project” concretely means (e.g., liquidity/incentives/treasury coordination)
  • How we’re thinking about the ≥1M RIF staked target
  • Who exactly on each team is going through the accelerator (BD vs. engineers vs. product) so the work actually lands.

Also strongly agree on the “fast-track” point and the broader growth plan: mature teams shouldn’t be forced through generic curriculum if the bottleneck is deployment + liquidity + distribution.

2 Likes

Hi @404Gov and @PGov,

Thank you both for this thoughtful feedback.

Let me address your questions directly:

  1. On KPIs and Token Focus:

Regarding our KPIs, our primary focus is aligned with the metrics that matter most: the impact on RIF and the overall Total Value Locked (TVL) on the ecosystem.

For the projects in our current cohort, the tokens we anticipate will have the most significant initial impact are rBTC, USDT0, and DOC. Our strategy is not one-size-fits-all; we will work with each company to create several different token pairings depending on their specific goals and user base. All of these activities and their resulting liquidity will be meticulously tracked and reported as part of our ongoing TVL milestones.

  1. On “RIF Treasury Strategies” and Ecosystem Alignment:

Our core objective is to ensure each project becomes a long-term, aligned member of the Rootstock ecosystem. The most effective way to achieve this is by demonstrating tangible value and making it as easy as possible for them to participate.

When we refer to developing “RIF treasury strategies,” it means our job is to create a compelling proposal for each project, clearly outlining the benefits of acquiring and staking RIF. We want to show them why this is a strategic decision for their own growth and success within our ecosystem. Our goal is to facilitate this alignment by presenting a clear value proposition, not by imposing a requirement.

3. On Accelerator Roles and Team Participation:

To ensure the work “lands” effectively, we focus our engagement on the key decision-makers and implementers within each project. This typically involves the CEO, who is crucial for strategic decision-making and ecosystem buy-in, alongside the core technical team responsible for the integration. Depending on the company’s structure, this could be the CEO and a technical co-founder, or the CEO and a lead engineer.

4. On Fast-Tracking Mature Projects:

Yes, we are already actively fast-tracking several of the companies in our cohort. We recognize that mature teams need targeted support, not a generic curriculum. We must balance this very carefully to ensure the companies receive the focused support they need without overburdening their schedules.

I’m pleased to share that progress is already being made. Even at this early stage, we have initiated technical discussions between our team, the companies’ technical leads, and the experts at Rootstock Labs to map out the integration path. It’s all in progress right now.

5. On Go-to-Market and Growth Campaigns:

On this crucial point, we feel very supported and are in full agreement. Several members from both the Rootstock Collective and Rootstock Labs have already joined calls with the companies, demonstrating a fantastic collaborative spirit from the start.

We believe this early involvement is key. We are confident that when the time comes to execute the go-to-market strategy, we will be able to align quickly and effectively with all key stakeholders to design and launch the coordinated growth campaigns you mentioned.

We look forward to keeping you updated on our progress.

1 Like

Hi everyone,
I’m pleased to say that we were finally able to submit our on-chain proposal do Milestone 2.

Milestone 2 – Acceleration Phase 1: Foundation (Month 2)

Outputs:

  • Weekly mentorship sessions initiated (technical, GTM, treasury);

  • RIF treasury strategies developed for each project;

  • Technical feasibility validation completed.

Acceptance Criteria: Signed onboarding agreements for 4-6 projects.

Evidence: Mentorship session logs, treasury strategy documents, and technical validation reports.

@404Gov @CodeKnight @ChronoTrigger @Tane @Curia @PGov
Hopefully, we can maintain engagement even during the holiday time!
I wish everyone a great time with the family :orange_heart:

4 Likes

@Francisco We’re impressed by the great work the team has done. The report is well structured and easy to follow. Scouting down from around 225 projects to a final cohort of 7 is a lot of work and really shows the effort behind the process. Also great to see Alby here with a fresh new logo. Looking forward to supporting the next phase!

1 Like

Seems like you’ve sourced some quality teams! Congrats all involved. Looking forward to seeing mainnet impact on this one. Do you have any idea of timelines on when we may see that?

1 Like

We just found that there have been discrepancies in how milestone 2 (and 3 for this matter) grant budget is planned in the final grant structure as below:

The current onchain seems to have applied the latter ($8,000), thus we assume that the milestone 3 budget will be $12,000, not $15,000, and the total budget size won’t be changed ($50,000). However, we would like to request the team to clarify on them and properly update the specifications of the whole grant. This should have been addressed before when @ChronoTrigger mentioned this structure as below.

We vote for the milestone 2 grant proposal this time, but we will revisit how the grant is actually structured and closely look into any inconsistent descriptions or discrepancy.

2 Likes

Hi @Tane,
You’re correct. It seems we had discrepancies in two sections of our reviewed proposal. We’re following the path we proposed on the Milestone section, not the budget section, as seen below.

Thank you for highlighting this. Hopefully, we did not mislead anyone in the community. @ChronoTrigger

2 Likes

Nice catch @Tane.
As long as the next milestone is $12k, this should be ok.

3 Likes

Peach Bitcoin is Now on Rootstock :peach:

We are proud to announce a key advancement for the Rootstock ecosystem. Please welcome Peach Bitcoin, the first of our partners to go live with a Rootstock integration by enabling Dollar on Chain ($DoC) as a payment method, allowing users to trade BTC using $DoC settlement rails. This is step one. Peach Bitcoin is evaluating a deeper Rootstock-native integration that further strengthens the escrow and settlement.

About Peach Bitcoin

Peach Bitcoin is a leading peer-to-peer, non-custodial Bitcoin marketplace. It empowers users to buy and sell Bitcoin securely and privately without the need for KYC, using a sophisticated escrow system. The service is available in Europe, Africa, and Latin America.

We congratulate the Peach Bitcoin team on their launch and invite you to learn more about their platform.

Official Links

Website: https://peachbitcoin.com

X (Twitter): https://x.com/peachbitcoin

Announcement Tweet: https://x.com/peachbitcoin/status/2017232659181695307

We have more achivements to share in the upcoming weeks!
Here is the signed Peach Bitcoin onboarding agreement, and we have other three :locked:

@ChronoTrigger @Tane @GoldenGatsby @Curia @404Gov @CodeKnight

4 Likes

Congratulations @Francisco and the Peach Bitcoin team on this milestone. Seeing a privacy-focused P2P marketplace integrate $DoC as a payment method is exactly the kind of Bitcoin-native bridge we need.

Noticed the website is already available (at least) in Portuguese, Spanish, and English (did I miss others?). Good work on this!

The letter of intent looks nice, and I genuinely hope Peach’s intention to work more deeply with Rootstock is sincere and follows through.

I’d like to raise a flag on the obvious potential for deeper settlement integration down the line. Peach is already intrinsically focused on BTC, the next step would be to integrate native rBTC on Rootstock, for a blooming ecosystem of web3-enabled BTC-centric products.

Looking forward to those other three :locked: projects to be announced.

1 Like

Dear Community,
We have completed Milestone 2, “Acceleration Phase 1: Foundation”. The primary objective was to establish a qualified pipeline of projects and initiate foundational support through mentorship, RIF treasury strategies, and technical validation.

Milestone 2 – Acceleration Phase 1: Foundation (Month 2)

Outputs:

  • Weekly mentorship sessions initiated (technical, GTM, treasury);
  • RIF treasury strategies developed for each project;
  • Technical feasibility validation completed.

Acceptance Criteria: Signed onboarding agreements for 4-6 projects.

Evidence: Mentorship session logs, treasury strategy documents, and technical validation reports.

All acceptance criteria and deliverables have been met. We successfully secured signed Letters of Intent (LOI) from four high-potential projects, Peach Bitcoin, Cyclo, Caddy Finance, and Blockroll, fulfilling the core requirement. For this cohort, we have also completed weekly mentorship sessions. A key observation during this phase is the maturity of the projects we have attracted. Many of these mid-stage companies have opted to conduct their technical integration studies and subsequent development in-house. This demonstrates a strong commitment to the Rootstock ecosystem, as they are allocating their own resources to ensure a deep and robust integration.

All supporting documentation, including the signed LOIs, detailed reports, and the dashboard, is available via the links provided below for your review.

Evidence:

Looking Ahead to Milestone 3

The successful completion of Milestone 2 has created significant momentum. Our team is now channeling this energy directly into Milestone 3, where we will drive a wave of new deployments, onboard them to the ecosystem, and ensure continued growth.

Let us know if there are any questions.

3 Likes

Congrats!

I see from the 1-pager that Swiss regulations impose limits of 1,000 CHF per trade/day and 100k USD/year per user, which keeps the platform retail-focused with smaller transaction sizes. Given these constraints, could you share more context on the expected impact of the $DoC integration. Specifically, what are the volume projections and number of trades expected using $DoC for settlement? And how is the team planning to encourage $DoC adoption? (in-app marketing, incentives, etc.)

Lastly, is there anything specific you’d like delegates to do to support this integration or help maximize its impact?

Congrats again on this integration. :clap:

2 Likes

Thanks for your update, @Francisco!

We reviewed the Milestone 2 evidence links and the deliverables folder. The only complete deliverables set we can find is for Blockroll (treasury strategy, technical validation, and a session log). Based on that, we have three questions:

Coverage across the 4 onboarded projects

Blockroll has the full set of M2 artifacts, but we do not see equivalent treasury strategy, technical validation, and session log materials for the other signed-LOI projects. Can you upload the same three artifacts per project (even if “lite” versions), so the milestone is auditable across the full set?

What “technical feasibility validation” means when teams are doing work in-house

In Blockroll’s technical validation, the Rootstock-focused vault layer is still pre-launch and there is no Rootstock-specific repo reviewed yet; the main blockers are PRD updates, scope narrowing, gas sponsorship controls, and audit scoping. Can you clarify what you consider “validated” for the other projects if they are doing integration studies internally, and provide a comparable 1-page assessment per project?

Treasury strategy expectations vs. advisory direction

Blockroll’s treasury strategy is explicitly non-binding and preliminary (e.g., indicative 15 to 25% range, readiness assumptions, and sustainability/risk flags). For the other projects, can you share the same level of clarity: whether it is a recommendation vs. a commitment, what assumptions drive the range, and what guardrails you expect to avoid over-subsidizing early yield demand?

3 Likes

Hi @Axia,

Given the Swiss limits, we expect smaller ticket sizes but higher trade counts, so the key metrics we’ll report are DoC-settled trade count and DoC settlement volume. We’re treating the first 4-8 weeks as a ramp and will publish numbers once we have baseline data (so it’s auditable on-chain + via internal analytics).

On rollout: DoC is live for settlement now, and the next step is pushing the escrow flow using DoC (rather than “primary rail” language) so more transactions naturally route through it as escrow adoption increases.

Adoption plan is straightforward: in-app education + prompts at settlement/escrow selection, and light, capped, time-boxed nudges only if needed (no ongoing subsidy). From delegates ‘liquidity intros’ are our highest request to ensure retail users don’t face slippage as we scale.

1 Like

Hi @Tane,
Thank you for the feedback.

1) Coverage across the 4 onboarded projects
You’re right that Blockroll is currently the only project with the full set. For the others (Peach Bitcoin, Cyclo, Caddy Finance), we will upload ‘lite’ versions of the 3-artifact set by to ensure the milestone is fully auditable across the portfolio.

2) What we mean by “technical feasibility validation” (when teams do work internally)
For M2, “validation” does not mean “Rootstock specific repo fully reviewed + production code shipped.” It means we confirmed: (i) architecture fit on Rootstock EVM, (ii) required dependencies and Rootstock specific deltas (gas/UX assumptions, liquidity/oracle/bridge requirements), (iii) scope and execution plan, and (iv) identified blockers/risks with clear next steps. Deeper repo review and implementation checkpoints sit in M3 once there is a Rootstock specific branch/repo and testnet/mainnet work underway.

3) Treasury strategy expectations vs advisory direction
Same principle as Blockroll: these are non-binding, preliminary recommendations, not commitments. The goal is to set indicative ranges/assumptions and clear guardrails so we don’t over subsidize mercenary yield.

1 Like

Noted! Thanks for this ask.

2 Likes

Hey @Francisco thanks for publishing the M2 evidence.

I’ve reviewed the materials shared (LOIs, tracking sheet, mentorship logs, treasury strategy lite, and technical validation documentation).

Based on the deliverables defined for Milestone 2:

  • 4–6 signed onboarding agreements → You’ve provided 4 (Peach, Cyclo, Caddy, Blockroll), which satisfies the stated acceptance criteria.

  • Mentorship initiation, treasury strategy development, and technical feasibility validation → These are clearly demonstrated for Blockroll. Equivalent documentation for the remaining onboarded projects is not yet fully visible, but the structure appears to be in place.

Structurally, Milestone 2 is completed in line with the milestone definition. Ahead of the next milestone, it would be useful to understand which of the onboarded projects is currently expected to serve as the primary candidate for the first Rootstock mainnet deployment under the program.

Additionally, publishing concise “lite” summaries (mentorship + treasury + feasibility) for each onboarded project would strengthen portfolio-wide documentation.

Appreciate the structured milestone communication and transparency throughout the process.

3 Likes