Skip to content
Blockchain Association of Cameroon

Layer-0 Developer Academy

Developer resources

Everything a participant needs before the first session, and everything a contributor needs before the first pull request.

Standard environment

One baseline across every track, installed progressively rather than all at once — a beginner does not need Terraform in week one.

ToolPurposeFrom
Ubuntu 22.04 LTS ou 24.04 LTSReference system for every lab; WSL2 accepted on Windows.L0
GitVersion control and submission channel for all coursework.L0
VS CodeReference editor, with the Rust Analyzer and Go extensions.L0
Docker EngineReproducible environments and local multi-node networks.L1
Node.js LTSFront-end tooling, RPC clients, integration scripts.L1
Rust (rustup, toolchain stable + cible wasm32)Polkadot SDK, sovereign rollups, cryptographic tooling.L1
GoCosmos SDK, AvalancheGo, Celestia nodes.L1
FoundryContract development and testing on EVM-compatible chains.L1
Python 3Analysis scripts, economic simulation, automation.L2
Terraform + AnsibleInfrastructure as code for the cloud labs.L3
Prometheus + GrafanaNode metrics, dashboards and alerting.L3

GitHub architecture

Twelve repositories under the bac-blockchain-academy organisation, each workshop repository following one mandated layout.

Repositories

  • foundationTwenty Level 0 workshops: networking, cryptography, consensus, fundamentals.
  • polkadotRelay Chain architecture, parachains, XCM, OpenGov.
  • substratePolkadot SDK: FRAME, pallets, runtime, benchmarking.
  • cosmosCosmos SDK, CometBFT, IBC, CosmWasm.
  • avalancheAvalanche L1s, virtual machines, ICM/Warp.
  • celestiaData availability, sampling, sovereign rollups.
  • interoperabilityCross-chain labs and comparison of messaging models.
  • securityThreat modelling, hardening, supervised attack exercises.
  • devopsInfrastructure as code, monitoring, disaster recovery.
  • capstonesCohort capstone projects, archived and citable.
  • infrastructureCode for the BAC Blockchain Engineering Lab and the multichain testnet.
  • documentationCurriculum, workshop templates, instructor guides, translations.

Workshop repository layout

  • README.mdWorkshop identity, prerequisites, duration, version block.
  • architecture/Diagrams and architecture decision notes.
  • lessons/Bilingual lesson content in Markdown.
  • labs/Guided and independent lab briefs.
  • solutions/Reference solutions, published after the session and never before.
  • starter-code/Starter skeleton that compiles and is tested in CI.
  • tests/Executable tests acting as the automated marking scheme.
  • docker/Reproducible environment and light-mode images.
  • scripts/Environment install, reset and verification.
  • security/The workshop's threat model and its security challenge.
  • resources/Documentation references and further reading.

Contribution rules

  • 01Every change goes through a pull request; nobody pushes to the main branch directly, teaching staff included.
  • 02A pull request touching a published workshop must update its version block — workshop version, protocol version, review date.
  • 03Two approvals are required: a technical reviewer and a pedagogical reviewer. One contributor cannot provide both.
  • 04Continuous integration builds the starter code, runs the tests and fails if a solution leaks outside `solutions/`.
  • 05Participant work lives in personal forks; the cohort repository keeps only assessed submissions.
  • 06No key, no mnemonic, no token ever enters a repository — not on a test network, not in a comment.

Documentation registry

Workshops contain no URLs: they cite keys in this registry. Documentation that moves is corrected in one place rather than in a hundred and seventy files.

Registry pending verification: the links below have not been checked automatically (outbound network restricted at build time). Link checking is a mandatory step of the quality review.

Tier 1Official protocol documentation

Tier 2Official repository

Tier 3Research paper

Tier 5Reputable independent research