June Cohort | From Zero to Hackathon-Ready

Format: 6 Virtual Sessions | Every Tuesday & Thursday, 8:00 PM EAT | 2 Hours Each Platform: Google Meet | Special Events: Nights of Code (Jun 19) + Builders Connect (Jun 27)

🗺️ COHORT ROADMAP AT A GLANCE

Date Week Sessions Theme Deliverable
Tue Jun 9 Session 1 The Payment Stack on Avalanche Architecture diagram of your dApp
Thu Jun 11 Session 2 Smart Contracts for Payments Deployed ERC-20 + payment contract on Fuji
Tue Jun 16 Session 3 Stablecoins, USDC & Gas Abstraction Working gasless payment flow on Fuji
Thu Jun 18 Session 4 Embedded Wallets & UX Layer Integrated embedded wallet with payment UI
Tue Jun 23 Session 5 Cross-Chain Payments & ICM/ICTT Cross-chain token transfer working demo
Thu Jun 19 🌙 NIGHTS OF CODE Build the MVP (12-Hour Hackathon) Blockchain Centre

https://luma.com/x8v5qugw | Live MVP deployed on Fuji | | Tue Jun 25 | Session 6 | Production Patterns & Hackathon Playbook | Pitch deck + technical architecture doc | | Fri Jun 27 | 🤝 BUILDERS CONNECT | IRL MVP Pitches & Peer Review

https://luma.com/gn745sur | Feedback + final roadmap to August 28 |

📘 SESSION 1 Week 2 — Tuesday, June 9 | 8:00–10:00 PM EAT

"The Web3 Payment Stack on Avalanche | What You're Actually Building"

Goal: Give builders the full mental model of how payments work on Avalanche before writing a single line of code.

⏱️ AGENDA (120 min)

Time Block Details
0:00–0:15 Cohort kickoff Program structure, hackathon brief, team formation rules
0:15–0:45 The Modern Web3 Payment Stack Walk through all 6 layers: App → Wallet Abstraction → Transaction Orchestration → Settlement → Compliance → Merchant Integration
0:45–1:15 Avalanche Architecture Deep Dive C-Chain (EVM), P-Chain (staking), X-Chain (assets). Why Avalanche wins for payments: sub-second finality, 1 nAVAX base fee (ACP-125), Cancun EIPs (ACP-131), Dynamic gas (ACP-176)
1:15–1:45 Live Case Studies Urbanspace NYC pilot, Uptop marketplace rails, Wyoming FRNT stablecoin, Avalanche Card
1:45–2:00 Homework brief Design your payment dApp architecture on paper. What problem does it solve? Who is the user? What layer of the stack does it live in?

📚 CONCEPTS COVERED