Proposal: Mexico Local Node

Global Community
,
21

GM Scroll fam! :nerd_face:

Really stoked to read this proposal. Big respect to the team behind it :heart_hands:
This feels like the kind of initiative that could actually change the game if done with care and patience.

Wanted to drop a few thoughts from my perspective, as someone working in org design and coordination, and currently applying to join the node as a founder (yep, I already filled out the form and had the convo with @HumbertoBesso).

On identifying founders & builders

Spotting real potential is about reading context, motivations, and depth of commitment. That kind of filtering requires a human approach. I really think we need to bet more on people who are obsessed with the problem they’re solving, not just the tech they’re using.

On local+vertical specialization

There’s plenty of talent in Mexico to justify a vertically-specialized + locally-rooted cohort.
And doing it local creates bonds between founders, between mentors, between projects. That’s what makes an ecosystem feel alive. Global mentors are great, but only as a second layer. Local-first builds culture and long-term resilience.

On hackathon winners vs founders

Hackathon winners = great talent, fast execution, short feedback loops. But often motivated by exposure or prizes. Founders = long-term obsession, higher emotional investment, deeper resilience. That is way more skin in the game. If we’re talking long-term bets, my chips are on the founders.

On the 1-year Scroll commitment

IMO, that’s not a red flag; that’s raising the bar for both .
It filters for founders who are serious about building with Scroll, not just on Scroll. People who resonate with the mission and are down to commit. But it also demands that Scroll do its part.

No-equity is already huge win, as long as Scroll brings real support, visibility, and follow-through.
In other words, it’s not about locking people in, it’s about building mutual commitment.

In the age of situationships, offering real commitment can be a differentiator with other protocols.
In my case, I’m a little tired of taking the merch-photo for the hackathon (when there’s no real connection behind it nor interest in developing it).

Super excited about where this can go.
Thanks for opening the door.

:victory_hand:

2 Likes
22

Thank you for this thoughtful first-stage proposal. We would like to point out that the budget of $36,00 exceeds the $30,000 max budget that is provided in the Local Nodes Framework. We understand that this budget may be justified, which is why as a verified delegate, we feel comfortable endorsing this proposal.

2 Likes
23

Hello @HumbertoBesso,

Scroll Foundation considers this proposal ready for vote.

Observations to consider for the execution of the Local Node:

  • Our team would like to assist in the refinement of the educational content.
  • We will be supporting in the setup of operational tracking tools.
  • Social media amplification will be done through Scroll official channels.
  • We encourage the Local Node to participate on all Community activations lead by Scroll, engage with social media, and partake in initiatives through various community channels.

cc @eugene

1 Like
24

This is the actual proposal, the first one of this forum thread is about Mexico as a good place to launch.

25

Thank you @404Gov for the support!!

We modified the proposal to $30K for 3 months as it was suggested by other comments. The proposal went through refinement thanks to comments and discussions. You can check the final one here

1 Like
26

Hi @HumbertoBesso,

Thank you and your team for putting together this thoughtful and detailed proposal for a Mexico Local Node. It’s encouraging to see such proactive community initiative.

The proposal is comprehensive, and I’m particularly enthusiastic about the “mobile local node” concept for broader outreach.

The main point that gives me pause is the “build exclusively on Scroll for at least one year” clause. While I understand the intent to foster deep engagement with the Scroll ecosystem, it does bring up practical considerations:

  • Enforcement & Monitoring: How would this exclusivity be practically monitored and enforced without becoming overly burdensome?
  • Ethos Alignment: In a Web3 space that often champions interoperability and open-source contributions, how does long-term, mandated exclusivity fit?
  • Flexibility for Founders: What if a project organically discovers strong synergies with another (perhaps complementary) ecosystem, especially if their codebase is open source?

I see this as a “yellow flag” – an aspect to observe and learn from – rather than a deal-breaker for this initial pilot. The relatively short 3-month experimental period makes it a lower-risk way to test this model.

Ultimately, the success of this Local Node will hinge on the tangible value it delivers to founders and, by extension, to the Scroll ecosystem. If the support, mentorship, and access provided are truly exceptional, the exclusivity aspect may naturally become less of a concern for participants.

As a verified delegate, I am happy to support this proposal. Mexico is indeed a vibrant and rapidly growing Web3 market, as your proposal clearly outlines, with significant potential for Scroll. I also commend the proactive approach of establishing a presence where the community is actively seeking engagement, even if it wasn’t on the immediate roadmap. This responsiveness is key.

Perhaps the learnings from this pilot, including feedback and outcomes related to the exclusivity clause, can provide valuable insights for Scroll’s broader Local Node strategy moving forward.

Wishing you and the entire Mexico Local Node team the best of luck with this!

1 Like
27

I thank the team for this proposal, unfortunately I feel I need to vote AGAINST as the concerns raised here have not been addressed

The program is trying to do too much and is hence spread too thin. The team lacks a seasoned person to manage the builder support program and with a budget of only $1,250/month I doubt any quality can be achieved.

I have often suggested there is significant risk with doing local programs that lack quality, instead of local nodes focusing on engagement and letting an online digital program focus on quality founder support.

I would be happy to support a more focused proposal.

28

As a verified delegate , we are voting AGAINST the proposal.

