Summary of Proposal (50 words)
Community-run space where builders turn Ethereum L1+L2 data into clear app signals, use APIs and notebooks, and make sound product and funding decisions. Short labs, office hours, and a dashboards corner. English program with Spanish assistance. Includes sessions on L2 design and building apps across rollups, and transparent impact reporting.
Motivation and Rationale
What attendees get out of it
· Make better product decisions with data: define app signals (activation, retention proxies, cost-to-serve) and compare across L1 + L2.
· Use APIs confidently: go from contract events → indexed endpoints → charts/alerts; understand latency, coverage, and cost trade-offs.
· Build metrics fast: copyable queries, schemas, and Python notebooks you can adapt to your contracts.
· Show impact & raise funding: structure transparent metrics for grants, VC/angels, and retro funding (what to track, how to publish, common pitfalls).
· Understand L2s in practice: how sequencers, DA, proofs, and fee models affect UX—and what that means for app instrumentation and comparisons.
· Help on demand: office hours for your app’s metrics, indexing, and cross-L2 questions.
· Language: English program, with Spanish-speaking assistance during office hours; we aim to include some Spanish sessions if feasible.
Why a Community Hub (vs. a single talk)
People arrive with different stacks and questions. The hub supports drop-in learning all day, repeated mini-labs, and rotating office hours so attendees can try things, get feedback, and leave with working approaches.
How it complements Devconnect ARG / the World’s Fair
The World’s Fair showcases applications. This hub provides the measurement and L1 & L2 context behind them: labeling actions, indexing data, analyzing impact for funding, and comparing activity across L1 and L2s in a way teams can act on.
Implementation
Space plan
Four zones (to be created with flexible furniture on the fly):
· Mini-Lab tables (hands-on)
· Office Hours corner (whiteboard + stools)
· Dashboards corner (rotating screens)
· Ecosystem Map Wall (attendee contributions: apps/infra/gaps)
Sample program (English-only draft; Spanish assistance available)
· 09:15–09:35 Primer: From raw transactions to app signals (L1 + L2 basics)
· 09:45–10:20 Mini-Lab: Index one event → API in 35 minutes (Envio)
· 10:30–11:00 Primer: Metrics that matter for funding (grants, VC, retro): what to track and how to publish (growthepie + Open Source Observer)
· 11:10–12:00 Office Hours: Cross-L2 comparisons that don’t mislead (growthepie)
· 12:15–12:45 Workshop: Impact metrics with Python notebooks (Open Source Observer, participants bring a laptop)
· 14:00–14:30 Primer: How L2s work (sequencers, DA, proofs) and what that means for apps (superchain.eco; OP Labs if available)
· 14:40–15:20 Clinic: Decode transactions → human-readable actions for your app (Noves)
· 15:30–16:00 Dashboards Unpacked: Methods, caveats, failure modes (growthepie)
· 16:10–17:00 AMA / Office Hours: Building on L2 vs L1: trade-offs, costs, tooling (superchain.eco; OP Labs if available)
· 17:10–17:40 Mini-Lab: Instrument your app for grant/retro reports (labels + simple endpoints) (Open Labels Initiative / Enscribe / Envio, with growthepie)
· All day: Help Desk (rotating), Dashboards Corner, Ecosystem Map Wall
Daily rhythm (Nov 17–22)
· Repeat core labs with new examples (DeFi, payments, social, infra).
· Rotate office hours so there’s always coverage for indexing, labeling, notebooks, L2 design questions, and funding-metrics reviews.
· Provide Spanish-speaking assistance during office hours; add Spanish sessions where possible.
How topics support the application layer
· Funding-oriented metrics: define, compute, and publish impact transparently for grants, VC/angels, and retro programs.
· Labels & taxonomies (Enscribe, Open Labels Initiative): consistent action names → cleaner funnels and retention metrics.
· Indexing to API (Envio): make app data queryable by dashboards and alerting systems.
· Notebook analysis (Open Source Observer): explore and graph impact metrics; reuse notebooks.
· Cross-ecosystem metrics (growthepie): interpret L1 + L2/app signals and avoid apples-to-oranges.
· L2 design & implications (superchain.eco; OP Labs if available): how sequencing, DA, proofs, and fee dynamics shape what apps should measure.
Team
Dedicated organizers (committed coverage during operating hours)
· growthepie: Coordination; L1 & L2 cross-ecosystem + application metrics; “dashboards unpacked.”,
· Open Source Observer: Python notebook workshop + office hours; OSS directory in collaboration with growthepie
· Envio: Indexing mini-labs; pipeline design office hours.
· Noves: Transaction-to-action decoding clinics for app-level metrics.
· Enscribe: Contract/action naming patterns; ENS-based clarity.
· Open Labels Initiative: Shared labels and label-confidence patterns across tools.
· superchain.eco: Comparable metrics and ecosystem view across OP-Stack chains (and L2 design context).
· Routescan: metrics across ecosystems.
Why this team and set of partners is suited
These contributors work daily on labeling, indexing, analysis, and ecosystem-level metrics across L1 and L2s. They bring practical code, schemas, and operational experience that translate directly into what builders need to ship. More partners contacted and waiting for answer.
Ensuring a neutral, welcoming space
· Content is methods-first; examples are chosen for clarity; speakers disclose affiliations, but to not shill or market their own products too much.
· Sessions avoid endorsements; alternatives are presented where relevant.
· Materials (slides/notebooks/queries) are shared for reuse.
· English program with Spanish assistance during office hours; we aim to include Spanish sessions if feasible.
Production requirements (space & equipment)
· Flexible layout for ~10–30: movable tables + stools for mini-labs; a quieter corner for office hours.
· Displays/Projection: 2 projectors or maybe 3 large displays (HDMI/USB-C).
· One additional screen for live notebook demos.
· Power: 12–16 outlets, 6–8 power strips, 4–6 extension cords (5–10 m), gaffer tape.
· Whiteboards & materials: 2 whiteboards + erasers; sticky notes; A4/A3 paper; fine + broad markers; pens; clipboards.
· Adapters: a few USB-C→HDMI and MiniDP→HDMI dongles if possible
We are still in touch with more partners for more content around the topics. There’s so much to cover 