Implement a Proof-of-Stake Consensus Mechanism in Rust

FreeVerified credential4 weeksExpert

Overview

What this challenge is about.

Implement a Proof-of-Stake Consensus Mechanism in Rust. Expert-level challenge in code. Writing production code that solves real engineering problems, earn a...

CredentialBlockchain-anchored

ShareableLinkedIn-ready

LanguageEnglish

PaceSelf-paced

The Brief

What you'll do, and what you'll demonstrate.

Implement Casper-FFG-style PoS consensus in Rust, simulate it on a 21-validator network, and demonstrate safety + liveness under partition and equivocation.

This is not a coding exercise. It is the work a software engineer does between a Jira ticket and a merged PR. That distinction matters to every hiring manager who has seen candidates solve LeetCode problems and none who have shipped production code under real constraints.

When you finish, you will have something most graduates do not: a real-world deliverable, verified by Ewance, that you can show to a hiring manager and say "I did this. Here is the proof."

Earning criteria — what you'll demonstrate

Implement a non-trivial consensus algorithm from the original paper
Reason about safety + liveness under realistic failure modes
Build a deterministic simulator for protocol research
Communicate consensus properties in a paper-quality writeup

Program Fit

Where this fits in your program.

Sharpens the same skills your degree expects you to demonstrate.

Blockchain and Decentralized Systems Engineering

Master · Software Engineering

Strong alignment

This challenge maps to Blockchain and Decentralized Systems Engineering at the Master level. It sharpens the same practical skills your coursework expects — but in a real industry context with actual constraints and deliverables.

Skills

Skills you'll demonstrate.

Each one shows up on your verified credential.

Careers

Career paths this challenge builds toward

Completing this challenge demonstrates skills that transfer directly to these roles:

Career paths this builds toward

Canonical roles

Systems Architect
Systems architects make the decisions whose consequences are felt for years. The role is about choosing: which cloud provider, which integration pattern, which trade-off between cost and reliability deserves an Architecture Decision Record so the next team understands the reasoning. You'll work in C4 diagrams, ArchiMate models, and the AWS or Azure Well-Architected Framework, but the real artifact is clarity of thought. Strong architects know when to standardize and when to let a team diverge, and they write documents that survive a leadership change. Students drawn here usually loved their distributed systems course and are patient enough to think before they build. Growth happens through scars: owning architectures end-to-end, watching them strain under real load, and learning which abstractions earned their place.
Platform & Infrastructure

One more thing

You can put a credential on your CV by Friday.

Start this challenge