Backend
How wide must an eavesdropper be? Leakage of a toric-code logical bit to a strip and the Nishimori point
arXiv cs.CR0 views
arXiv:2611.13174v1 Announce Type: cross Abstract: Fault-tolerant quantum computers hand pieces of each logical qubit to separate decoder modules and shared readout lines. How much does a piece reveal? We prove that for any region and any Pauli noise, including correlated noise, an observer's optimal advantage in learning a logical bit is exactly 1 - 2 P_fail, where P_fail is the failure probability of maximum-likelihood decoding confined to that region. Two lessons follow. Geometry, not noise, provides the protection: a region that misses a single column of the code learns exactly nothing at any noise level, while a region that spans the code is protected by noise only at impractical distances (d > 350 for one row at a 10^-3 flip rate). And width is a poor guide to risk: under i.i.d. noise a two-row strip learns exactly as little as one row, yet below threshold an eavesdropper needs a width growing only as ln d. Through the identity, the strip's operational threshold is the Nishimori point of the random-bond Ising model, and a Walsh-Hadamard transfer matrix up to width 16 locates it to within a few thousandths. On two IBM Heron processors (d = 3, 5), an emulated strip adversary shows the predicted jump at width three, and non-uniform qubit errors let a trained attacker profit from the second row that uniform noise makes useless. We turn these results into design rules for partitioned decoding and multiplexed readout. Code and data are included.
Source:https://arxiv.org/abs/2611.13174PreviousHow Well Do SAST Tools Work Across Languages? An Empirical Study Using OCPP ImplementationsNextVeritas: A Verifier Generation Harness for Agent Tasks
Related posts

How Does AWS Protect Sensitive Data? Understanding AWS KMS, Encryption & Key Management
0dev.to AWS
How Conditional Email Routing Rules Work
0dev.to Security
SOC 2 Readiness for SaaS Companies: A Developer's Guide to Security Controls and Audit Preparation
0dev.to Security
CRA Annex I for mobile apps: a practical checklist mapped to OWASP MASVS
0dev.to Security

Your SOC 2 report doesn't answer a single AI question
0dev.to Security
The Second App Problem: Every Hosted Health MCP Is Also an App You Have to Keep Installed
0dev.to Security