Abuja Hub Story
CATS26 Action-Learning Journey
Abuja, Nigeria
November 4 – December 15
In-Person Hackathon: December 6
Orientation: Establishing Shared Ground
The Abuja Hub began with a formal orientation call designed to align participants around a shared understanding of the programme.
From the outset, this was framed not as a conventional hackathon but as an action-learning journey, one where learning would emerge through engagement with local context, disciplined experimentation, and continuous documentation. From the call, three principles were established early:
- Learning would emerge through engagement with real local contexts.
- Progress would be validated through demonstrable artefacts, not intentions.
- Documentation and publishing were integral to the work, not post-hoc tasks.
This orientation aligned participants around a shared understanding of accountability, visibility, and collective responsibility. From the outset, it was made clear that sustained participation, attendance, and delivery were non-negotiable.
Evidence:
→ Orientation Call Recording - Passcode: w0x@%Nxm
Stage 1: Engaging Local Contexts
Following orientation, participants entered a structured exploration phase focused on understanding systems of place.
Teams and individuals engaged directly with their neighbourhoods, daily routines, and community dynamics. Observations, quotes, timelines, and patterns were captured continuously using documentation tools. These contributions accumulated into a substantial body of qualitative data, forming the foundation for later technical work.
Rather than rushing into solution design, teams were required to first articulate:
- Community essence maps
- Recurring tensions and patterns
- Lived experiences that indicated systemic opportunity or failure
This ensured that subsequent projects were grounded in lived reality rather than abstract problem statements.
Evidence:
Workshops & Q&A: The Learning Backbone
The learning journey was structured around twice-weekly live workshops and a Q&A session (Tuesdays and Thursdays at a fixed time for workshops and Mondays for Q&A Sessions), delivered at a consistent cadcadence and time. These sessions formed the backbone of the hub’s learning process.
These sessions were mandatory and cumulative; then, over time progressed deliberately from foundational Cardano concepts toward applied architecture, smart contract development, and implementation patterns. Live Q&A sessions allowed teams to surface blockers, clarify technical decisions, and adapt learning directly to their project needs.
Attendance was treated as a data integrity requirement. Participation was verified through live session monitoring, time-bound attendance forms, screenshots, and post-session cross-verification. Unverified submissions were removed to maintain accuracy.
All sessions were recorded. Slides, examples, and exercises were uploaded and organised centrally, ensuring that learning remained accessible to teams progressing at different speeds.
Participants new to blockchain were directed to a dedicated foundational resource, ensuring accessibility without lowering technical expectations.
Evidence:
Reinforcing Learning Through Weekly Kahoots
Weekly Kahoot sessions complemented workshops by reinforcing key concepts covered during that same week. Questions were drawn directly from workshop material, ensuring alignment between teaching and assessment.
Kahoots served as both a learning reinforcement mechanism and an engagement tool. Weekly leaderboards reset after each session, emphasising consistent participation rather than cumulative advantage.
Cash prizes were awarded to the top three performers each week and delivered within a defined timeframe, reinforcing accountability and follow-through.
Evidence:
Team Formation and Early Accountability
As shared understanding deepened, participants formed teams around a common purpose, not assigned challenges.
The Hub Lead ensured that:
- Each team included at least one capable Cardano developer
- Roles were clarified early (technical, coordination, documentation, UX, where applicable)
- Teams created shared workspaces and repositories from the outset
This shifted the dynamic from exploration to ownership. Teams were expected to move quickly from discussion into visible planning and early implementation. By the end of this phase, every active participant was embedded within a team, and every team had begun defining a concrete project direction grounded in their Stage 1 insights.
Evidence:
- Team List & Role Assignments
- Team Workspace & Repository Index
- [Team Formation Call Recording]
Internal Coordination and Alignment
From the start of the programme, Hub Leads held daily internal alignment check-ins. These sessions enabled real-time sharing of insights, early identification of at-risk teams, cross-hub pattern recognition, and coordinated intervention. This internal rhythm ensured that the hub operated as a coherent system rather than a collection of parallel teams and allowed information and experience exchange across Addis Ababa, Kigali, and Abuja hubs managed by DirectED.
Evidence:
From Insight to Implementation
Midway through the programme, expectations shifted decisively toward visible implementation. Teams translated insights into architectures, user flows, prototypes, and early smart contract logic.
Teams were required to demonstrate:
- Early prototypes or working components
- Code commits or architectural artefacts
- Clear alignment between community insights and technical decisions
Workshops and Q&A sessions were adapted accordingly, focusing increasingly on technical execution and problem-specific guidance.
In-Person Hackathon: December 6
The in-person hackathon marked a moment of convergence rather than conclusion.
Teams gathered physically at The Meeting Point Abuja to refine prototypes, clarify narratives, and pressure-test assumptions. The day was structured around collaboration, iteration, and demonstration rather than competition or judging.
This moment surfaced both strengths and remaining gaps, informing the structure of the final phase.
What made the Abuja in-person hackathon particularly remarkable was the extraordinary sacrifice participants made to attend. Many traveled across states, sleeping in hotels and going by road despite real hazards including kidnapping risks. Students and workers alike sacrificed personal time, family commitments, and in some cases exam preparation to be present. This level of commitment revealed not just dedication to the programme but the deep resilience and determination that characterizes Nigerian builders—willing to push through systemic barriers to create meaningful change in their communities.
Evidence:
Final Sprint: Validation, Reviews, and Submissions (Dec 8–14)
The week following the hackathon was the most intensive phase of the journey. At this stage, the focus shifted to ensuring team progress is visible in the docs, and support and accountability for team members continued.
Consolidation & Reviews
Stage 1 materials were reviewed and consolidated to ensure continuity between contextual insight and technical execution.
Teams underwent structured final reviews, designed explicitly as validation checkpoints rather than informal check-ins. Each team was required to:
- Demonstrate a live working MVP
- Explain concrete progress since previous demos
- Walk through the implementation logic where required
- Surface blockers clearly and honestly
Technical reviews examined code structure, architectural decisions, and implementation quality. Feedback was documented precisely, with action items, deadlines, and risk levels assigned.
Evidence:
→ Team Review Tracker Spreadsheet
→ Recorded MVP & Code Review Sessions:
Submission Management
Final submissions included MVP demos, source code repositories, documentation, and pitch materials. All submissions were reviewed for completeness, accessibility, and alignment with requirements before being archived and published.
Evidence:
Publishing as Part of the Learning Process
Publishing was treated as an extension of the action-learning journey rather than an administrative step. Final artefacts were organised, verified, and made accessible through the hub’s documentation structure. This curation layer connects exploration, learning, iteration, and outcomes into a coherent account of the journey.
Challenges and Resilience: The Abuja Reality
The Abuja Hub journey was marked by significant challenges that tested participant resilience and revealed systemic gaps requiring urgent attention.
Technical Infrastructure Gaps
The documentation infrastructure presented a critical barrier. There was no proper documentation setup for troubleshooting issues, forcing teams to figure out solutions independently. When teams did find solutions, there was no structured system to document them for others, meaning every team potentially faced the same blockers repeatedly without access to accumulated knowledge. This created inefficiency and frustration that could have been avoided with proper knowledge management systems.
Cardano Developer Scarcity
The Abuja hub faced a severe shortage of Cardano developers, reflecting a broader ecosystem challenge. This scarcity isn’t unique to Abuja—it’s a national issue requiring urgent investment in Cardano training, university partnerships, or dedicated developer schools across Nigerian communities. Current Cardano ecosystem focus tends to concentrate on specific regions like Kaduna or Lagos, leaving other parts of the country without adequate developer capacity. Building sustainable blockchain ecosystems in Nigeria requires distributed investment in technical education, not geographic concentration.
Timeline and Cultural Context
December proved to be a particularly challenging time for the hackathon. In Nigeria, December is traditionally when work winds down, offices close early, and people travel to meet family as the year ends. Many participants were students facing exams or workers managing year-end responsibilities, requiring them to sacrifice significant personal time and face considerable stress to maintain participation.
The compressed timeline created intense pressure. The hackathon operated as a sprint fast paced and demanding which became stressful even for those leading the hub. One hub lead had to step down because the programme interfered with exam preparation, highlighting how the timing created impossible choices for participants balancing education, work, and programme commitments.
The Sacrifice Behind the Success
Despite these challenges, participants demonstrated extraordinary resilience. The in-person hackathon revealed the depth of their commitment: people traveled across states, paid for hotels, and journeyed by road through dangerous conditions including kidnapping risks all to be present and contribute. This wasn’t recklessness; it was determination. It showed how much Nigerian builders are willing to sacrifice when they see real opportunity to create meaningful change in their communities.
This resilience is characteristic of Nigerian innovation ecosystems: builders push through systemic barriers, infrastructure gaps, and personal hardships because the work matters. The Abuja Hub’s journey is a testament not just to what was built, but to what Nigerian builders are capable of achieving when given even imperfect conditions and support.
Recommendations for Future Programmes
These challenges point to clear improvements for future iterations:
- Invest in documentation infrastructure that captures and shares solutions systematically
- Expand Cardano developer training across Nigeria, not concentrated in select cities
- Consider programme timing carefully summer periods may offer better participation windows when educational and work commitments are lighter
- Extend timelines to reduce sprint-induced stress and allow for deeper learning and iteration
- Build support systems that acknowledge participants’ competing commitments and provide flexibility where possible
Outcomes & Reflections
By the end of the programme, the Abuja Hub had demonstrated:
- Sustained participant engagement supported by structured learning despite significant personal sacrifice
- Strong alignment between local context and technical execution
- Clear accountability mechanisms at both team and hub levels
- A disciplined transition from exploration to delivery
- Extraordinary resilience in the face of infrastructure gaps, developer scarcity, and timing challenges
The projects produced are presented as credible, grounded interventions with a clear lineage from lived context to technical artefact, built by teams who sacrificed significantly to see them through.
What Emerged
Several patterns became clear over the course of the Abuja Hub’s journey:
- Consistent workshops created a stable learning spine despite external pressures
- Disciplined coordination built trust and visibility
- Kahoots reinforced learning and sustained engagement
- Daily Hub Lead alignment enabled early intervention and support
- Structured final reviews turned effort into credible outcomes
- Nigerian builder resilience transformed barriers into motivation for young people
- Systemic gaps in documentation, developer capacity, and timing require urgent attention for future programmes
Team Stories
This hub-level story provides the overarching narrative. Each team’s story offers a deeper view into how context, learning, feedback, and iteration came together in practice.
👉 Abuja Team Stories
| Team | Project | Team Story Link |
|---|---|---|
| StemTrust | Blockchain-powered milestone-based STEM research funding platform | View Team Story |
| CATS_P | Mobile mechanic accessibility and verification for rural drivers | View Team Story |
| Classly | Decentralized FinTech infrastructure for education creator economy | View Team Story |
| Ctrl + Alt + Win | Cardano-powered medicine verification and prescription management system | View Team Story |
| YoTouch | Community-powered digital identity system for rural farmers and FMARD registration | View Team Story |
| Autofy | Transportation safety, compliance, and enforcement | View Team Story |
| HealthChain | Blockchain-secured patient-controlled medical records with PWA technology | View Team Story |
| SendWaste | Blockchain-powered waste recovery verification platform with NFT receipts | View Team Story |
| Cardano Moon | National Electronic Medical Records (EMR) infrastructure for Nigeria | View Team Story |
| $READS | Learn-to-Earn education platform with blockchain tokens and CBT simulations | View Team Story |
| Zeno Wallet | Cardano-native Telegram wallet for conversational blockchain interactions | View Team Story |
| Team Excellent | Blockchain-based transparent aid distribution and verification system | View Team Story |