Layer-0 Developer Academy
Roadmap and partnerships
Every phase ends on an observable criterion rather than a date reached. A phase whose criterion is not met does not close, whatever the calendar says.
Eleven phases
- Phase 0
Governance and architecture
Assemble the task force, settle the technical standards and publish the programme architecture.
Deliverables
- Task force assembled on the critical roles
- Technical standards and workshop template published
- GitHub organisation created and contribution rules in force
- Curriculum map and competency graph published
Exit criterion
One pilot workshop passes all six quality reviews with no waiver.
- Phase 1
Blockchain foundations
Produce and test the twenty Foundation track workshops.
Deliverables
- Twenty workshops published in French and English
- Workshop repositories with starter code tested in CI
- First Level 0 pilot session delivered
Exit criterion
A test group passes the Level 0 practical exam with no help from the workshops' author.
- Phase 2
Polkadot / Substrate curriculum
Deliver the thirty workshops of tracks A and B and their shared capstone.
Deliverables
- Thirty workshops published and tested
- Demonstration chain operated by BAC
- First appchain capstone delivered and reproduced
Exit criterion
An outside team reproduces the capstone chain from the repository alone.
- Phase 3
Cosmos curriculum
Deliver the twenty-five workshops of track C, IBC and relayer operations included.
Deliverables
- Twenty-five workshops published and tested
- Two demonstration chains linked over IBC
- Monitored relayer operated by BAC
Exit criterion
An IBC transfer is executed end to end by a participant on BAC's chains.
- Phase 4
Avalanche curriculum
Deliver the twenty workshops of track D, up to bespoke virtual machines.
Deliverables
- Twenty workshops published and tested
- Demonstration L1 validated by an assembled set
- Documented validator requirements
Exit criterion
A participant's L1 runs for a week with no intervention from the teaching team.
- Phase 5
Modular curriculum
Deliver the twenty workshops of track E, from the availability problem to the sovereign rollup.
Deliverables
- Twenty workshops published and tested
- Availability nodes operated by BAC
- Demonstration rollup rebuildable from published data
Exit criterion
A third party rebuilds the demonstration rollup's state with no data handed to them.
- Phase 6
Interoperability
Deliver the fifteen cross-chain workshops and publish BAC's selection doctrine.
Deliverables
- Fifteen workshops published, including the three comparative labs
- Measurement records for all three models published
- Selection doctrine and trust taxonomy versioned
Exit criterion
The three comparative labs produce records another cohort can reproduce.
- Phase 7
Infrastructure and security
Deliver the thirty DevOps and security workshops, and professionalise testnet operations.
Deliverables
- Thirty workshops published and tested
- On-call rota and public post-mortems for BAC's testnet
- Responsible disclosure policy in force
Exit criterion
A disaster drill on the testnet succeeds within the publicly committed window.
- Phase 8
Certification
Open every certification with assembled panels and tested practical exams.
Deliverables
- Certification frameworks published
- Panels assembled and trained
- Public register of certifications issued
Exit criterion
One exam, marked by two distinct panels, produces comparable results.
- Phase 9
BAC Blockchain Engineering Lab
Make the three lab environments and their funding permanent.
Deliverables
- LAB-LOCAL, LAB-CLOUD and LAB-NETWORK in continuous service
- Documented infrastructure funding model
- Testnet Polkadot and Cosmos chains in service
Exit criterion
The infrastructure runs a full quarter with no emergency funding.
- Phase 10
BAC multichain testnet
Open to the region's developers a network where they can deploy, break, upgrade and connect with no financial risk.
Deliverables
- Four demonstration networks in service and interconnected
- Faucet, explorer and public endpoints
- Opened to developers outside the cohorts
Exit criterion
Developers outside the programme deploy on the testnet unaided.
Pilot cohort
30–50 developers over 12–16 weeks, from foundations to demo day.
Selection
- 01Programming experience, in any language
- 02Verifiable public activity: a repository, a contribution, a personal project
- 03Computing fundamentals: networking, command line, data structures
- 04Genuine declared availability, verified in interview
- 05Motivation anchored in a project rather than an intention
Structure
- wk 1–3Foundations and tooling
- wk 4–5Blockchain fundamentals
- wk 6–10Ecosystem specialisation
- wk 11–13Infrastructure and security
- wk 14–15Capstone
- wk 16Defences and demo day
- A reserved share of each intake goes to high-potential beginners: the programme does not select only the already-trained.
- Every participant gets effective infrastructure access, in full, light or shared mode according to their equipment.
- No withdrawal is recorded without an interview: drop-out is treated as a programme defect before being attributed to the participant.
How the programme will be judged
Including the metrics that are uncomfortable: a low completion rate is treated as a defect in the workshop, not in the learner.
Reach
Registered learners
Accounts created with at least one workshop started.
Active learners
Learners who passed a workshop in the last thirty days.
Hackathon participants
People who submitted a project to the BAC Multichain Builders Challenge.
Quality
Per-workshop completion rate
Share of enrolled learners passing the workshop; a low rate signals a design defect.
Capstone reproducibility rate
Share of capstones reproduced by a third-party team from the repository alone.
Output
Certifications issued
Certifications earned through practical examination, by level.
GitHub contributors
People with a merged contribution in the Academy organisation.
Chains deployed
Application chains delivered by participants and operated for at least a month.
Validators operated
Validators operated by graduates on test or production networks.
Ecosystem
Upstream contributions
Contributions merged into official protocol repositories.
Companies created
Entities formed out of a capstone or hackathon project.
Ecosystem grants obtained
Grants awarded by protocol foundations to projects from the programme.
University partnerships
Signed agreements providing for integration into a degree programme.
Employment outcomes
Graduates in a technical blockchain role within six months.
At one year
- A pilot cohort of thirty to fifty developers taken through to demo day
- Fifty workshops published, tested and bilingual
- One demonstration chain continuously operated by BAC
- Two signed university agreements
At three years
- The full catalogue published and kept current with protocol versions
- Several hundred developers trained and dozens certified
- The multichain testnet open to the region's developers
- Application chains from the programme operated outside BAC
- Formalised partnerships with at least two protocol foundations
At five years
- Cameroon exports protocol engineering rather than importing solutions
- Graduates sit on technical bodies of international ecosystems
- The curriculum is embedded in degree programmes across Central Africa
- A research programme anchored in the capstones produces publications
BAC Global Blockchain Technology Partners Program
Each category states what a partner brings and what they get back. A partnership request with no return column is a request for aid.
No international partnership is concluded to date. The categories above describe the framework BAC proposes, not existing commitments.
Founding Technology Partner
Brings
Multi-year commitment: instructors, curriculum review, infrastructure and funding.
Receives
A track kept current with its releases, and a pool of developers trained on its stack.
Curriculum Partner
Brings
Technical review of workshops and validation of their protocol accuracy.
Receives
A public curriculum that is accurate about their technology, rather than stale tutorials.
Infrastructure Partner
Brings
Cloud credits, servers, RPC endpoints or regional hosting.
Receives
A real, publicly documented usage ground, under African conditions.
University Partner
Brings
Rooms, teachers, credit recognition and access to students.
Receives
An up-to-date engineering curriculum the institution does not have to produce alone.
Research Partner
Brings
Scientific supervision and co-publication of work arising from the capstones.
Receives
An experimental ground and unpublished usage data on the region.
Developer Ecosystem Partner
Brings
Developer advocates, mentoring, international visibility for graduates.
Receives
Trained contributors entering the ecosystem through the technical door.
Hackathon Partner
Brings
Prize funding, technical judges and follow-through for winning projects.
Receives
Prototypes built on their stack for real African problems.
Certification Partner
Brings
Recognition of BAC certifications and participation in the panels.
Receives
A practical assessment framework applicable to their own ecosystem.
What BAC brings to the table
- 01A public, versioned and maintained curriculum in which every technical claim is traceable back to official documentation.
- 02A pool of developers assessed on practical examination rather than attendance.
- 03A usage ground documented under African bandwidth and cost conditions — data few ecosystems hold.
- 04An institutional entry point to Cameroonian administrations and universities.
- 05Upstream contributions from the cohorts, in the language and on the topics where the ecosystem lacks contributors.