Skip to contentSkip to content
Verified credentials. On-chain. Forever.Learn more
Ewance
Sign in
Cover image for Assess Secure Cross-Bank Fraud Computation for a Four-Bank Consortium
Code

Assess Secure Cross-Bank Fraud Computation for a Four-Bank Consortium

FreeVerified credential3 weeksExpert

Overview

What this challenge is about.

Build a private cross-bank fraud computation on MP-SPDZ, benchmark three dataset sizes, and earn a verifiable certificate.

The scenario

A consortium of four mid-sized European banks, each holding EUR 30–90 billion in assets, suspects that organized fraud rings exploit the gaps between institutions, and they want to pool fraud signals without any bank exposing its customers' transactions to the others or to a central operator.

CredentialBlockchain-anchored
ShareableLinkedIn-ready
LanguageEnglish
PaceSelf-paced

The Brief

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

Decide whether secure multi-party computation can compute joint cross-bank fraud signals correctly and fast enough to be production-viable at one million records per bank, and justify the verdict with a working demo and measured evidence.

Earning criteria — what you'll demonstrate

  • Implement private set intersection and a private joint aggregate as multi-party protocols where no party reveals its own inputs.
  • Verify cryptographic protocol output against a trusted plaintext baseline to prove correctness rather than assume it.
  • Measure and interpret how secure-computation cost (time and bandwidth) scales with input size and identify the dominant bottleneck.
  • Translate threat-model choices (honest-but-curious versus malicious) and operational risks into a clear adoption recommendation for non-technical risk committees.
  • Package a distributed multi-party system for one-command, reproducible bring-up.

Program Fit

Where this fits in your program.

Sharpens the same skills your degree expects you to demonstrate.

Aligned coursework coming soon.

Careers

Career paths this challenge builds toward

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

Privacy Engineer

Building a working private-computation demo and judging its real-world cost is exactly what privacy engineers do when evaluating data-sharing technologies; you practice turning a privacy requirement into a measured, defensible engineering recommendation.

This challenge sharpens

  • privacy-engineering
  • secure-computation
  • benchmarking

Applied Cryptography Engineer

Implementing and verifying multi-party protocols against a plaintext oracle, then reasoning about honest-but-curious versus malicious threat models, mirrors the daily work of shipping cryptography that must be both correct and fast enough to deploy.

This challenge sharpens

  • cryptography
  • mpc
  • secure-computation

Security Engineer, Financial Services

Banks increasingly need engineers who can prototype privacy-preserving systems and communicate their limits to risk committees; this challenge bridges hands-on protocol coding with the regulatory and operational judgment that financial security roles demand.

This challenge sharpens

  • mpc
  • python-programming
  • privacy-engineering

One more thing

You can put a credential on your CV by Friday.