Academy Projects Space Randomness Beacon
Cybersecurity

Space Randomness Beacon

Generate random numbers onboard using a hardware RNG, continuously self test health metrics, and broadcast signed randomness blocks. Evaluate how radiation and temperature correlate with RNG performance and error flags.

8-12 months Beginner 0.5U
0.5U
Form Factor
Beginner
Difficulty
8-12 months
Timeline
2
Disciplines

About This Project

Generate random numbers onboard using a hardware RNG, continuously self test health metrics, and broadcast signed randomness blocks. Evaluate how radiation and temperature correlate with RNG performance and error flags.

Category: Cybersecurity

This is a beginner-level project with an estimated timeline of 8-12 months using a 0.5U form factor.

Overview

Random numbers are a foundational building block of cryptography, scientific simulation, and fair decision-making systems. Generating truly random numbers — as opposed to pseudorandom sequences — requires a physical entropy source. A hardware random number generator on a satellite operates in a uniquely isolated environment: no network connections, no electromagnetic interference from nearby electronics at scale, and continuous exposure to cosmic radiation that may itself contribute entropy. This payload generates random numbers continuously, runs statistical health tests to verify their quality, and broadcasts cryptographically signed blocks of randomness that anyone on the ground can receive and verify. The experiment investigates whether the space radiation environment — particularly passages through high-radiation zones — affects the quality or performance of the random number generator, producing data that is relevant to both space cybersecurity and fundamental randomness research. The signed broadcast creates a publicly verifiable randomness beacon — a concept with applications in lottery systems, blockchain protocols, and multi-party computation. This is the simplest cybersecurity payload in the catalog, requiring minimal hardware and straightforward firmware.

Technical Details

ATECC608B FIPS 800-90 hardware TRNG (~$7, I2C) generates random numbers continuously. Secondary entropy source: ADC noise from unconnected analog input on payload MCU. Health monitoring: NIST SP 800-90B statistical tests (monobit, runs, longest run) executed onboard every N samples. Broadcast signed 256-bit random blocks at fixed intervals via UHF beacon. Each block includes: random data, timestamp, GPS position, temperature, TRNG health status, ECDSA signature. Ground stations worldwide can receive and verify. Evaluate correlation between radiation environment (SAA passes) and TRNG health metrics.

Research & Notes

Cryptosat (backed by YC) demonstrated the concept of a space-based trusted randomness beacon. Key value proposition: randomness generated in physically isolated environment (orbit) is verifiable and tamper-resistant. ATECC608B TRNG is NIST-certified but performance in radiation environment is uncharacterized — this experiment fills that gap. Broadcasting signed random numbers does not require encryption — compatible with amateur radio regulations. Cost: $100-$300. Complexity: beginner — the simplest cybersecurity payload. Hardware is identical to projects 13 and 26 — shared ATECC608B. Interesting secondary experiment on any mission.

Required Disciplines

This project spans 2 disciplines, making it suitable for interdisciplinary student teams.

CS
EE

Next Steps

Ready to take on this project? Here's a general roadmap that applies to most CubeSat missions:

  1. Build your foundation: Complete the core modules in the CubeSat Academy to understand spacecraft subsystems, mission design, and development workflows.
  2. Form a team: Recruit students across the required disciplines and identify a faculty advisor. Plan for knowledge transfer between graduating and incoming members.
  3. Write a mission concept: Draft a 1–2 page document outlining your objectives, target orbit, payload requirements, and success criteria.
  4. Connect with a chapter: Join a Blackwing chapter for mentorship, shared resources, and access to the platform ecosystem.
  5. Explore the developer tools: Visit the Developer Portal for platform documentation, SDKs, and hardware specs.
  6. Plan your timeline: Map milestones to your academic calendar. Most projects align well with a 2–4 semester capstone or research sequence.
  7. Reach out: Contact us to discuss your project goals, platform selection, and path to orbit.

Ready to start this mission?

Connect with a Blackwing chapter for mentorship, platform access, and a path to orbit.

Find a Chapter CubeSat Academy