An interdisciplinary demonstration of post-quantum cryptography, blockchain risk awareness, and sustainable distributed trust through interactive user experience and real quantum hardware execution.
“What I cannot create, I do not understand.”
— Richard Feynman
⚛️ Quantum Computing • 🔐 Post-Quantum Cryptography • ⛓️ Blockchain Security • ☁️ AWS Braket
Quantum Blockchain Interactive is a research demonstration exploring the transition toward quantum-resilient blockchain infrastructure through a guided interactive experience.
The platform integrates:
- ⚛️ post-quantum cryptography,
- ⛓️ blockchain security risk awareness,
- ☁️ real quantum hardware execution,
into a unified demonstrator designed for interdisciplinary audiences.
The demo illustrates:
- how advances in quantum computing affect current blockchain cryptographic assumptions,
- how post-quantum cryptographic mechanisms can be introduced through participatory interfaces,
- how infrastructure decisions and stakeholder perception influence adoption dynamics,
- how distributed trust systems evolve under emerging computational paradigms.
Unlike demonstrations focused solely on protocol implementation or algorithmic benchmarking, this system emphasizes the interaction between technical security mechanisms, ecosystem understanding, and adoption processes. Participants experience post-quantum migration through a structured interaction flow culminating in the generation of a quantum-resistant cryptographic artifact using Amazon Braket.
Quantum Blockchain Interactive is an interactive web platform designed for:
- 🎤 live demonstrations
- 🧪 workshops and exhibitions
- 🌍 public engagement
The experience connects quantum computing progress, blockchain security challenges, and post-quantum cryptography through a structured user journey.
Participants move from scientific context and risk awareness to participatory interaction and infrastructure exploration, concluding with the generation of a quantum-safe cryptographic key — a personalized Quantum-Safe Blockchain Passport.
The project serves simultaneously as:
- 📘 an educational interface for emerging cryptographic transitions,
- 🔬 a research demonstration of interdisciplinary technology adoption,
- 🚀 a deployable interactive system for events and exhibitions.
- Experience (UI Journey)
- System Architecture
- Configuration
- Getting Started (Local Development)
- Cloud Deployment
The application presents a 7-page guided interaction flow that progressively introduces quantum computing concepts and blockchain security implications while remaining accessible to mixed technical audiences.
👉 Detailed UI documentation:
docs/ui-information/Readme.md
| Page | Screen | Experience Goal | UI Module |
|---|---|---|---|
| Page 1 | Nobel Prize Context | Establish scientific grounding | Scientific context module |
| Page 2 | Quantum Meets Blockchain | Explain quantum threat and PQC transition | Threat analysis module |
| Page 3 | Experience Overview / Consent | Establish transparency and participation rules | Consent & session module |
| Page 4 | Public Sentiment | Capture perception and engagement | Sentiment input module |
| Page 5 | Results & Industry Voting | Aggregate community priorities | Voting & visualization module |
| Page 6 | Device Selection | Explore infrastructure and hardware tradeoffs | Device exploration module |
| Page 7 | Quantum-Safe Passport | Present cryptographic outcome artifact | Key generation & result module |
The interaction flow mirrors real-world technology adoption and post-quantum transition processes.
| Design Principle | Pages | Role in Experience |
|---|---|---|
| Context → Understanding | Pages 1–2 | Establish shared scientific and security context |
| Participation → Reflection | Pages 3–5 | Transform learning into interaction and feedback |
| Decision → Outcome | Pages 6–7 | Connect infrastructure choices to cryptographic results |
This progression allows participants to understand post-quantum migration as both a technical and socio-technical transition involving research, engineering, governance, and investment perspectives.
A protected dashboard at /dashboard provides:
- 📊 session monitoring and activity metrics
- 🔑 invite code management
- ☁️ sentiment and voting aggregation
- 📝 feedback review and export
The application is deployed as a single-stack, serverless web system on AWS. It is optimized for live demos and workshops: low operational overhead, fast global delivery, and strict separation between the browser UI and privileged cloud operations (data + quantum execution).
CloudFront (CDN) → API Gateway (HTTP) → Lambda (Next.js / Docker ARM64)
│
┌───────────┼───────────┐
DynamoDB Lambda S3
(7 tables) (Braket) (feedback)
| 🌍 CloudFront (CDN) | Serves the UI and static assets (images, scripts) from edge locations to reduce latency during public events. Dynamic requests (API calls and server-rendered routes) are forwarded downstream. |
| 🚪 API Gateway (HTTP) | Provides the public HTTP entry point for the application’s server-side endpoints. It establishes request boundaries (routing, throttling) between the internet and compute functions. |
| ⚙️ Lambda (Next.js / Docker ARM64) | Runs the Next.js application as a serverless container. This layer performs server-side rendering and hosts API routes for session orchestration, consent gating, sentiment/voting submission, and result retrieval—while ensuring no AWS credentials are ever exposed to the browser. |
| 🗄️ DynamoDB (7 tables) | Persists interaction artifacts and operational state with burst-friendly scaling. Typical tables include sessions, sentiments, industry votes, generated key metadata, invite codes, admins, and feedback metadata. |
| ⚛️ Lambda (Braket) | Isolates quantum execution from the web runtime. It submits tasks to Amazon Braket (simulators or QPUs), tracks job status, and returns device/job metadata used to render auditable outcome artifacts (the “Quantum-Safe Passport”). |
| 📦 S3 (feedback) | Stores optional large uploads such as feedback attachments or exported artifacts. DynamoDB retains associated metadata and pointers. |
- Performance for live audiences: CloudFront reduces global latency and stabilizes UI delivery under burst traffic.
- Security by design: the browser never holds AWS credentials; privileged operations (data writes + Braket jobs) happen server-side.
- Auditability of outcomes: quantum execution returns job/device metadata that can be surfaced in the final results page for traceability.
- Operational simplicity: a single CDK stack provisions the system; one deployment path supports repeated event setups.
In summary, the stack is designed to keep the interactive experience responsive and reliable while supporting real post-quantum workflow integration with quantum hardware.
Application behavior is configured through environment variables used in both local development and cloud deployment.
Create:
frontend/.env.localExample:
AWS_REGION=us-east-1
ADMIN_API_KEY=your-keyEnvironment variables are injected into Lambda functions through AWS CDK during deployment. These values remain server-side and are never exposed to the browser.
| Variable | Required | Default | Description |
|---|---|---|---|
AWS_REGION |
No | us-east-1 |
AWS region for DynamoDB and Braket |
ADMIN_API_KEY |
Yes | — | Admin dashboard authentication |
DDB_TABLE_SESSIONS |
No | qc-bc-sessions |
Sessions table |
DDB_TABLE_SENTIMENTS |
No | qc-bc-sentiments |
Sentiment storage |
DDB_TABLE_INDUSTRY_VOTES |
No | qc-bc-industry-votes |
Voting storage |
DDB_TABLE_QUANTUM_KEYS |
No | qc-bc-quantum-keys |
Generated keys |
DDB_TABLE_INVITE_CODES |
No | qc-bc-invite-codes |
Invite code storage |
Run the application locally for development or testing.
- Node.js 20+
- Docker
- AWS CLI configured
- AWS CDK v2
cd frontend
npm install
cp .env.example .env.local
npm run devApplication runs at:
http://localhost:3000
Deploy the application to AWS using CDK:
./deploy.shDeployment performs:
- Frontend container build
- Infrastructure provisioning via AWS CDK
- Lambda, API Gateway, DynamoDB, and CloudFront configuration
- Output of the public application URL
After deployment, the application runs fully serverlessly and is ready for live demonstrations or production use.