Proposal: Argentina Local Node Proposal by Buidlers

:argentina: :rocket: Buidlẽrs Proposal – Builder Activation Program for Privacy & Autonomy-First Consumer Products

Cover Letter

In an era demanding digital autonomy & privacy, Buidlẽrs Realm stands at the forefront of innovation, fusing Web3 and AI to forge a more sovereign digital future. We are thrilled to partner with Scroll on a shared mission: to empower the next wave of builders dedicated to creating privacy-preserving, user-sovereign technologies.

Our shared goal is to cultivate a builder-first ecosystem where developers craft privacy-preserving, user-sovereign technologies, deeply aligned with the values of decentralization and transparency. Scroll’s commitment to empowering developers and promoting user sovereignty perfectly mirrors our own.

Through this partnership, Buidlẽrs Realm will nurture new projects, leveraging Scroll’s advanced technology to champion privacy, autonomy, and decentralization as core principles.

We are motivated by the opportunity to help grow Scroll’s ecosystem through an incubation program that puts builders first. This program will provide mentorship, resources, and community support to developers focused on privacy & autonomy-first products – decentralized applications where users retain control over their data and digital interactions. In collaboration with Scroll DAO, we intend to cultivate a cohort of innovators who will build on Scroll’s Layer-2 solution and demonstrate the power of Web3 to address pressing issues of centralization and privacy erosion. We are confident this partnership will not only yield impactful MVPs on the Scroll network but also significantly strengthen Scroll’s builder community, solidifying our shared commitment to decentralization, privacy, and user sovereignty. We appreciate the consideration of Scroll’s delegates and community, and look forward to the possibility of working together to accelerate a builder-first culture and a more sovereign digital future.

Summary

We propose a 12-week online incubation program designed to help builders create privacy-focused decentralized apps on the Scroll network. We are requesting S₵R 110,000 to run this program. This initiative will collaboratively engage talented builders, experienced mentors, and the Scroll DAO community, driving tangible outcomes. The program will deliver 10 minimum viable products (MVPs), grow the Scroll builder community, and promote the adoption of Scroll’s technology. Ultimately, this program will directly accelerate Scroll’s ecosystem growth by empowering developers with essential guidance and resources, leading to the deployment of new dApps on Scroll and a fortified builder-first culture.

Motivation

Challenges and Opportunities in Activating Builder-First Communities

Engaging builders in nascent ecosystems demands more than just robust infrastructure; it requires deep emotional resonance, cultural adaptability, and unwavering support. This proposal directly addresses common pain points with a deliberately designed program.

Pain Points in Outreach

  • Lack of visibility in emerging ecosystems: Limited visibility in emerging ecosystems: Many talented builders remain unfamiliar with, or even skeptical of, new blockchains.".

  • Uninspiring or generic narratives: Uninspired or generic narratives: Messaging that lacks emotional or technical depth fails to capture true builder interest.

  • Mismatch with local/regional contexts: Programs that don’t reflect cultural or technical realities (e.g., LatAm, Asia) struggle to connect.

  • Competition with better-known blockchains: Ethereum, Solana, Base, and others dominate attention unless differentiation is clear.

Pain Points in Program Execution

  • Lack of structured milestones and follow-up: Without clear stages and deliverables, builders lose direction.

  • Shortage of accessible, high-quality mentors: Without strong technical and human support, teams stall.

  • Difficulty maintaining momentum: Without consistent rituals, the builder’s enthusiasm can fade.

  • Weak feedback processes: Without specific, timely feedback loops, progress is hindered.

Pain Points in Motivation and Inspiration

  • Lack of real success stories: Builders need role models and credible pathways.

  • Missing emotional and symbolic incentives: Programs that are purely technical lack soul—gamification, storytelling, and identity help drive energy.

  • No human connection: Real community is key to builder longevity.

Opportunities We Embrace

  • Pedagogical interpretation of the stack: Translating the stack: Making the Scroll tech stack profoundly understandable, exciting, and practically useful.

  • Translation/localization of resources: Clear, accessible documentation across languages.

  • Real stress testing of protocols: Builders discover and improve tools through real use cases.

  • Builder-centric narratives: Crafting builder-centric narratives: Speaking the language of vision and tools, not just KPIs, to truly resonate with innovators.

  • Spotting and supporting high-potential founders: Early detection and strategic support.

  • Fostering collaboration: Encouraging team blending, idea sharing, and common problem solving.

  • Creating community culture: Building a builder-first identity for the Scroll ecosystem.

  • Designing experiential learning journeys: Generating excitement and mastery through lived experience.

In an era where centralized digital platforms erode user sovereignty and stifle innovation, Buidlẽrs Realm is committed to flipping this paradigm. We will ignite Scroll’s builder ecosystem, guiding developers to forge real, usable Web3 products that directly challenge the centralized status quo.

This program fosters:

  • A culture of open experimentation with Scroll technology

  • A builder-first narrative, grounded in local relevance and emotional connection

  • Clear pedagogical structure and community rituals that maintain engagement

  • Real stress-testing of Scroll tools in the hands of committed builders

No conflicts of interest exist. All parties involved share the mission of empowering builders and communities.

Base 0: Why Scroll?

As a foundational moment of alignment, each of our mentors and participants will be invited to reflect on the central question: “Why Scroll?”. These collective reflections will articulate why Scroll is the ideal home for privacy-first, autonomy-centered builders, exploring themes such as:

  • Scroll’s technical commitment to zkEVM scalability with integrity Its alignment with builder-first values over VC-first incentives

  • The importance of transparent, community-owned infrastructure

  • The clarity and usability of Scroll’s documentation and stack

  • The feeling of building in an ecosystem that values ethics and experimentation

