Arbitrum Stylus Awakening: Builders Lunch & Talks | Final Report

[WakeUpLabs]

Executive Summary

Name of the project: Arbitrum Stylus Awakening: Builders Lunch & Talks by WakeUp Labs

Questbook Application: Arbitrum Stylus Awakening: Builders Lunch & Talks by WakeUp Labs

Website / Socials:

• Website: https://www.wakeuplabs.io
• X (Twitter): https://x.com/wakeuplabs
• LinkedIn: WakeUp Labs | LinkedIn

As part of Devconnect 2025 in Buenos Aires, we successfully delivered Arbitrum Stylus Awakening, an international in-person event dedicated to the Stylus builder community. The event was organized by WakeUp Labs and supported by the Arbitrum DAO.

The primary objective of the event was to convene project teams, protocol contributors, and ecosystem stakeholders who are currently building with, or exploring, Arbitrum Stylus. Representatives from Arbitrum, Offchain Labs, Superposition, Fairblock, Co-Builders, Entropy Advisors, Fairgate, and additional ecosystem leads participated in the session, contributing technical presentations, roadmap updates, live demonstrations, and group discussions.

The event provided a valuable platform for coordination, alignment, and information exchange within the early Stylus ecosystem.

Bringing contributors together in person emphasized the importance of collaborative momentum and highlighted the ecosystem’s strong foundational progress. Regardless of Stylus being in an early stage, participants demonstrated tangible development activity, thoughtful experimentation, and a high degree of interest in advancing the technology.

A short video recap accompanies this report, providing an overview of the atmosphere, engagement, and builder activity captured during the session.

• Objective: Strengthen Arbitrum’s ecosystem through technical education, Stylus adoption, and relationship-building between Arbitrum’s core contributors and top regional builders.
• Outcome: Brought together leading Stylus builders and ecosystem partners for coordinated knowledge-sharing, resulting in increased engagement, new collaborations, and clear momentum for Stylus adoption.

Full report can be found here: Arbitrum Stylus Awakening Final Report.pdf

Performance Against KPIs

Qualitative Impact & Community Feedback

General feedback was outstanding: reviews on the chosen venue, speaker selection and intentionally curated guests was something that everyone highlighted. The Stylus ecosystem found a site where they could meet and keep an ongoing conversation.

Even guests who couldn’t attend followed the event remotely and numbers of the OD show the interest that the event generated.

Event Impact

The event acted as a coordination layer for early Stylus builders, enabling direct connections between protocol teams, infrastructure vendors, and application developers.

Key outcomes include:

• New collaborations: Multiple teams initiated conversations around joint experimentation with Stylus, including performance testing, cryptographic use cases, and cross-protocol integrations.
• Follow-up meetings scheduled: Several post-event technical and strategic follow-ups were arranged between builders and Arbitrum ecosystem stakeholders to explore pilots, grants, and deeper technical support.
• Unlocked opportunities for the Arbitrum Ecosystem: The event surfaced concrete opportunities for Stylus adoption across areas such as high-performance execution, cryptography-heavy applications, and trust-minimized Bitcoin integrations, providing early signals for future ecosystem initiatives and funding priorities.

Overall, the gathering accelerated the transition from isolated experimentation to coordinated ecosystem activity around Stylus.

LATAM Builder Engagement

Arbitrum Stylus Awakening demonstrated strong engagement from LATAM’s developer ecosystem, with a high concentration of technically mature teams actively building or prepared to build on Arbitrum.

The event positioned Arbitrum as a credible and attractive platform for LATAM builders looking to deploy sophisticated, performance-oriented applications.

Media Content

X (Twitter) thread before the event, announcing it: https://x.com/wakeuplabs/status/1988357330958770292

X (Twitter) thread immediately after the event.

And many more social media posts and follow-ups, all of which can be found in the full report here: Arbitrum Stylus Awakening Final Report.pdf

Financial Summary

Grant fund utilization (approximate):

• Venue, catering, and logistics: ~75%
• Event operations, materials, and coordination: ~10%
• Marketing, distribution, and post-event content: ~10%
• Audio-visual production (video & photography): ~5%

Budget alignment

Spending closely matched the original budget proposal. No material deviations were required.

Future Plans & Continued Ecosystem Alignment

Arbitrum Stylus Awakening confirmed that Stylus has moved from experimentation to active adoption by experienced builders. The event aligned core contributors and teams, validated strong demand for a dedicated technical forum, and highlighted LATAM as a strong source of Stylus builders. Builder-to-builder exchange stood out as a key outcome, with future editions benefiting from broader access and lighter formats to scale impact.

Going forward, future editions could explore a hybrid format that balances open technical talks for the wider community with smaller, high-signal builder gatherings.