The Local Node model may introduce significant and recurring costs to Scroll without delivering tangible benefits to the network or the DAO. While it could increase the number of individuals engaging with the ecosystem, this does not necessarily translate into active users, applications, transaction volume, or revenue generation for the DAO.

Similar models, implemented under different names by other organizations, have historically failed to demonstrate clear, measurable results for the projects that funded them.

29

We, the Unicircle work group, believe this proposal is in the best interest of the protocol. It is indeed paramount to increase the number of local nodes across the globe and thus we are voting FOR this proposal.

1 Like
30

I voted FOR.

The team seems solid and well poised to execute. The curriculum looks like it’ll do a decent job of educating and onboarding new users. Eager to see metrics post program to see the effectiveness of this approach.

1 Like
31

The following reflects the views of L2BEAT’s governance team, composed of kaereste, @Sinkas, and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.

We are voting FOR the proposal.

A mobile “Scroll bus” that pairs local workshops with an online builder track is a creative and cost-conscious way to meet Mexico’s fast-growing Web3 scene, where it already gathers at universities, fintech hubs, and regional hackathons. The draft demonstrates real legwork, including identified partners, a clear 3-month route (CDMX → Puebla), and a curriculum designed to drive graduates toward Scroll Grants.

Our only request is clarity on how success will be measured. A short metrics table (events held, applicants, teams accepted, and grant applications submitted/approved) and a public mid-tour update enable delegates to track progress and help the node secure follow-on support.

As mentioned in the other local nodes proposals, we think these proposals shouldn’t have to go through a DAO-wide vote, and would instead be much more efficient if we assigned an individual or group to review them, with the DAO having a veto window.

1 Like
32

Another one on regional efforts that can meaningfully drive grassroots adoption. The focus on developer education, community-building, and bridging Web2 talent into Web3 is particularly aligned with what I’ve seen work well in other ecosystems.

Strong support from me—excited to follow how this unfolds and what insights emerge that might be applied to future nodes.

–-jensei

2 Likes
33

The Mexico Local Node proposal has successfully passed the June 2025 Voting Cycle. Find details on next steps here:

cc @HumbertoBesso

2 Likes
34

Pagoda voted FOR the proposal. I am excited to see it moving forward! I do have some questions about the logistical details, like who will be driving and managing the bus per schedule. However, I believe all will be available in the execution phase. Congratulations!

1 Like
35

Thank you all who participated in this proposal. We value from the bottom of our hearts the input that you gave us. We’ve been busy thinking through it, having calls and chats with delegates and founders, as well as from @Juansito.

We’ve updated the proposal with your inputs, the feedback received, and with the Foundation’s KPI package

A summary of the updates are the following:

  1. Calendar has been updated. We’ve set that our activities have begun today and will end on Sept 20th.
  2. Team members have been updated. Below you’ll find a summary of our hiring process.
  3. Budget has been updated to SCR. Also, it was redistributed following a detailed review of what would make more impact and also based on comments we received from delegates.
  4. KPIs have been updated and fused with the Foundations KPI package.

Additionally, today the KYC process was filled.

Below you’ll find the overview of the hiring process regarding the Builder Program Manager and the Social Media Manager, as well as some final comments.

Overview of the Hiring Process for the Builder Program Manager

  1. We initiated the search by reaching out to our tech-focused WhatsApp groups, announcing the opening for a specialist in startup incubation and acceleration. Interested candidates were asked to submit their CV and a letter of motivation.
  2. In parallel, we extended the search to two academic institutions to attract qualified profiles from their respective networks.
  3. From the initial outreach, we received three applications. Each candidate was asked to submit a brief case study outlining how they would approach the role. We proceeded to interview two of them.
  4. Subsequently, we published the opportunity on our social media channels, the one linked had 1,079 views. From these we got contacted by three individuals. One of them proceeded to apply formally.
  5. The applicant submitted a well-developed case and was invited for an interview. After careful evaluation, both @Dorian and I concluded that her profile aligned perfectly with the needs of the program and we chose her.

We are pleased to introduce @Aleinweb3 as part of the team. Her CV is found here.

Overview of the hiring process for the Social Media Manager

Brenda Magaña has been a volunteer for years in many projects I’ve led since college. She has gained professional experience in many areas including marketing, social media management, impact evaluation, and project management. Her CV is reachable here.

Her fresh perspective outside the crypto sphere alongside with the guidance of the rest of the team (crypto bros and sisters) will give us the advantage of producing content that reaches both crypto people and not-yet onboarded talent.

Final comments

Thank you again to everyone and specially to those trusting us your vote and the DAO’s funds to deliver a unique experience to grow the Scroll ecosystem and positively impact Mexico.

We will post updates soon here at the forum, at calls, and on our social media channels:
X & Insta: 0xUrbanika ; Anguloweb3
X: HumbertoBesso ; Solxpriestess ; Aleinweb3

3 Likes
36

Hi everyone! :waving_hand: I’m excited to introduce myself. I’m joining as Builder Program Manager for Mexico Local Node initiative.

My role involves designing the cohort program, coordinating mentors, and identifying allies who can add value to early-stage projects. I’ll also be supporting local activation in Mexico, connecting with communities to encourage founders and Web3 enthusiasts to start building within the Scroll ecosystem.

Looking forward to collaborating and helping more builders grow with Scroll! let’s make it happen :rocket: