PoW & Completion Criteria
At Btrust Builders, progress is measured by what you build and contribute, not by time spent or attendance.
We don’t issue certificates for simply showing up. Instead, we recognize builders who consistently engage, complete meaningful work, and demonstrate learning through practice.
This page explains what Proof of Work (PoW) means across Builders pathways and how completion is determined.
What Proof of Work Means
Proof of Work is evidence that you:
Actively engaged with your pathway’s learning material
Applied your learning through practical work
Maintained consistency and follow-through over time
Your Proof of Work lives in public, verifiable spaces (GitHub repositories, submissions, discussions, demos, or written reflections), not in private claims.
This reflects how credibility works in open-source communities:
What you build and share matters more than what you say you know.
What Counts as Proof of Work
While details vary by pathway, Proof of Work generally includes:
Learning Milestones
Evidence that you meaningfully engaged with the core material:
Completion of required modules, chapters, or exercises
Screenshots or progress markers showing engagement
Written reflections, notes, or summaries (where required)
Practical Work & Deliverables
Evidence that you applied your learning:
Completed Builders tasks or exercises
Code written and pushed to GitHub with clear commits
Written analyses, structured responses, or reflections
Demos, walkthroughs, or presentations
For technical pathways, public code and commit history are the strongest signals of progress.
Consistent Weekly Submissions
Proof of consistency includes:
Submitting weekly progress updates on time
Sharing links to completed work and supporting evidence
Clear signals of steady effort over time
Consistency matters more than perfection.
Community Participation
Pathways are designed to foster collaboration:
Attending sync calls, study sessions, discussions or office hours
Asking thoughtful questions or sharing solutions
Helping peers, giving feedback, or sharing learnings
You don’t need to be loud, you do need to be present.
Core Completion Requirements
To complete a Builders pathway, participants typically must:
Notes:
Each pathway may define minimum thresholds (e.g., “4 out of 5 tasks completed”)
Completion is based on effort and demonstrated learning, not mastery
Late or partial work may affect completion status
Live pathways may include additional participation expectations
Details are always communicated clearly at the start of each pathway.
What You Receive Upon Completion
Builders Proof of Work Recognition
Official recognition as a Btrust Builders Pathway Graduate
Inclusion in internal Builders tracking and alumni records
This is not a certificate, but a signal of demonstrated effort and learning.
Sharable Evidence of Learning
You leave with:
Public artifacts (code, writing, or projects)
A clear learning trail to reference for:
Open-source contributions
Grant or fellowship applications
Future Builders opportunities
Your Proof of Work is yours to carry forward.
Clear Next Steps
Depending on your pathway and performance, you may:
Be encouraged toward more advanced Builders pathways
Be recommended for open-source projects
Be considered for grants, fellowships, or supported work
Completion opens doors, it does not guarantee outcomes.
What Does Not Count as Completion
The following alone do not qualify:
Watching content without submitting work
Attending calls without completing required tasks
Private or unpublished work without public proof
Last-minute submissions without meaningful engagement.
Completing a pathway means you:
Took ownership of your learning
Produced real, verifiable work
Demonstrated reliability over time
That signal matters, inside Btrust Builders and far beyond it.
Last updated