Hey @jatinsahijwani, The HackTour India track record is genuinely impressive. 50+ events, 7,500+ attendees, 23 ecosystem partnerships. But at the same time, this track record can be a double-edged sword. Having delivered for Polkadot, Arbitrum, Avalanche, Aptos, Stellar and so many others, is this a community initiative built around a genuine understanding of Rootstock, or is it a proven playbook with Rootstock’s logo swapped in? I think the proposal in its current form leans toward the latter. There’s no mention of rBTC, merged mining, specific protocols live on the network, or any coordination with Rootstock Labs. If Rootstock India is going to be the ecosystem’s presence in the country, delegates need to see that the team understands what makes Rootstock unique as a Bitcoin L2, not just that it’s EVM compatible, as all the others.
On KPIs: The current success metrics are almost entirely vanity numbers. Telegram members, X followers, event headcounts. These are easy to acquire with campaigns and tell us very little about actual ecosystem impact. What matters is whether developers actually build on Rootstock after engaging with your initiative. I’d want to see conversion-oriented KPIs like testnet-to-mainnet deployment rates, developer retention 30 days post-event, or GitHub contributions to Rootstock projects. The bounty design has the same issue. “50 on-chain testnet deployments” sounds impressive but a test contract can be deployed in five minutes. What’s the quality bar?
On Devcon Mumbai 2026: The proposal ends in July but Devcon Mumbai is November. That’s a 4-month blackout right when momentum should be peaking. If Devcon is the strategic justification for launching now, the narrative should account for how the community stays active through that period, even if this specific grant only covers April through July.
On process: Submitting this on-chain before the forum discussion has had time to develop is not standard practice in any DAOs. Proposals benefit from a few weeks of delegate feedback and iteration, it builds stronger support and results in better outcomes. I’d suggest planning spending 3 to 4 weeks incorporating feedback, and resubmitting a tighter version. The potential is clearly there, the execution plan just needs refinement to match it.