We believe this exercise will root every team’s process in a shared sense of purpose, and anchor the program in the deeper cultural mission of Scroll.

Scroll’s Track Record in Argentina

Our existing relationship with Scroll highlights their strong commitment to grassroots innovation. Scroll was the main sponsor of the “Level Up Hackathon” — organized in collaboration with Buidlẽrs — held during Ethereum Argentina 2024, which brought together over 60 teams. Among the winning projects was ChatterPay, a WhatsApp-based smart wallet leveraging AI and account abstraction to simplify blockchain interactions. ChatterPay not only took first place in both the general and Scroll tracks, but was also selected for the first cohort of the Scroll Open Campus in Malaysia (2025), where it continues to actively collaborate with the program. This clear follow-through — from sponsoring local hackathons to supporting long-term builder growth globally — demonstrates Scroll’s genuine dedication to ecosystem development and sustainable innovation in Latin America and beyond.

Execution

Operational

Program Structure: The Builder Activation Program will run for 12 weeks and is structured in three phases to systematically guide teams from identity and idea to prototype and pitch:

Phase 1 – Identity & Foundations (Weeks 1-4): This phase focuses on inspiration, alignment, and creating strong personal and project foundations. Workshops include vision and purpose setting, personal branding for builders, community building, and foundational legal and financial setup for Web3 ventures. Teams will define their purpose, brand, legal form, financial planning and complete:

  • Builder Purpose Statement

  • Personal Brand & Elevator Pitch

  • Legal Setup Preliminary Plan

  • Financial Security Plan

Phase 2 – Validation, Iteration & Building (Weeks 5-8): Builders will validate real user problems and rapidly prototype solutions. Modules include value proposition design, early user acquisition strategies, storytelling and pitch training, as well as experimental coding sprints (Vibe Coding Sessions). Deliverables include:

  • Value Proposition Canvas

  • Growth Strategy + Whitelist Plan

  • 3-minute Pitch Recording + One Liner

  • MVP or Basic Prototype

Phase 3 – Scale & Present (Weeks 9-12): Builders will prepare for Demo Day through team building, agile collaboration, and economic modeling (tokenomics if applicable). The phase culminates in a final live pitch and demo. Workshops include hiring, token design, and pitch deck crafting. Deliverables include:

  • Team & Collaboration Plan

  • Token Canvas + Economic Model (if applicable)

  • Final Pitch Deck

  • Live Pitch & Functional Demo

Personnel & Resources

A dedicated and experienced team will carry out this program to maximize its chances of success. Key roles and responsibilities include:

  • Program Lead (1 person, Buidlẽrs Realm) – The Program Lead will be the driving force behind the 12-week program, ensuring seamless coordination and delivery.

The Program Lead will be responsible for overall coordination and delivery of the 12-week program. This includes planning the curriculum and schedule, onboarding participants, moderating weekly meetings, and tracking each team’s progress. The Program Lead will serve as the primary point of contact between Buidlẽrs Realm and Scroll DAO, providing updates as needed. They will also ensure that the program’s objectives (building privacy-first products on Scroll) remain on track throughout the cohort. In practice, the Program Lead will facilitate mentor-team interactions, handle any conflicts or issues that arise, and drive the evaluation process (collecting metrics and feedback). This role requires strong project management skills, familiarity with Web3 development (to understand projects’ technical needs), and alignment with the mission of decentralization and privacy. We have identified a Program Lead within Buidlẽrs Realm who has prior experience running Web3 hackathons and a background in product management.

  • Mentors (5-6 people, external experts) – Our curated roster of 5-6 expert mentors will provide invaluable guidance and domain expertise, acting as critical enablers for each team.

A roster of mentors will be assembled, comprising experienced builders, subject-matter experts, and Scroll ecosystem contributors. Each mentor will be assigned to one or more teams to provide guidance and domain expertise. Their responsibilities include: hosting at least one workshop or AMA session in their area of expertise, offering weekly feedback on team updates, and being available for ad-hoc advice during office hours. We plan to recruit mentors with diverse specialties relevant to our focus – e.g. a smart contract engineer (expert in Solidity and Scroll’s zkEVM), a UX designer with experience in privacy-centric design, an AI specialist for teams incorporating AI, and perhaps a Web3 entrepreneur who can guide on product strategy. Mentors will help ensure that each project follows best practices (security reviews, proper use of decentralized storage, compliance with data privacy principles, etc.) and that the teams stay motivated and make consistent progress. We will prepare guidelines for mentors to clarify the expected time commitment (for example, ~2-3 hours per week) and to streamline communication (possibly a private Discord channel for mentors to coordinate and share notes on teams). By tapping into Scroll’s community and Buidlẽrs Realm’s network, we have already identified several strong mentor candidates keen to support this program.

  • Technical Support (1-2 people) – Technical Support will serve as the on-call technical bedrock, ensuring no team falters due to technical roadblocks, especially concerning the Scroll stack.

