Seedless randomness extractors for device-independent quantum key distribution (DI-QKD). Truncation-based proof technique achieves optimal rate of one key bit per singlet without requiring initial randomness seeds. Use when implementing DI-QKD, designing quantum cryptographic protocols, evaluating privacy amplification methods, or analyzing device-independent security proofs. Activation: device-independent QKD, seedless extractor, privacy amplification, DI cryptography, randomness extraction,...
Scanned 9/11/2026
Install to Claude Code
npx -y skills add hiyenwong/ai_collection --skill seedless-di-qkd-extractors --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Seedless Di Qkd Extractors?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hiyenwong-seedless-di-qkd-extractors)More formats (shields.io, HTML) on the badges page.
---
name: "seedless-di-qkd-extractors"
description: "Seedless randomness extractors for device-independent quantum key distribution (DI-QKD). Truncation-based proof technique achieves optimal rate of one key bit per singlet without requiring initial randomness seeds. Use when implementing DI-QKD, designing quantum cryptographic protocols, evaluating privacy amplification methods, or analyzing device-independent security proofs. Activation: device-independent QKD, seedless extractor, privacy amplification, DI cryptography, randomness extraction, Bell violation, quantum key distribution"
---
# Seedless Extractors for Device-Independent QKD
High-rate seedless randomness extraction for DI quantum cryptography. Based on arXiv:2605.31525 (Lin, Foreman, Masanes, 2026).
## Problem Statement
DI quantum cryptography requires randomness extractors for privacy amplification, but traditional extractors need an initial seed of randomness — a potential vulnerability. Previous seedless approaches required many rounds to estimate Bell violations, consuming substantial randomness.
## Solution: Truncation-Based Seedless Extraction
New proof technique using truncation method that:
- Estimates protocol parameters with asymptotically vanishing fraction of rounds
- Achieves optimal rate: **1 key bit per singlet**
- Uses computationally efficient seedless extractors
## Core Architecture
```
Raw DI data (Bell violation) → Truncation → Bell violation estimate → Seedless extractor → Secure key
```
### Key Innovation
Instead of using min-entropy as the extractor promise (traditional), use the **Bell violation** of the raw data directly. The truncation method reduces estimation variance dramatically.
## Implementation Pattern
### Step 1: Bell Violation Estimation
```python
def estimate_bell_violation(raw_data, sample_fraction=0.01):
"""Estimate CHSH Bell violation from truncated sample.
Args:
raw_data: list of (a, b, x, y) tuples (Alice output, Bob output,
Alice input, Bob input)
sample_fraction: fraction of rounds to use for estimation
Returns:
Estimated CHSH value S ∈ [2, 2√2]
"""
n = len(raw_data)
sample_size = max(int(n * sample_fraction), 1)
sample = raw_data[:sample_size]
# CHSH = E[AB|00] + E[AB|01] + E[AB|10] - E[AB|11]
chsh_terms = []
for x, y in [(0,0), (0,1), (1,0), (1,1)]:
subset = [(a,b) for (a,b,xi,yi) in sample if xi==x and yi==y]
if not subset:
return 0 # insufficient data
correlations = [a*b for a,b in subset]
chsh_terms.append(np.mean(correlations))
return chsh_terms[0] + chsh_terms[1] + chsh_terms[2] - chsh_terms[3]
```
### Step 2: Truncation-Based Security Proof
The truncation method bounds the tail of the Bell violation distribution, enabling tight finite-size analysis:
```
ε-security ≤ exp(-n · D(S_est || S_threshold)) + O(1/√n)
```
where D is the relative entropy between estimated and threshold Bell values.
### Step 3: Extractor Application
```python
def seedless_extract(raw_bits, bell_violation, min_rate=0.9):
"""Apply seedless extractor using Bell violation as entropy source.
Args:
raw_bits: raw key bits from measurement outcomes
bell_violation: estimated CHSH value
min_rate: minimum extraction rate (bits per raw bit)
Returns:
Extracted secure key bits
"""
# S > 2 implies quantum correlations → extractable randomness
if bell_violation <= 2.0:
raise ValueError("No Bell violation detected — no quantum security")
# Extraction rate depends on Bell violation strength
# For S → 2√2 (maximal violation), rate → 1.0
rate = compute_extraction_rate(bell_violation)
if rate < min_rate:
raise ValueError(f"Extraction rate {rate} below minimum {min_rate}")
# Apply seeded Toeplitz matrix extractor
# Seed derived from public randomness (acceptable in DI setting)
return toeplitz_extract(raw_bits, rate)
```
## Rate Analysis
| Bell Violation (S) | Extraction Rate | Notes |
|-------------------|-----------------|-------|
| 2.0 (classical) | 0 | No extractable randomness |
| 2.1 | ~0.1 | Weak quantum correlations |
| 2.5 | ~0.5 | Moderate violation |
| 2.8 (near max) | ~0.95 | Strong quantum correlations |
| 2√2 ≈ 2.828 | 1.0 | Optimal rate |
## Comparison with Prior Work
| Method | Requires Seed? | Rate | Rounds Needed |
|--------|---------------|------|---------------|
| Traditional extractors | Yes | Variable | N/A |
| Quantum 9, 1654 (2025) | No | Low | Many |
| This work (truncation) | No | **1.0** | Few |
## Security Assumptions
1. **No-signaling**: Alice and Bob devices cannot communicate during measurement
2. **Measurement independence**: Inputs x, y chosen independently of internal device state
3. **Authenticated classical channel**: Prevents man-in-the-middle on public discussion
## Related Work
- arXiv:2606.04669 — PQC-HOT framework (complementary quantum-safe security approach)
- arXiv:2606.05696 — QFI bounds on entanglement robustness
- arXiv:2606.06490 — Coherent dipole synchronization (room-temperature quantum platform)
## Activation Keywords
- device-independent QKD, seedless extractor, privacy amplification
- DI cryptography, randomness extraction, Bell violation, quantum key distribution
- DI-QKD security proof, quantum randomness, extraction rate
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!