Quantum Art Lab

When you measure a qubit on real quantum hardware, you don't always get the truth. A qubit prepared as |0> sometimes reads back as 1 , and vice versa. These readout errors are some of the most common and controllable sources of noise in modern processors — and unlike decoherence or gate infidelity, they're comparatively easy to model and correct with classical post-processing. This post is the practical version of that correction. Where the theory of quantum error correction (which we've covered elsewhere) deals with protecting the state with logical qubits, measurement error mitigation is a lighter-weight trick: characterize how often the machine misreads, then undo that on the distribution you observe. No extra qubits, no complex codes — just calibration and a matrix multiply. Where readout errors come from A qubit is a physical device (superconducting circuit, trapped ion, etc.). When you "measure" it, the machine maps its state to a classical signal ...

Every developer has heard the disclaimer: "not secure for post-quantum use." Most of us have ignored it. In 2026, that's no longer a safe posture. The migration is no longer hypothetical — the new standards are public, the libraries have shipped, and "harvest now, decrypt later" attacks mean the data you send today could be broken years from now. I'm a developer, not a cryptographer. This post is the practical lay-of-the-land I've built up reading the standards, running the tools, and figuring out what actually changes in a real codebase — the algorithms, what they replace, and the concrete migration steps for a web app or a smart contract. What "quantum" actually threatens Quantum computers threaten a specific class of classical math: factoring and discrete logarithms . RSA, elliptic-curve Diffie-Hellman (ECDH), ECDSA — the workhorses of TLS, SSH, and virtually every cryptocurrency — all rest on problems a sufficiently large quantum compu...

Quantum Key Distribution (QKD) is the rare quantum protocol that does something classical cryptography genuinely cannot: it lets two parties detect, in real time, whether an eavesdropper was listening to their key exchange. The security doesn't come from computational hardness — it comes from measurement disturbance, one of the few aspects of quantum mechanics that holds up even against an adversary with infinite computing power. This post walks through the oldest and most practical of these protocols, BB84 , from the raw qubits up to a working Qiskit implementation. No math degree required — just circuits, Python, and the willingness to re-sift a key. The problem BB84 solves Two parties, Alice and Bob, want to share a secret random bit string. A classic approach — Diffie-Hellman — is secure only if the enemy can't solve a hard math problem. But a future quantum computer (or a patient classic one) could break it. BB84 sidesteps the math entirely: Alice sends information enc...

When we first seeded Quantum Genesis, we ran circuits the old way: build a circuit, call execute() or backend.run() , and wait for a Result object with raw counts. It worked, but every run felt like negotiating with the machine directly. Since then the Qiskit SDK has moved to a model built around the primitives — first Sampler / Estimator (V1), now SamplerV2 / EstimatorV2 on Qiskit Runtime. This post is the mental model I wish I'd had, with code you can run today. If you've been following old tutorials and finding that qiskit.execute no longer exists, or that IBMQ.save_account is gone, this is the update you need. The days of manually transpiling and submitting a single circuit to backend.run() for every experiment are over. Modern Qiskit wants you to think in terms of what you want to compute , not how to shuffle bits from the QPU. Why the primitives exist The old flow forced you to become an expert in the transport layer: pick a backend, submit a job, poll for sta...

For the first fifteen years of crypto, "digital scarcity" meant one thing: social consensus enforced by code. Bitcoin's 21M cap holds up because miners keep agreeing on the rules. NFTs are "limited" because a smart contract and a marketplace agree on the number. An Art Blocks release is scarce because of artist reputation and platform curation. Every limited edition in crypto is limited because we all agree it is. That arrangement works — until it doesn't. Forks happen. Contracts get upgraded. Marketplaces delist. Narratives shift. The scarcity is only as strong as the consensus holding it, and consensus is something people can always change their minds about. With Quantum Genesis we tried a different foundation: physics. Let me explain what that actually means, because I don't think "physics-backed" should be a marketing buzzword. It should be a specific technical claim you can check. Consensus-based scarcity and its failure modes The con...

I used to do everything with Math.random() and a seeded PRNG, the same way every generative art platform does. Art Blocks, fxhash, most custom pipelines — they all start from a pseudorandom number generator. And whenever the question of "true" randomness came up, the answer was always the same: "It passes statistical tests. It's random enough for art." For aesthetics, that's true. For uniqueness, it's false — and that's the part that matters when you're promising someone a one-of-one. "Random enough" is a category error, and I want to show you the math, because in this post I'll make the full argument: every PRNG is deterministic, every PRNG is reversible, and every PRNG has a finite state space. Then I'll show where a quantum measurement breaks each of those limits. First, the claim everyone makes The stock defense of a PRNG is that its output is computationally indistinguishable from random — no efficient algorithm can t...

Quantum Genesis needed 100 quantum seeds, one per NFT. We started on Origin Quantum's WK_C180 and produced the first 18 pieces there. Then we switched to IBM Quantum (ibm_fez and ibm_torino) for the remaining 82. I want to be upfront about why: this wasn't a strategy we designed, it was a necessity forced on us, and the comparison below is honest field notes rather than a curated spec sheet. Before relying on vendors' claims, we'd spent the previous weeks building a working pipeline — the QRNG approach is laid out in the generator post , and my earlier Origin vs IBM comparison captured the first impressions. This post is the production version of that, at 100 jobs. The hardware, side by side Metric Origin Quantum WK_C180 IBM Quantum ibm_fez IBM Quantum ibm_torino Qubits 180 156 133 Topology Not fully public Heavy-hex (fixed coupling) Heavy-hex (fixed coupling) SDK pyqpanda3 Qiskit Runtime (SamplerV2) Qiskit Runtime (SamplerV2) Access model QCloudService API (privat...

I've been burned by impostor collections before — by that I don't mean losing money, I mean the specific incompetence of almost minting a token from a copycat contract because the marketplace page looked right. So when we shipped Quantum Genesis, I wrote the verification checklist I wished I'd had. This post is that checklist, and it doubles as an explanation of what a Quantum Genesis token actually is. I'm going to skip the "how to buy" part on purpose. If a piece of this collection matters to you, the thing worth learning is how to verify it — the seed, the certificate, the rarity tiers — and that's transferable to any on-chain art you look at. If you're new to the general mechanics of listing and trading, my OpenSea walkthrough covers that ground separately. What a token actually is When a Quantum Genesis piece changes hands, what transfers is a bundle that's unusual compared to typical "digital art": A unique quantum measurement...

Provenance is the boring part of art, which is why it's usually the forged part. In the traditional world it's a paper trail — certificates, gallery receipts, expert opinions — all of it forgeable, all of it dependent on trust in whoever holds the stack of paper. Classical generative NFTs improved on that: provenance becomes a transaction hash plus an algorithm. But the seed is usually a PRNG output, which — as I covered in the min-entropy post — is deterministic and theoretically reversible. The provenance is better, but the "uniqueness" underneath it can be reconstructed. What we built with Quantum Genesis is a different record: each piece embeds a quantum measurement certificate — a record of a physical event that happened once, on specific hardware, at a specific microsecond, governed by the Born rule. I want to show you the whole chain, from the seed to the on-chain record, so you can verify any piece yourself instead of trusting this blog post. Why provena...

Solidity contracts usually grow features as the project does, which is how you end up with an admin key, a pause function, and a roadmap-dependent supply. For Quantum Genesis I deliberately went the opposite direction: a contract small enough that "the team can't mess with it later" is a property you can eyeball. The whole thing came out to a box of constraints: a fixed supply of 100 that no one can extend, batch minting to keep gas down, royalties enforced by the contract rather than by marketplace goodwill, metadata that freezes permanently, and zero admin keys. This is the build log — what I needed, the choices that followed, and the exact code. If you want the broader deployment context, the minting-on-Polygon post covers the why; this one is the how. The requirements, non-negotiable 100 NFTs, fixed supply — no minting after deployment Batch minting — 10–20 NFTs per transaction to keep gas down 5% royalties enforced everywhere — OpenSea, Blur, LooksRare, any E...

Once the last circuit had run and the metadata was pinned, I still had to face the step I'd been dreading: rarity. In most collections, that's where someone on the team opens a spreadsheet and decides which traits are rare — often after the mint has already happened. I wanted no part of that, and luckily the pipeline we'd built left us no room to do it even if we'd wanted to. Every rarity attribute in Quantum Genesis is a derived quantity. It's computed from the measurement distribution itself, written into the metadata before anything went on-chain, and it's not editable afterward — not even by us. This post goes through what the numbers actually did: where the entropy scores landed, which color harmonies the seed's first outputs picked, how the phase attribute came to exist, and which ten pieces rose to the top of the composite ranking. The one thing we never assigned Most NFT projects manufacture rarity: "Only 10 have gold backgrounds!" or ...

When we started Quantum Genesis, we weren't trying to invent a new asset class. We were trying to answer a narrower question: can you build a generative project whose origin story is actually verifiable, starting from physics up? This post is that answer — a blueprint, honestly labeled. It covers how supply is enforced, how provenance can be checked, and where the approach starts to bend. Most "scarcity" in digital art is an agreement. A contract says there are 100 of these, a marketplace agrees to keep it that way, and everyone trusts the combination. That arrangement works — until someone forks, migrates, or simply changes the narrative. Quantum Genesis takes a different route on exactly one attribute: the seed behind each piece is a quantum measurement, and a measurement outcome is a one-time physical event that cannot be reproduced, in principle. Three ways things end up scarce Scarcity Source Examples Vulnerability Physical uniqueness Mona Lisa, rare earth elemen...

This is the post I wanted to read before we started. After the 100 pieces were minted, I went back through our notes, the deployment logs, and the code, and wrote down exactly how each layer was built — including the rough edges (the queue time on ibm_fez, pyqpanda3 shipping breaking changes mid-project). Not because any of it is glamorous, but because the whole point of this project is that the pipeline can be checked. If you're going to trust that the seeds came from real hardware, the infrastructure itself has to be open. At a glance, Quantum Genesis is a distributed quantum-classical pipeline spanning three compute paradigms. Every layer is auditable, every transition is deterministic. The only non-deterministic event — the quantum measurement — happens once, is recorded, and from that moment the entire pipeline becomes reproducible from a single seed. System architecture ┌─────────────────┐ ┌──────────────────┐ ┌────────────────────┐ │ QUANTUM LAYER │────▶│ CLASS...