The Tech Support personnel are essentially the “on-call” experts for any technical difficulties teams face, particularly with respect to the Scroll stack or integrating privacy technologies. These individuals will likely be developers from Buidlẽrs Realm or the Scroll community who are deeply familiar with Scroll’s architecture (zkEVM, network endpoints, tooling) and can troubleshoot smart contract issues, performance bottlenecks, or deployment problems. They will set up dedicated support hours (e.g., certain evenings or weekends if needed) where teams can hop on a call for debugging. They might also contribute code reviews or security audits for the teams’ smart contracts to ensure quality. Having Tech Support ensures that no team stalls out due to a technical roadblock – any critical issue can be escalated and resolved with expert help. Additionally, this role will help maintain documentation of common issues and solutions encountered during the cohort, which can be fed back into Scroll’s developer documentation for the benefit of the broader community.

In addition to these primary roles, we will leverage existing resources wherever possible. For example, we plan to coordinate with Scroll’s own developer relations team (if available) to ensure our participants have access to the latest info and support from Scroll’s side (e.g., testnet faucets, technical docs, etc.). We may also invite guest speakers (such as privacy researchers or Web3 founders) for one-off talks – while not formal mentors, they are a resource to inspire and educate the builders. Any guest session will be arranged in collaboration with the Program Lead and likely will not require additional funding beyond perhaps a small honorarium. All program staff and mentors will be onboarded with an orientation so that everyone understands the tools (Notion, Discord) and the workflow. We will maintain a clear division of responsibilities but also encourage the team to collaborate – for instance, the Program Lead and Community Manager will work closely to address any participant concerns, and mentors and Tech Support will share insights to help teams holistically. In summary, we have assembled a capable team with the right mix of project management, technical expertise, mentorship experience, and community skills to ensure the program runs smoothly and achieves its goals.

Financial

The total funding requested for this 12-week program is $30,000 USD, which will be received and managed in SCR tokens through the Scroll DAO (approximately 110,300 SCR at the current exchange rate, to be finalized at time of funding). Below is a detailed breakdown of the budget, with subcategories in USD and an approximate equivalent in SCR:

  • Program Personnel – $19,500 (≈71,700 SCR): This category covers the compensation for the core team running the program.

    • Program Lead: $4,500 (≈16,550 SCR) – for three months of full-time coordination and oversight. This reflects a monthly rate of $1,500 given the seniority and critical responsibility of this role.

    • Technical Support: $6,000 (≈22,060 SCR) – allocated for 1-2 technical experts. This could be split, for example, between two part-time support developers at $1,000 each monthly, to be on-call throughout the program.

    • Mentor Stipends: $9,000 (≈33,090 SCR) – to reward the contributions of 5-6 mentors. We anticipate offering an average stipend of ~$1,500 per mentor for the 12 weeks, plus a small buffer for any additional specialist consultations or a bonus for particularly active mentors. This ensures we can attract high-quality mentors and acknowledge their time commitment. (If certain mentors volunteer without pay due to passion for the cause or affiliation with Scroll, any unused portion of this budget would be returned to the DAO or reallocated to other program needs with DAO approval.)

  • Participant Support & Events – $9,000 (≈33,090 SCR): We propose a budget to directly support participants and enhance program outcomes.

    • Builder Stipends/Prizes: $6,000 (≈22,060 SCR) – A pool to incentivize and reward the participating teams. For example, we could provide a completion stipend of $1,000 to each team that successfully builds an MVP and presents at Demo Day. Alternatively, part of this could be structured as small prizes for standout projects (such as an extra $2,000 for the top project, $1,000 for runner-up, etc., as decided by a judge panel or community vote). This financial incentive is modest but meaningful – it helps teams cover costs during development (or continue development after the program) and signals Scroll DAO’s investment in their success.

    • Demo Day & Community Events: $3,000 (≈11,030 SCR) – While the program is online, we will invest in making the experience polished and engaging. This budget covers any production costs for the Demo Day event (e.g., professional video editing for demo reels, design work for presentation materials, or high-capacity Meet webinar licenses if needed). It also allows for sending swag or celebration kits to participants (as a reward, we could mail T-shirts or stickers for Scroll and Buidlẽrs Realm to the teams). Additionally, we may use a portion to promote the program’s achievements (for instance, a small budget for social media promotion of Demo Day, or hosting a community giveaway to attract attendees). These efforts will raise the visibility of both the projects and Scroll’s ecosystem.

  • Operational Expenses (Tools & Overhead) – $1,500 (≈5,515 SCR): This covers the miscellaneous costs to run the program infrastructure.

    • Contingency & Miscellaneous: $1,500 – A buffer for unforeseen expenses. This could include additional mentorship sessions if teams need extended support, content creation (like commissioning a technical writer to document the best projects for a case study), or other minor operational costs that weren’t initially anticipated. We will maintain transparency on how this contingency is used; if unspent, it can remain in DAO treasury or be returned. (Software Licenses, Infrastructure & Testing)

In summary, the $30,000 budget is designed to be comprehensive yet lean, ensuring all critical aspects of the program are funded. We have prioritized spending on human capital – the people (program staff, mentors, and participants) – as that is the key driver of the program’s success. The amounts were estimated based on fair compensation for effort and competitive rates in the Web3 industry to attract talent, while also reflecting the part-time nature of some roles. We will handle funds in a transparent manner: Buidlẽrs Realm can receive the SCR and disburse payments to team members and mentors according to the above allocations, with records available for DAO review upon request. If the SCR price fluctuates significantly, we will adjust the SCR amounts to ensure the USD values of compensation remain roughly as budgeted (we can peg at the value at time of approval). Any unused funds (for example, if a mentor declines a stipend or contingency isn’t spent) will either be returned to the Scroll DAO treasury or rolled over to a future cohort, subject to DAO’s guidance. This lean yet comprehensive budget is meticulously designed to effectively fuel the program, providing essential support to participants and staff, and ultimately delivering tangible, high-impact results for the Scroll ecosystem.

