Duration: 50 minutes | Points: 40 | Format: Team debate (4 teams)
Learning Objectives
- Analyze the tradeoffs between different consensus mechanisms (PoW, PoS, DPoS, BFT)
- Apply the blockchain trilemma framework to real-world use cases
- Evaluate consensus design decisions in context of specific application requirements
- Develop critical argumentation and technical communication skills
The Blockchain Trilemma
Every consensus mechanism must balance three competing goals:
Decentralization
No single entity or small group controls the network
Security
Resistant to attacks, reliable finality
Scalability
High throughput, low latency
The challenge: optimizing one dimension often requires compromising another.
Assignment Structure
0-5 min: Team formation and preparation. Each team receives a prep sheet for their assigned consensus mechanism.
5-25 min: Round-robin debates. Teams present 2-minute opening arguments, followed by 3-minute cross-examination from opposing teams.
25-40 min: Use case analysis. Teams receive scenario cards and must argue why their mechanism best fits that application.
40-47 min: Anonymous peer voting. Students vote for strongest arguments (cannot vote for own team).
47-50 min: Instructor debrief and key takeaways.
Teams and Mechanisms
| Team | Mechanism | Core Argument |
|---|---|---|
| Team 1 | Proof of Work (PoW) | Proven security and maximum decentralization |
| Team 2 | Proof of Stake (PoS) | Energy efficiency and economic security |
| Team 3 | Delegated PoS (DPoS) | Performance and democratic governance |
| Team 4 | Byzantine Fault Tolerance (BFT) | Instant finality and consistency |
Debate Format
Phase 1: Opening Statements (2 minutes each)
- Present your mechanism's strongest advantages
- Position it within the blockchain trilemma
- Provide 2-3 concrete examples (networks using this mechanism)
Phase 2: Cross-Examination (3 minutes per team)
- Other teams ask challenging questions
- Defend against known weaknesses
- Counter-attack other mechanisms' vulnerabilities
Phase 3: Use Case Defense (3 minutes per scenario)
- Receive a specific application scenario
- Argue why your mechanism is the optimal choice
- Address requirements: performance, security, governance
Presentation Requirements
Each team must:
- Use the provided prep sheet as a foundation
- Cite specific data points (energy consumption, TPS, validator counts)
- Reference at least 2 real-world blockchain implementations
- Demonstrate understanding of tradeoffs, not just list benefits
- Engage respectfully with opposing arguments
Grading (40 Points)
| Criterion | Points |
|---|---|
| Technical accuracy and depth of understanding | 12 |
| Quality of arguments and use of evidence | 10 |
| Engagement with opposing views (cross-exam) | 8 |
| Application to use case scenarios | 6 |
| Presentation clarity and team coordination | 4 |
Materials Provided
- Mechanism-specific prep sheets (4 sheets, one per team)
- Use case scenario cards (6 cards)
- Anonymous voting ballots
- Grading rubric
Tips for Success
- Prepare counterarguments: Anticipate what opponents will attack and have responses ready
- Use data: Numbers beat vague claims (e.g., "Bitcoin uses 150 TWh/year vs. Ethereum PoS at ~0.01 TWh/year")
- Context matters: No mechanism is universally best—emphasize fit for specific use cases
- Be honest about tradeoffs: Acknowledging weaknesses builds credibility
- Listen actively: Best rebuttals respond directly to points just made
Related Resources
Assignment Resources
© Joerg Osterrieder 2025-2026. All rights reserved.