The optimal structure is still evolving, but this iteration provided a strong signal of what creates the most impact.

Next Steps

• Convert builder interest into concrete outcomes through structured follow-ups and technical support.
• Launch focused initiatives (e.g. Stylus sprints or pilot programs) to accelerate deployments and experimentation.
• Maintain momentum via recurring technical sessions and regional touchpoints.
• Amplify builder progress and ecosystem signals through coordinated content and reporting.

Overall, the event established a strong foundation for sustained Stylus adoption and positions Arbitrum to continue scaling its builder ecosystem with clear, actionable next steps.

[Arb_Junior]

Thank you for this final report @WakeUpLabs

This final report covers a relatively small, focused community/builder event. It demonstrates reasonable accountability on process and narrative impact, while showing typical limitations of early-stage ecosystem grants (soft metrics, limited quantitative rigor, and reliance on qualitative claims).

Strengths:

• Milestone tracking is genuinely useful. Section 8 gives dated deliverables against 4 milestones (planning → marketing → execution → report), which is more traceable than most event reports.
• KPI table is upfront and specific, with targets vs. results rather than vague “success” language — attendance (77 vs ≥35), builder mix (33 vs ≥15), social impressions (19,770 vs ≥10,000).
• Speaker/agenda detail is verifiable — named speakers, affiliations, talk titles, and timestamped agenda make it easy to cross-check against public event listings or recordings.
• Extensive public promotion trail (X, LinkedIn, blog, YouTube, forum post) gives a real paper trail for the visibility KPI rather than self-reported numbers alone.

Opinions:

• The Ecosystem Growth KPI is not measured, it’s deferred. Target was “≥6 new project leads/collabs created”; result says this “will be properly defined in the future through initiatives like Stylus Sprint V2.” That’s the KPI most tied to actual grant ROI (ecosystem growth, not just attendance), and it’s the one left unquantified. For a governance review this is the weakest link in the report.

• 100% “positive survey responses” is a red flag on measurement design, not just a great outcome — no sample size, no survey instrument, no response rate disclosed. Perfect scores without methodology invite scrutiny.

• Social impressions (19,770) is a single vanity metric with no breakdown of reach vs. engagement vs. bot/impression inflation, and no link to conversion (e.g., how many impressions → RSVPs → attendees).

• No budget/spend section at all. For a fund-accountability review this is a significant gap — the report covers deliverables and KPIs but not cost-per-attendee, cost-per-lead, or reconciliation against the grant amount.

• “Builder mix” (33 confirmed founders/builders) is self-declared, with no methodology for how “founder/builder” status was verified (e.g., LUMA registration field vs. manual curation).

• Qualitative claims outpace evidence in Section 5 (“multiple teams initiated conversations,” “several post-event… follow-ups were arranged”) — these are asserted, not named or counted, unlike the Section 4 KPI table.

Questions:

1. What is the current status of the deferred “new project leads/collabs” metric — is Stylus Sprint V2 funded/scheduled, and will it retroactively report against this event’s grant?

2. Can you share actual grant spend by milestone against the approved budget, and cost-per-attendee/cost-per-confirmed-builder?

3. What was the survey instrument and response count behind the 100% positive figure?

4. How was “confirmed founder/builder” status determined for the 33 figure — self-reported at registration, or vetted?

5. Of the “several post-event follow-ups” and “new collaborations,” can you name specific teams/projects (even anonymized categories) and their current stage?

6. Given the report’s own suggestion to shift toward “lighter formats such as focused lunches or dinners” — does this imply a change in future grant request size/scope versus this full-conference format?

Providing answers would further strengthen the report’s credibility.​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​

Overall, this is a clean, professional final report for a domain-allocator / Questbook-style events grant.

[MconnectDAO]

Strong work by the WakeUp Labs team. Activities like Stylus Awakening are very important for building awareness, trust, and real collaboration among developers. The event created useful space for technical learning, builder connections, and future Stylus adoption.

For future editions, I suggest expanding this initiative beyond major cities and including rural and village areas as well. Students, local developers, colleges, and young communities in these regions often have strong potential but limited access to Web3 education and ecosystem networks.

A simple outreach model could include:

• Introductory Stylus and Arbitrum workshops in regional colleges

• Local language learning material and recorded sessions

• Small community meetups with online participation options

• Beginner friendly hackathons or learning challenges

• Mentorship pathways for promising builders from rural areas

This can give people early knowledge, practical skills, and future career opportunities while bringing new talent into the Arbitrum ecosystem. The report itself also notes that future editions could use broader access and hybrid formats, which makes this direction especially relevant. @WakeUpLabs @Arb_Junior