Budget Monthly

Budget Details

Evaluation

To ensure maximum impact and accountability, we’ve defined clear, measurable outcomes and success metrics for the Builder Activation Program. Our overarching goal is to cultivate a new cohort of Scroll-based builders who will deliver viable, privacy- and autonomy-focused applications, significantly advancing both the Scroll ecosystem and the broader vision of a user-sovereign web. We will measure success across several dimensions:

  • Product Outcomes (MVPs Developed): A primary metric of success is the number and quality of projects that reach MVP stage by the end of the program. We aim for 5-8 completed MVPs (for a cohort of roughly that many teams) as a tangible output. Success means each of these MVPs is functional and demonstrates a solution to a real problem in privacy/autonomy (e.g., a decentralized application with a working smart contract on Scroll and a front-end interface). We will track how many teams meet their planned milestones and launch their product on Scroll’s testnet or mainnet. Metric: # of projects that deploy a dApp on Scroll by program’s end (target: >5). Beyond the raw count, we will qualitatively assess the impact of each MVP – for instance, does it have a novel approach to data privacy, or potential for real user adoption? We will gather feedback from Demo Day judges and users to gauge each project’s viability.

  • Scroll Ecosystem Adoption: The program’s success is also reflected in how it drives usage of Scroll’s technology. We will monitor tooling and network usage by participants. Metrics: number of smart contracts deployed on Scroll by the cohort’s projects; number of transactions or interactions on Scroll testnet/mainnet generated during development and testing; any Scroll-specific features (like zkEVM proofs or Scroll APIs) utilized in the solutions. A successful program should see each project deeply integrate with Scroll (i.e., not just theoretical ideas, but actual contracts and activity on Scroll). We set a goal that at least X% of the cohort’s projects continue to run on Scroll after the program (for example, 6 months later, they are still live or have progressed to mainnet and actual users). We will stay in contact to track this continuation metric. Additionally, we’ll look at whether any project goes on to secure further funding through Scroll’s Ecosystem Fund or other grants – a sign that the DAO and community see value in what was built.

  • Builder Community Growth: A less tangible but equally important outcome is the expansion and engagement of the builder community around Scroll. We will measure how the program affects community metrics. Metrics: the number of developers who actively participated (target ~20 individuals across teams and mentors) and how many new members join Scroll’s developer channels as a result. For example, we will track the increase in membership or activity on the Scroll Discord/Forum attributable to the program (did we see new introductions, project updates, questions in Scroll’s dev channels coming from our cohort?). We also consider retention: do the builders remain involved in the Scroll community after program completion? A success indicator would be, say, at least 80% of the participants remain active (continuing their project or contributing to others on Scroll) 3 months after the program. We will follow up with alumni to see if they become long-term Scroll advocates. Another metric is community content produced – for instance, did participants write tutorials, blog posts, or talks about building on Scroll? Such outputs amplify Scroll’s reach and are a positive outcome we will encourage (possibly by highlighting them in the program).

  • Participant Satisfaction and Skill Growth: We will evaluate how satisfied and empowered the builders and mentors felt through the experience. Using surveys and feedback forms, we’ll collect a Net Promoter Score (NPS) or similar metric from participants at program’s end – essentially asking “How likely are you to recommend this program to other builders?” and “Did this program meet your expectations?”. We aim for a high satisfaction rating (e.g., NPS > 50 or an average satisfaction of 8/10 or above). We’ll also ask participants to self-assess their skill improvement and confidence in building Web3/privacy tech after the program. If most indicate significant improvement, that’s a success indicator that we delivered educational value. Similarly, mentor feedback will be gathered to see if they found the engagement fruitful and if they observed meaningful progress in teams.

  • Quality of Solutions (Privacy & Autonomy Impact): Since our focus is on privacy and autonomy, we will evaluate the qualitative impact of the solutions in those terms. This involves checking if each project actually implemented privacy-preserving features (for example, encryption of user data, zero-knowledge proofs, decentralized storage of personal info) and if the design choices enhanced user autonomy (such as giving users control over their data sharing preferences). We might measure this via a simple rubric or checklist during Demo Day judging – e.g., “Project uses decentralized identity (yes/no)”, “No central server for critical functions (yes/no)”, “User can export/delete their data easily (yes/no)”. Achieving a strong score in this rubric for the majority of projects would mean the program stayed true to its ethos. It’s not just about having working apps, but that those apps align with the privacy-first, user-sovereign principles we champion.

To track these metrics and outcomes, Buidlẽrs Realm will maintain an evaluation log. This will include: weekly progress data (from reports on Notion), a final report from each team (including their own reflection on what they achieved), and statistics like contract deployments on Scroll (we can use blockchain explorers and analytics to count those). We will prepare a Post-Program Report for Scroll DAO summarizing all the results and metrics above. This report will be shared on the governance forum within a few weeks after the program ends. It will highlight key achievements (e.g., list of MVPs with short descriptions and links, community growth numbers, participant quotes). It will also candidly discuss any shortfalls relative to targets and lessons learned for next time. By defining success metrics from the start and collecting data throughout, we ensure accountability to Scroll DAO and the ability to demonstrate the ROI of this growth proposal. Ultimately, the success of this Builder Activation Program will be unequivocally demonstrated through a robust combination of quantitative data (e.g., deployed projects, user engagement, transaction volume) and compelling qualitative evidence (e.g., participant testimonials, documented skill growth, and strengthened community sentiment). We are confident this program will make a profoundly meaningful difference.

