Thanks @AndrewG for the updated proposal. We voted for the milestone 1 request as below. One request for this post; would you add required deliverables and target KPIs to be achieved for each milestone so that we can review your each milestone’s completion report with defined KPIs to evaluate against?
Voted FOR this proposal. Appreciate @AndrewG’s responsiveness to delegate feedback and the restructuring of milestones into phased deliverables that enable clearer progress tracking by delegates.
3 Likes
Hi @Tane let me share our current deliverables & KPI targets so we can more clearly measure progress for each milestone.
Project Milestones Overview
Milestone 1 (M1)
| Category | Details |
|---|---|
| Deliverables | 1) Standalone wallet 2) NPM package for a white-labeled SDK 3) SDK usage guides and documentation |
| KPIs | - User and usage tracking implemented, including wallet creation, active addresses, user sessions, transaction volume, DApp interactions, and gas sponsorship usage |
Milestone 2 (M2)
| Category | Details |
|---|---|
| Deliverables | 1) Full wallet integration with Blockscout 2) Usage statistics covering 3 months of gas-sponsored activity 3) DApp outreach results and engagement metrics |
| KPIs | - Retention rate: 10% over the first 3 months, defined as addresses returning in 2+ distinct sessions across separate days - Gas sponsorship usage: target of $1,500.00 in sponsored transactions per month (usage will inform continuation in M3) - 1+ production DApp integration live with a direct wallet integration (prioritized from popular apps with higher TVL listed on DeFi Llama) |
Milestone 3 (M3)
| Category | Details |
|---|---|
| Deliverables | 1) 6 months of cumulative usage statistics 2) Comprehensive analytics and performance report |
| KPIs | - Daily Active Users (DAU): June 20 – July 20, 2026 target of an average 100 new users per day, resulting in 356+ daily active users during that timeframe. - Active address usage: Blockscout wallet usage from 10% of monthly active addresses - Retention: average 10% across the full project duration (returning users for multiple sessions) - Cost per user acquired: detailed user acquisition cost and efficiency analysis - 3+ DApp integrations actively using the wallet |
1 Like
Hi @AndrewG, it’s been over two months since the grant was funded and we haven’t seen a Milestone 1 completion report. The standalone wallet, SDK, and usage tracking were due January 20. As a funded grantee, we expect timely updates on deliverables and progress. Could you provide the M1 report as soon as possible?
Hi @Tane thanks for the note. Yes those items are implemented (except for gas sponsorship - see below). From my perspective the KPI was to implement these items during M1 and then provide a report on usage when we apply for M2, which is coming up shortly. However, I may have misunderstood the need to post an update sooner, so I apologize for the lack of information provided. I will look at the structure for the M1 reporting and add more info shortly.
It would not have been feasible to provide a report Jan 20, first of all that was the start of the grant so we were just building things out. Secondly, we are tracking usage over these first 3 months. To date we’ve seen 1000+ unique users of the wallet. We will prepare a usage report and submit in the coming weeks.
Here’s what’s been delivered so far:
- A standalone page for the Rootstock global wallet: https://rootstock-wallet.blockscout.com/
- A white-labeled SDK for developers and protocols, enabling their users to connect the Rootstock wallet within their applications: https://www.npmjs.com/package/@blockscout/rootstock-global-wallet
- A developer integration guide and overall overview of the Rootstock global wallet: Integration Guide - Blockscout
Regarding Gas Sponsorship, our implementation partner Gelato has unfortunately sunset this service, so it has not been possible to implement. However we are still seeing robust usage. This will result in a smaller ask for M2 as gas sponsorship cost coverage will no longer be required.
Thanks for the update, @AndrewG. Good to see the standalone wallet, SDK, and integration guide are live, and 1000+ users is a reasonable early signal.
We want to clarify our understanding of the milestone dates. The dates in the proposal (M1: January 20, M2: April 20, M3: July 20) are completion deadlines, not start dates. A completion report should be posted by that date, not deferred to whenever the next milestone application comes up. We raised this expectation when voting for M1 and asked for defined KPIs to evaluate against at each milestone.
We understand M1’s timing was tight given the on-chain vote landed January 21, essentially making the M1 deadline day zero. That’s worth acknowledging as a scheduling issue in the original proposal rather than treating the report as something that wasn’t yet due.
Two asks:
- Post the formal M1 completion report with the usage metrics and KPIs we requested, by April 20
- Propose revised completion dates for M2 and M3 that reflect realistic timelines, given M1’s late start and the removal of gas sponsorship from scope
2 Likes
Thanks @Tane will do and will also plan to post metrics relevant to M2. Fyi we are exploring another gas sponsorship avenue as we feel this is an important part of the WaaS. Will provide additional details once we confirm the integration.
1 Like
Hi @AndrewG thank you for sharing your deliverables. The wallet, SDK, and dev integration guide all look good. I would just remove the Gelato gas sponsorship information from the docs as soon as you can. What do you need the Collective’s help with?
Thanks @Axia we will get that cleaned up this week and also share our progress to date.
1 Like
[2512 Grant 1] Rootstock Global Wallet — M1 & M2 Completion Report
Grantee: Blockscout
Grant Amount: $20,000 USDRIF
Reporting Period: January 20 – April 14, 2026
Timeline Note
M1 was originally scheduled for January 20, 2026, with the on-chain vote landing January 21. Despite this tight window, we deployed M1 deliverables by January 28 — effectively 8 days past the original date. This shifts the effective dates for M2 and M3 forward by 8 days accordingly.
| Milestone | Original Date | Adjusted Date | Status |
|---|---|---|---|
| M1 | Jan 20, 2026 | Jan 28, 2026 |  Complete |
| M2 | Apr 20, 2026 | Apr 28, 2026 | Complete |
| M3 | Jul 20, 2026 | Jul 28, 2026 | In Progress |
Milestone 1: Standalone Wallet, SDK & Tracking
Delivered: January 28, 2026
Amount Requested: $4,750 USDRIF
Deliverables
| # | Deliverable | Status | Link |
|---|---|---|---|
| 1 | Standalone wallet page for Rootstock | Live |
rootstock-wallet.blockscout.com |
| 2 | White-labeled SDK (NPM package) | Published |
@blockscout/rootstock-global-wallet |
| 3 | Developer integration guide & docs | Published |
Integration Guide |
M1 KPI: User & Usage Tracking
As defined in our milestone KPI framework (Post #23), the M1 KPI was to implement user and usage tracking covering wallet creation, active addresses, user sessions, transaction volume, DApp interactions, and gas sponsorship usage.
Status: Complete. Tracking is implemented within the Dynamic wallet framework. We can pull additional on-chain statistics using the Blockscout MCP server.
Promotional Activities
Following deployment, we ran a launch campaign to drive initial adoption:
- Badge Mint: 738 badges minted — rootstockMilestone1Badge
- AMA Participation: Rootstock Collective AMA on X
- Promo Campaign on X: Blockscout announcement
- Email Newsletter: Sent to 300K+ subscribers — Updates from the Edge
Milestone 2: Explorer Integration, Retention & DApp Outreach
Delivered: April 2026
Original Amount Requested: $8,000 USDRIF (reduced — see Gas Sponsorship below)
Adjusted Amount Requested: $3,500 USDRIF
Deliverables
| # | Deliverable | Status | Details |
|---|---|---|---|
| 1 | Full wallet integration with Blockscout explorer | Live |
Users can log in via email, passcode, or wallet and use the wallet within the explorer interface |
| 2 | Gas sponsorship (3 months) |  Not delivered |
Gelato sunset their sponsorship program (see below) |
| 3 | DApp outreach results and engagement metrics | In progress |
See DApp Integration section |
Adjusted M2 Budget
Due to the Gelato gas sponsorship program being discontinued, we are only requesting the wallet integration subsidy ($3,500) and not the gas sponsorship costs originally budgeted. This reduces our M2 ask accordingly.
KPI 1: Retention Rate
Target: 10% over the first 3 months, defined as addresses returning in 2+ distinct sessions across separate days.
| Metric | Value |
|---|---|
| Total wallet users to date | 1,694 |
| Return users (sessions >1 hr apart) | 213 |
| Retention rate | 12.6% |
| Retention rate (separate days only) | 10.5% |
Status: KPI Met. Both retention measures meet or exceed the 10% target. The 12.6% rate (filtering returns <1 hr) and the 10.5% rate (distinct-day sessions only) are roughly in line with current industry standards for Web3 wallet products.
KPI 2: Gas Sponsorship
Target: $1,500 in sponsored transactions per month.
Status: Not achieved — external dependency.
Our initial gas sponsorship partner, Gelato, changed their program and we were unable to proceed with this method. As a result:
- We will not collect for gas sponsorship costs in M2.
- We are actively exploring integration with Zerodev for M3, as we believe gas sponsorship is an important metric for assessing whether it increases usage and retention.
- If implemented, we plan to shift the gas sponsorship KPI to M3 (see M3 Plan below).
KPI 3: DApp Integration
Target: 1+ production DApp integration live with a direct wallet integration.
Status: 
Partially met — Swapscout live, Tropykus on testnet.
Connecting with and gaining traction from popular DApps on Rootstock has been challenging. We have one live mainnet integration (Swapscout) and a testnet integration with Tropykus that will move to mainnet in M3. We also have active discussions with several other applications, though progress has been dependent on their response times and integration capacity.
DApp Outreach Summary
| Application | Status |
|---|---|
| Swapscout | Live on mainnet |
| Tropykus |  Testnet integration — moving to mainnet in M3 |
| Money on Chain | Active discussions |
| OpenOcean | Active discussions |
| Aera | In progress — struggling on integration |
| Sideshift |  Reply received, no active conversation |
| Bedrock | Rejected |
| Boltz | Rejected |
| Avalon | Not yet deployed on RSK |
| Mellow | Not compatible |
| Sovryn | No reply |
| Woodswap | No reply |
| Layerbank | No reply |
| Merkle | No reply |
| Rif | No reply |
We welcome recommendations from the community for additional applications to contact. We plan to move forward with Tropykus mainnet deployment and continue pushing integrations with OpenOcean, Money on Chain, and others in M3.
M3 Plan
Revised delivery date: July 28, 2026
Amount Requested: $7,250 USDRIF - includes 2K gas sponsorship
Gas Sponsorship via Zerodev
We would like to attempt gas sponsorship implementation via Zerodev for approximately 1.5 months (May 1 – June 15) to test usage. We are requesting a maximum of $2,000 to cover gas sponsorship during this period, and will only request the amount actually used for sponsorship — no additional fees.
At the beginning of June, we will post an update to assess usage and determine whether gas sponsorship is driving meaningful adoption. At that point, the Collective would decide whether to continue and, if so, take on the costs directly with Zerodev ($400/month + $1,400 one-time initialization fee).
M3 KPIs (as defined in Post #23)
| KPI | Target |
|---|---|
| Daily Active Users (DAU) | Average 100 new users/day during Jun 20 – Jul 20, resulting in 356+ DAU |
| Active address usage | Wallet usage from 10% of monthly active addresses |
| Retention | Average 10% across full project duration |
| Cost per user acquired | Detailed acquisition cost and efficiency analysis |
| DApp integrations | 3+ DApps actively using the wallet |
Summary
| Category | M1 | M2 |
|---|---|---|
| Deliverables | All 3 delivered |
Explorer integration delivered |
| KPIs Met | Tracking implemented |
Retention (12.6%) · DApp (1 live + 1 testnet) · Gas sponsorship (external) |
| Amount Requested | $4,750 | $3,500 (reduced from $8,000 — gas sponsorship removed) |
| Total Users | — | 1,694 |
| Return Users | — | 213 (12.6% retention) |
1 Like
Thanks for the detailed completion report, @AndrewG. We appreciate the transparency and the honest acknowledgment of the gas sponsorship situation.
However, we have significant concerns about the impact this grant has produced. 1,694 total users over three months with 213 returning. The 12.6% retention rate meets the stated 10% target, but against that user base it represents 213 people in absolute terms, which is too small a base to validate continued investment. The SDK package shows 9 weekly downloads, meaning effectively no third-party developer adoption.
On the DApp integration KPI, the target we agreed on was “1+ production DApp integration, prioritized from popular apps with higher TVL listed on DeFi Llama.” Swapscout is hosted at swap.blockscout.com and is Blockscout’s own swap interface, not a third-party DApp listed as a top protocol on DefiLlama as we suggested. With Tropykus still on testnet and 10 of 15 outreach targets stalled (5 no reply, 2 rejections, 3 others incompatible or inactive), this KPI is not met.
On process: this report bundles M1 and M2 completion, but only M1 has gone through an on-chain vote. Could you clarify what the next on-chain proposal covers? Will M2 and M3 be separate votes?
On M3, the DAU target of 100 new users/day would require roughly 3,000 new users in one month, nearly doubling the total accumulated over three months. The proposed lever is a $2,000 Zerodev gas sponsorship experiment with no baseline data. We don’t see a credible path from current traction to that target.
The team built what was scoped. The wallet works, the SDK is published, the explorer integration is live. But the purpose of this grant was to bring new users to Rootstock and drive ecosystem adoption, and on those terms the results don’t support continued funding. We would need to see a materially different acquisition and distribution strategy before supporting M3.
Hi @Tane thanks for the comments and appreciate the overall take. We’ve definitely had some unexpected challenges in regards to integration with 3rd party Rootstock apps. We are planning to separate M2 / M3 and will discuss with our team about strategies that might make M3 more viable. The gas sponsorship issue is a possible contributor to the lack of usage or interest, but we are not sure. and ideally would still like to test this. Overall market sentiment and other factors are likely contributing as well.
Will get back next week with a modified proposal for M3, and also check with Tropykus on their progress towards mainnet inclusion.
1 Like
Hi all - wanted to share an update and what our thoughts are about wrapping up M2 and proceeding to M3 for this grant. As mentioned above, we’ve had more difficulty than anticipated getting traction with apps on Rootstock. Despite our best efforts to contact and engage we have not received interest or responses from many projects. This said, we do have a testnet integration with Tropykus which we would like to move to mainnet. The gas sponsorship is an important component of this move.
Moving forward, we are proposing adjusted amounts for Milestones 2 and 3 of the Rootstock Global Wallet grant.
Adjusted Milestones:
M2 (Full wallet-explorer integration): $3,500 USDRIF (reduced from $8,000 due to gas sponsorship delay).
- We completed the integration with Blockscout, onboarded Tropykus in a testnet capacity and brought 1,694 total users and 213 return users to Rootstock. While this is not a huge number, considering the overall active and new accounts in the Rootstock ecosystem (Rootstock averaged 21 new accounts per day from Nov 20 2025 to Jan 20 2025), this represents a substantial number of new users.
- We are proceeding with the vote for this item
M3 (6-month run, analytics & gas sponsorship): $3,000 USDRIF Max (reduced from $7,250)
We would like to proceed with M3 in a reduced capacity which coincides with the lack of traction from apps in the ecosystem.
Why the reduction?
Overall we will be taking a loss on this grant due to the costs associated with the Dynamic integration. However, the implementation is already in place and we want to complete the project to determine whether gas sponsorship meaningfully increases usage and traction on the Rootstock chain.
How the M3 funds will be used:
- $1,500 — Partially cover monthly wallet infrastructure costs (the remainder is covered by Blockscout)
- $1,500 (max) — Fund gas sponsorship through June 15 to evaluate whether subsidizing transaction costs boosts regular usage and retention. This will be up to 1500, if less is used we will reduce the ask based on actual usage.
Updated M3 Deliverables:
- Gas sponsorship active on mainnet
- DApp integrations — 1 DApp actively using the wallet on mainnet (Tropykus)
- Reporting to assess user retention, user acquisition cost, and other metrics from the pilot including gas sponsorship usage. If Rootstock would like to continue sponsorship all functionality will be in place.
- We will provide an initial report June 15 to assess gas sponsorship utility.
- The completion date for reporting and overall assessment is July 28, 2026
We believe completing M3 is important for generating the data needed to evaluate whether a global wallet with gas sponsorship can drive sustainable ecosystem growth on Rootstock, even though the grant no longer covers our full costs. Please let us know your thoughts here before we proceed with the pared-down M3 integration.
Here is the proposal for M2 reimbursement 
Hi @AndrewG — I voted FOR the Milestone 2 payout. The budget reduction from $8,000 to $3,500 is reasonable given the removal of gas sponsorship costs, and I appreciate the team’s transparency and good faith in making that adjustment.
Regarding your request to connect with additional Rootstock dApps for integration — I’m tagging @Francisco from Infrastructure Ventures, as some of the projects he works with may be strong candidates for Global Wallet integration.
Feel free to reach out directly if there’s anything else I can help with!
1 Like
Hey @AndrewG ,
We voted FOR milestone 2.
Our rationale was rather formal, so it may not have conveyed how much we appreciate the depth of metrics you’ve shared throughout this milestone. Acquisition cost, retention windows, session-level data, full DApp outreach status, that level of granularity and depth is rare and genuinely useful for the ecosystem.
Also wanted to add congratulations on the Tropykus integration progress. They’re one of the strongest projects on Rootstock and getting that path to mainnet is a meaningful step. Looking forward to seeing it live and to the M3 data.
Update: We just learned that Tropykus will be winding down operations. This is unfortunate news, and we will double down on our efforts to contact and follow up with other Rootstock ecosystem apps to integrate the wallet.
If you have a direct contact with any of the apps listed below, please let us know. We have not had many rejections for the integration, but most of our inquiries to these projects have gone unanswered.
1 Like
Hi @AndrewG the news on Tropykus is unfortunate. Thanks for requesting feedback on the updated M3 scope.
Two observations:
1) DApp outreach
With Tropykus winding down, it would be useful to get a fuller picture of the outreach effort. Some thoughts:
The outreach table shows Bedrock and Boltz as rejected, and eight teams with no reply.
-
For the rejections: did these teams explicitly decline, or did Blockscout step back? What were the main reasons—technical constraints, lack of demand, concerns around the Dynamic provider, or something else?
-
For the no-reply group: are these teams actively building on Rootstock, or largely inactive?
This context will help the ecosystem determine whether limited DApp traction is primarily a wallet issue, an ecosystem maturity issue, or a BD execution issue.
More broadly, granular visibility into DApp outreach efforts increase the learning value of this work for the ecosystem.
2) User data and engagement
The M2 retention data showed some encouraging signals—a 9-day median return gap and 35 users active after 4+ weeks. For M3, it would be valuable to go deeper, especially given the promotional mix used for acquisition.
The launch included:
-
Badge mint (738 mints)
-
AMA
-
X campaign
-
Email newsletter to 300K+ subscribers
It would be useful to read you insights based on the data regarding conversion and engagement:
-
Badge-driven acquisition often results in one-time engagement. Are there insights on how the 738 badge minters behaved relative to the 1,694 total users?
-
A 300K newsletter yielding 1,694 users suggests relatively low conversion—any insight into audience mismatch (Rootstock vs. Blockscout subscribers) or whether the wallet proposition didn’t resonate broadly?
For the M3 report, it would be especially valuable to connect acquisition → behavior → retention. Some thoughts:
-
Can badge minters be segmented from organic users in retention metrics?
-
Do returning users skew toward specific acquisition channels?
-
What actions are returning users taking—transactions, or just logins?
Ultimately, these are insights to understand the cost per acquired user vs. cost per retained user. Again more granular data on user journeys and engagement metrics would significantly increase the value of the report, helping the ecosystem understand not just how users were acquired, but what actually drives retention.