[2603] Beexo BTCFi Grant – Criptovendimia 2026 - Failed
for - 2,392,020
against - 2,790,503
I believe what Rootstock needs most right now is users and activity.
The main bottleneck is still awareness. We won’t reach adoption if people don’t know Rootstock exists or understand what can be done with it. I still attend conferences where many participants are either unaware of Rootstock or unclear about its use cases.
The users I know who actively use Rootstock protocols report high satisfaction.
Conferences remain key to addressing this. While impact is not always easy to measure, they are one of the most effective ways to reach new users and drive onboarding, especially when combined with hands-on follow-ups, which we are working on with Vottum.
In that context, I find it difficult to understand decisions like the vote against supporting Cryptovendimia. This is an event with strong ties to the ecosystem, direct access to the audience, and clear opportunities to drive wallet usage and protocol adoption—all with a relatively small investment.
I would understand not supporting events where we lack reach or influence. But in cases like this—where there is a key ecosystem partner involved in the organization, an ambassador directly engaged, and a team strongly aligned with Rootstock—the decision becomes even harder to understand. These are precisely the kinds of teams that actively drive real adoption.
Apologies for insisting on this point, but I’ve been working on Rootstock user adoption for over 6 years, and I care deeply about what actually works.
In the past, Rootstock Labs has sponsored many events with significantly larger budgets, often focused on branding without strong activation or follow-up. Those efforts also typically required team travel, logistics, and coordination costs, which likely matched or exceeded the sponsorship itself.
In contrast, initiatives like this are effectively outsourcing execution to highly committed ecosystem partners, who are already aligned and focused on driving adoption. Not supporting them is, in my view, economically inefficient and strategically counterproductive.
If the expectation is to return to a more centralized model of execution, I believe that would go against the spirit of the Collective, which exists precisely to decentralize efforts and empower the ecosystem.
This is exactly the type of initiative we should be supporting—especially when it comes from proven contributors with years of involvement and commitment to Rootstock.
The goal should remain simple: make sure people know Rootstock exists, understand what they can do with it, and start using it.