Conclusion

In conclusion, the Buidlẽrs Realm Builder Activation Program represents a pivotal strategic investment in Scroll’s ecosystem and community, poised to deliver significant, compounding benefits for all stakeholders. We have outlined a comprehensive plan to nurture a cohort of builders who will create new privacy- and autonomy-first applications on Scroll. By funding this program, Scroll DAO will not only gain innovative MVPs—each expanding Scroll’s use cases and demonstrating real-world utility—but will also cultivate the next generation of dApps and startups within its vibrant ecosystem. This directly contributes to Scroll’s growth by attracting more developers and end-users to the platform. Moreover, the program will grow the builder community: participants, mentors, and supporters will form lasting bonds and continue contributing to Scroll long after the 12 weeks, reinforcing a virtuous cycle of innovation. The program also serves as a public testament that Scroll values decentralization and user sovereignty in practice – we are not just talking about these ideals, but actively enabling teams to build real solutions embodying them.

For the builders involved, this collaboration offers an unparalleled opportunity: access to mentorship, resources, and a supportive network that will accelerate their projects and personal development. We expect many of these individuals to become ambassadors of Scroll’s technology, sharing their positive experience and know-how with others. In the long run, an engaged and skilled developer base is one of the greatest assets a Layer-2 network like Scroll can have.

This initiative perfectly embodies Scroll’s core values and mission: to build an open, inclusive, and permissionless ecosystem where innovation thrives. By empowering this diverse group of innovators to tackle the critical challenges of centralization and privacy erosion, we invite Scroll DAO to join us in shaping a more autonomous and user-sovereign digital future; It reinforces Scroll’s commitment to being a builder-first, community-driven platform – much like Ethereum’s culture that has made it successful, Scroll is cultivating a culture where developers are supported and celebrated as the engine of ecosystem progress.

There is also a broader impact to consider: by focusing on privacy and autonomy-first products, Scroll DAO will be championing the cause of user-centric technology at a critical time. The solutions that emerge from this program could become showcases for how Web3 can protect users where Web2 failed – whether it’s a decentralized social media platform that gives users control over their data, or an identity solution that preserves privacy by default. These success stories will enhance Scroll’s reputation as not only a technical powerhouse but also a values-driven community. This alignment with principles of decentralization, privacy, and user sovereignty is not just philosophically satisfying, it is increasingly a competitive advantage as users demand more from the products they use.

To summarize the key points: We request $30,000 (≈110,300 SCR)[1] to run a 12-week builder activation program that will yield new Scroll-based dApps, empower developers, and grow the community. We have a clear execution plan with defined roles, a reasonable budget, and metrics to measure success. No conflicts of interest exist – our only interest is in advancing the Scroll ecosystem and Web3 innovation. We believe that the return on this investment will be seen in the months and years to come: through the new projects that flourish, the developers who become long-term contributors, and the continued momentum of Scroll as a leading zkEVM network. We conclude by reiterating our enthusiasm to partner with Scroll DAO on this initiative. Together, we can cultivate a generation of builders who will carry forward the values of decentralization, privacy, and user empowerment. Buidlẽrs Realm is committed to making this program a success, and we are confident that with the DAO’s support, we will accelerate Scroll’s builder-first culture and drive meaningful growth for the community. Thank you for considering our proposal. We are excited at the prospect of collaborating to build a more autonomous and privacy-preserving digital realm on Scroll.


  1. ~U$D 30.000,- at ~$0.272 USD/SCR -16/06/2025- ↩︎

5 Likes

As co-founders of ChatterPay, we’re incredibly excited to express our full support for the “Builder Activation Program for Privacy & Autonomy-First Consumer Products” proposed by Buidlẽrs. This initiative resonates deeply with our journey and vision for a thriving, builder-centric Web3 ecosystem.

ChatterPay is a testament to the power of localized, community-driven innovation within the Scroll ecosystem. Our project, a WhatsApp-based smart wallet leveraging AI and account abstraction, was born out of a coordinated effort between Buidlẽrs and Scroll at the Eth Argentina 2024 hackathon. We were honored to not only secure first place in both the general and Scroll tracks, but also to be selected for the inaugural cohort of the Scroll Open Campus in Malaysia (2025). This experience, as a local Argentinian team participating in a global program, has given us firsthand insight into the immense value of programs like the one Buidlẽrs is proposing.

The challenges outlined in the proposal—such as the need for increased visibility in emerging ecosystems, culturally adaptable programs, and robust mentorship—are precisely what we’ve encountered and what this program aims to address. We believe that focusing on privacy and autonomy-first consumer products on Scroll is crucial for fostering a truly user-sovereign digital future.

Should this proposal be approved, the ChatterPay team is committed to actively assisting and supporting every phase of its implementation. We are eager to lend our experience and collaborate to bring more talented founders to Scroll, making Latin America a vibrant hub for incubation within the Scroll ecosystem. We believe that by nurturing local talent and providing them with the right resources and mentorship, we can collectively drive significant growth and innovation on Scroll.

We are confident that this program will not only yield impactful MVPs but also significantly strengthen Scroll’s builder community, solidifying its shared commitment to decentralization, privacy, and user sovereignty.

