Resources for students working on Bitcoin projects.

What students usually need from a Bitcoin page

Most students arrive here under deadline, looking for three things: a clean way in, a defensible set of sources, and a topic angle that does not collapse under five minutes of review. We try to provide all three without turning the page into a checklist of clichés.

Project and essay angles that hold up

These are angles that tend to produce good marks because they have enough depth for analysis without requiring you to predict the future of a market.

• How Bitcoin's design solves a specific consensus problem and what it gives up to do so.
• The difference between Bitcoin and "blockchain" as marketing language, with examples from real corporate announcements.
• The role of nodes versus miners in enforcing network rules, and why this matters during contentious upgrades.
• How fee markets behave under congestion, illustrated with public data.
• Case studies of countries where unstable local currency has driven real Bitcoin use.
• The human side of security failures in self-custody, drawing on published case studies rather than gossip.
• Energy use of mining with both critical and steel-manning arguments, supported by named sources rather than slogans.
• Open-source governance of Bitcoin compared to other long-lived software projects.

Angles to avoid for class assignments

• "Will Bitcoin's price reach X by year Y" - this is not analysis, it is guessing.
• "Bitcoin is going to replace all money" - too sweeping, too unverifiable, too cliché.
• "Bitcoin is a scam" without engaging with the actual design - equally unserious.
• "Compare every cryptocurrency" - too broad, too shallow, and likely to fail in citations.
• Topics centred on specific exchange or wallet products - those move too fast to cite cleanly.

A defensible source layer

For Bitcoin specifically, a defensible bibliography usually mixes the following:

• The Bitcoin whitepaper as primary source material.
• Bitcoin Improvement Proposals for any technical claim about how the system actually behaves.
• Peer-reviewed papers from established conferences in cryptography and distributed systems.
• Books from the reading shelf for context and synthesis.
• Reputable encyclopedia entries for high-level definitions, used as a sanity check rather than a primary reference.
• Public datasets from reputable explorers or research groups for any quantitative claim.

Avoid relying on social media threads, forum posts, or marketing pages as your main sources. They are sometimes interesting, but they are rarely defensible in a viva.

Citation tips

• Cite the whitepaper directly rather than secondary summaries of it.
• When citing a BIP, include its number and the proposal status at time of citation.
• For quantitative claims, include the dataset, the time window, and the calculation, not just the headline number.
• When citing this site, link to the specific page; we do not promise that summary pages will not evolve, but we try to keep page-level URLs stable.
• Use a consistent citation style. Markers see sloppy bibliographies before they see brilliant ideas.

A simple study schedule

For most undergraduate projects with a four to six week window, the following sequence tends to work.

1. Week 1. Read bitcoin basics and the first two modules of courses. Skim one layer-one book from the reading shelf.
2. Week 2. Finish the course modules. Pick a topic angle. Draft a one-paragraph statement of what your project is arguing and what it is not.
3. Week 3. Build the source layer. Read the whitepaper and at least one peer-reviewed paper end to end. Sketch the structure.
4. Week 4. First full draft. Read it aloud once. Identify any sentence you cannot defend from a source.
5. Week 5. Revision. Strengthen the weakest section rather than polishing the strongest.
6. Week 6. Final pass. Citations, formatting, hand-in.

Groupwork prompts

For seminars and study groups, the following prompts tend to produce useful discussion rather than repetition of slogans.

• "Explain Bitcoin's fixed supply rule without using the word 'scarcity'."
• "Describe how a node decides whether to accept a new block, in your own words."
• "List three things a wallet does that an account at a bank does not."
• "What is the most expensive single mistake a beginner can make in self-custody, and why?"
• "Pick one Bitcoin Improvement Proposal and explain why it was contentious."

Working with teachers and supervisors

Some supervisors are openly enthusiastic about Bitcoin, some are openly sceptical, and many are neither. The most useful approach with any of them is to make your project a piece of careful analysis rather than advocacy. Sceptical supervisors respond well to projects that take their concerns seriously; enthusiastic supervisors respond well to projects that take the design seriously. Neither responds well to projects that read as marketing.

Safety reminder for student researchers

Studying Bitcoin does not require buying Bitcoin. If your assignment requires you to interact with a live wallet, do so on a small test setup, with throwaway funds, and only after reading wallet safety. If you are under 18, do not move funds at all for a school project, no matter how mild the amount looks. Use simulators, testnet, or paper exercises instead.

What to read next

Pair this page with courses for the curriculum spine, books for deeper reading, glossary for vocabulary checks, and educators if you are also the person setting the assignment.