3 Likes

Hey everyone,

We wanted to reach out regarding the proposal we posted recently. We’re really excited about the ideas we’ve shared and believe they could bring some great improvements.

We haven’t received much feedback yet, and we’d love to hear your thoughts! Your input is incredibly valuable to us as we work to make this proposal the best it can be. Whether you have suggestions, concerns, or just want to voice your support, please don’t hesitate to share.

Let’s work together to shape this! We’re looking forward to a lively discussion.

Thanks,

2 Likes

Hi! @Buidlers

Thanks for sharing your proposal. Reaching out to delegates personally could also be a good idea to get more feedback on the proposal. Just fyi, tomorrow we will have two DAO calls, so if it’s helpful, happy to allocate some time for you to present your proposal.

2 Likes

Thanks for your proposal!

I have a question/suggestion: Why focus solely on privacy and autonomy? While those are really important topics, you are aiming to deliver at least 5 MVPs, and the topic seems to narrow to allow real differentiation between them, no?

Maybe it is a good idea to expand the scope a bit, so you guys can attract more builders interested in trying Scroll’s tech stack, and also make the proposal more appealing.

1 Like

Hi! Thank you very much for your message and suggestion :raising_hands: We would love to join the DAO call tomorrow to present the proposal and receive feedback. Would it be possible to allocate us a few minutes during the afternoon session?

Let us know what time works best for you and we’ll be there!

2 Likes

Yes, no problem, see you there!

1 Like

Hello! Great point, you’re absolutely right and thank you for the suggestion.

We can definitely clarify that the scope is not limited to privacy & autonomy. While those are core themes we care about and want to highlight, the goal is to support a broader range of projects that showcase Scroll’s capabilities. Expanding the scope makes a lot of sense to bring in more builders and ensure there’s enough room for variety and differentiation across the MVPs.

We’ll make sure to update the proposal to reflect this more clearly.

3 Likes

Really appreciate the clarity of this proposal; the twelve-week curriculum is sharp, and what stands out most to me is that it’s built around a vertically focused growth initiative that clearly differentiates it from other proposals (privacy and autonomy-first consumer products). Scroll needs more “depth over breadth” experiments like this.

A few thoughts to help tighten the fit with the Local Node framework. Since the program is 100% online, it risks losing the “Argentina” identity that gives regional nodes their unique value. If all sessions are remote, why limit participation to Argentina at all? One option might be to prioritize an Argentine cohort but open surplus seats to the broader LatAm community (or even globally if the language is English) while still reporting Argentina-specific impact separately. That would preserve community grounding while maximizing reach.

Second, I’d recommend mapping the program more clearly to the Open Economy funnel. My understanding is that a key purpose of Local Nodes is to act as feeders into Scroll Open → Open Economy → Campus. Could you add explicit milestones tied to that pipeline? For example: 200 builders CRM-tagged → 30 complete Open Economy applications → 10 accepted into Open Economy. This matches your MVP goal nicely, and a simple dashboard would make tracking outcomes transparent.

Finally, given the dense calendar of IRL events in Argentina leading up to Devconnect (Gira SEED, Aleph Hub, satellite hackathons, side events, etc) I’d really like to see this proposal include at least one in-person activation. A privacy-focused Build Weekend, watch party, or workshop in Buenos Aires would let you recruit talent and make Scroll visible to builders who are already plugged into the scene, without needing a major budget expansion.

If I’ve misunderstood any limitations (language, logistics, budget) happy to be corrected. But I’d love to see the next iteration include (i) a clearer Open Economy pathway, (ii) a local IRL component, and (iii) the option to open seats to more of LatAm. This proposal is already on strong footing, these additions would make it even stronger.

3 Likes

gm @Buidlers,
Thank you for sharing such comprehensive, builder-focused plan for Argentina’s ecosystem. I can see a lot of thought went into its design.

My questions are similar to @0xDonPepe 's above. I think there will be a lot of excitement around the upcoming Devconnect, and I’m wondering if there’s a way to tap into that local enthusiasm around the big event.

I was also really impressed with the https://bringargentinaonchain.org/ movement, and I’m curious if there are other local organizations or programs that Scroll could partner with to enhance the impact of the local node program.

1 Like

Thank you @0xDonpepe for this thoughtful and encouraging feedback! We’re thrilled that you recognize and appreciate our “depth over breadth” focus. This approach, centered on privacy and autonomy-first consumer products, is a key differentiator for the program, though we certainly encourage a wide array of innovative projects beyond this specific area.

Expanding Our Reach Beyond Argentina

Regarding your point about the “Argentina” identity and participation: you’ve hit on a crucial consideration. While the program is indeed 100% online, our intention was to leverage the strong talent pool and community in Argentina. However, we completely agree that limiting participation solely to Argentina might inadvertently diminish reach. We propose to open participation to the broader LatAm community, and indeed globally. While the program will be conducted entirely in Spanish, builders from around the world are very welcome. We believe this approach will maximize reach while still allowing us to report on specific impact metrics related to the Argentine cohort, preserving community grounding as you suggested.

Clearer Pathways to Open Economy

Your recommendation to map the program more clearly to the Open Economy funnel is spot-on. We absolutely see this program as a vital feeder into the Scroll Open → Open Economy → Campus pipeline. We will explicitly incorporate milestones related to this pathway. We envision tracking metrics such as: # of complete Open Economy applications → # of accepted into Open Economy → # in Campus projects. We also agree that a simple dashboard for transparent outcome tracking would be highly beneficial. We’d be keen to work with you further in defining the tracking mechanism.

Integrating an In-Person Component

Finally, we appreciate your push for an in-person activation. We’re pleased to confirm that our proposal does include an in-person Demo/Pitch Day in Buenos Aires at the conclusion of the twelve-week program. This event is designed to allow participants to showcase their projects, connect with the local ecosystem, and foster direct engagement with the Argentine builder community. We’re also committed to exploring avenues to generate additional resources beyond the core budget to incorporate more in-person events throughout the program’s lifecycle. We believe this will serve as a crucial touchpoint for recruiting talent and increasing Scroll’s visibility among builders already plugged into the scene, aligning perfectly with your suggestion for a local IRL component.

Your observations are incredibly helpful for tightening the fit with the Local Node framework, and we’re happy to clarify and incorporate these suggestions.

We are confident that these additions will make an already strong proposal even more impactful, and we’re excited to iterate on these points with your continued guidance.

2 Likes

I’m not seeing who the team is who can execute this well. Mentoring builders can lead to VERY underwhelming outcomes if not done with excellence. Does the team have significant experience in this area?

Also, we just delivered a series of recommendations based on 4+ months of deep research on Scroll’s builder support needs. The proposal here is not addressing one of the low hanging fruits. As such, my suggestion is to prioritise the key areas identified in the research and only after move to proposals such as this one.

1 Like

Hello,

I encourage having a local node in Argentina as it is one of the hottest web3 spots of the continent, additionally having DevConnect happening is a great point.

I come with some suggestions for improving the proposal:

  1. The Builder’s research has been released. I encourage the node to think and strategyze based on it. It will surely give you great advantage over other nodes as the first ones were created without that knowledge been out.
  2. The budget could be improved. When we were planning the Mx node, we calculated costs for tools based on only the three first months instead of annual cost, that allowed us to optimize our budget to deliver more value first. You have a tool budget of $500, ours is $271. Even if you are considering more tools than us (we don’t know, your proposal doesn’t specify which tools you are going to use) the budget most def could be optimized.
  3. Regarding events. The KPI package that the Foundation delivered asks about public facing initiatives and number of registrations. I really encourage you to re-assess your strategy based on those metrics. They were released recently and your proposal was drafted before, but still, if you want to ensure your proposal goes to vote include those metrics that the Foundation is going to use as base for evaluating ALL nodes.
  4. Regarding people. Would be great to know who is going to be part of the core team or at least the process that you are going to have more hiring.

Additionally, some comments:

  1. Great that the node is focusing on a specific vertical, it will def help comparing with other nodes.
  2. Great that the program is going to be online. We could share and collaborate regarding the educational content and the funneling of talent. At the Mx local node we have online sessions and IRL sessions, and we are participating with diff IRL events such as with Ethereum Mexico, Unlock Summit, Bitso, and others to onboard more people into the Open Economy.

Looking forward to reading any updates from your side and supporting the initiative.

3 Likes

Thank you so much for this detailed and encouraging feedback! We greatly appreciate your insights and shared experience from the Mexico node, especially given Argentina’s vibrant Web3 ecosystem and the upcoming Devconnect.


Responding to Your Suggestions:

  1. Builder’s Research Integration: You’re absolutely right about the importance of the newly released Builder’s Research. While our proposal was drafted prior to its publication, we’re pleased to say that our on-the-ground experience with local builders has consistently shown us insights that align closely with the report’s findings. Our approach recognizes the unique phase and needs of the region, which we believe is a key differentiator and strength of our proposal. We’re confident that our strategy already reflects many of the core takeaways from the research, and we’ll ensure this alignment is even more explicit in future iterations.
  2. Budget Optimization for Tools: We appreciate your keen eye on the budget, particularly regarding tools. The detailed budget actually allocates the tool expenditure at an estimated $100/month, not an annual cost, making the total for the program less than your stated $500. Furthermore, this allocation is part of our contingency budget, meaning any unspent funds will be returned. We’ve structured it this way to ensure flexibility while maintaining fiscal responsibility, and we’re committed to optimizing costs to deliver maximum value, just as you’ve done in Mexico.
  3. Aligning with Foundation KPI Package for Events: You’ve raised a critical point about the Foundation’s updated KPI package and the importance of public-facing initiatives. Our current proposal includes a single in-person Demo/Pitch Day in Buenos Aires, primarily focused on showcasing projects from the program. However, we’re very keen to align with the new metrics. As we’ve previously noted, we’re actively exploring avenues to generate additional resources beyond the core budget to incorporate more in-person events throughout the program’s lifecycle. These events would serve as crucial touchpoints for recruiting talent and increasing Scroll’s visibility, directly addressing the need for public-facing initiatives and aiming for high registration numbers that align with the Foundation’s new evaluation criteria.
  4. Core Team and Hiring Process: We understand the importance of transparency regarding the team. As with our past successful initiatives for LatAm builders, such as the Scroll Level-Up Hackathon '24, our strategy for team formation and engagement focuses on summoning individuals who are not only recognized as leaders in their respective areas but also possess significant experience and a proven track record within the industry. We believe this approach ensures that builders receive mentorship and guidance from figures with deep practical knowledge and influence.

Additional Comments:

  1. Vertical Focus (Privacy & Autonomy): We’re glad you see the value in our initial focus on privacy and autonomy-first consumer products. This serves as a key differentiator for the program, while still encouraging a wide array of innovative projects beyond this specific area.
  2. Online Program & Collaboration: We’re thrilled by your offer to collaborate on educational content and talent funneling! We absolutely agree that there’s immense potential for synergy between our nodes. We’re actively involved with other projects like Ethereum Argentina, Uruguay, Bolivia, Crecimiento, and The Mu, among others, and we would be incredibly excited to have participants from Mexico join our online sessions, and vice-versa. Shared learning and cross-pollination of talent will only strengthen the ecosystem across LatAm.

We’re truly excited about the opportunity to partner and build. We look forward to sharing further updates and continuing this collaborative discussion to make this initiative a resounding success.

2 Likes

Hi Danielo, thanks for taking the time to share your feedback!

We completely agree that mentoring builders requires real experience and a thoughtful approach. That’s precisely why the team behind this proposal is composed of people with a strong, hands-on track record in the ecosystem, we’ve been organizing educational and technical initiatives across Latin America for years.

For example, last year during The Level Up Hackathon, with the support of Ethereum Argentina, we helped over 50 projects get built on Scroll. Several of them ended up winning prizes, including the only Latin American team selected for Open Campus, evaluated by the Scroll team itself. One of the participating teams, Zup Protocol, was also selected from over 6,000 projects for Startup Bootcamp, Europe’s largest startup acceleration program (link), where only 10 projects made it through.

We’re happy to add a more detailed section outlining who we are and what we’ve done, so it’s clearer why we feel well positioned to execute this proposal. The 30,000 character limit made it tough to go deeper on team background, and we were also trying to avoid making it too centered on individuals.

While our proposal preceded the Builder’s Research, our direct experience with local builders revealed insights that strongly align with its findings. This understanding of the region’s unique needs is a core differentiator.

We’re totally open to refining or evolving the proposal if that helps align it more closely with Scroll’s strategic goals.

2 Likes

gm! Thank you so much for the kind words and thoughtful questions :raising_hands:

Totally agree, Devconnect is a massive opportunity, and we’re already working closely with Ethereum Argentina to ensure it becomes a catalytic moment for local builders. Part of this proposal’s timeline is designed to build momentum before Devconnect, so that by the time November arrives, we already have a strong network of engaged teams ready to showcase and take next steps.

As for Bring Argentina Onchain, yes! It was an inspiring campaign and a great signal of the community’s strength. We’d love to explore ways Scroll can plug into those organically.

If you have specific orgs in mind or ideas for how to best connect Devconnect with the local node, we’re super open to collaborating and co-creating. Always grateful for new eyes and insights!

1 Like

Thank you so much for sharing this well-structured proposal it’s clear there’s a strong commitment to growing the developer community and building real connections between Scroll and Argentina. We’re curious about a few things: are you planning to collaborate or integrate with SEED Latam, given their latest proposal? Also, since DevConnect will be in Buenos Aires, do you already have concrete plans for Scroll local node in Argentina with dates, formats, and ways to connect with the official agenda?

2 Likes

Thank you very much for your kind words and thoughtful questions.

Regarding SEED Latam, we’ve reviewed their proposal and, while we respect the visibility they’ve helped bring to the region, our approach is different. We focus on practical support for developers, long-term project acceleration, and direct integration with the Scroll ecosystem, not on retrospective event recaps or delegation-driven efforts without clear outcomes for builders.

We’re working closely with Ethereum Argentina, who played a key role in organizing our recent hackathon initiatives, including the latest one in collaboration with Scroll. Through them and as part of the planning and outreach circle, we’re coordinating activities that will give local developers the opportunity to showcase their work and connect directly with the global Scroll community.

Several pre-Devconnect announcements have already taken place, including the ETH House and more are planned during Devconnect week itself.

We’re excited about what’s ahead and fully committed to making Scroll’s presence in Argentina meaningful, visible, and developer-centric.

1 Like

We support the creation of the local Argentina Node.
We believe this proposal will strengthen the local community, foster new projects, and facilitate collaboration among developers.
At Ethereum Argentina, having worked closely with Buidlers, we see this initiative as aligned with the goal of positioning Argentina as a hub of innovation and opportunity.
We’re happy to stay in touch and explore ways to support as things move forward.

1 Like

Hi everyone!

Jumping in to clarify a bit some of the questions regarding the SEED Local Node proposal and this one. Our proposal stood as a first try to propel the local node initiative in Argentina in sight of its relevance for the industry and the opportunity that DevConnect represents for Scroll. In that sense, we’re happy to see different organizations adding up to the case, a true showcase of Argentina’s vibrancy. We are and always have been open to collaborate, exchange ideas and iteratively refine the proposal into Scrolls interest and Argentina’s reality.

We are in contact with the @ChatterPay and @Buidlers teams in order to explore synergies and unify strengths into the local node, something that might not be formalized in this current proposal but will do so in a potential future one if there’s intention to renew the program.

At this point we expect this proposal to follow its course within the governance process and contribute to it in order to see the Argentina Local Node live. We are naturally aligned with the spirit of the proposal in its builder-centric and vertical-focused approach, as well as the remote semi-format that will likely enhance participation.

As a comment, we do expect that some of the derived initiatives such as the one presented by @FinGuru do fall under the local node scope and some prior alignment is made before reaching the forum in order to keep things structured. Being that said, we’ll be following the unfolding of the discussion and keep working towards the final version of the proposal before the voting cycle.

Thanks!

5 Likes