QuanChain

Seven Threat Levels. One Ladder. QuanChain's oracle turns the cost of a quantum attack into one of seven threat levels. None starts at 1 million dollars per logical qubit-hour. Watch begins at 100,000, Advisory at 10,000, Elevated at 1,000, High at 100 and Critical at 10. Emergency is anything below 10. The cheaper an attack gets, the higher the level climbs. At Critical and Emergency the fast path is disabled, so every transaction goes through full consensus, and cross-chain anchoring runs every block or every transaction. A ladder, not a cliff. Each rung changes something, long before the last one.

Jargon Decoder: What Is A Hybrid Signature? Jargon decoder: hybrid signature. In plain words, it is two signatures on one transaction: a post-quantum one and a classical one. Both must verify. Think of a door with two different locks, where a thief has to beat both. Why it matters: if one scheme is ever found to be weak, the other still holds. QuanChain's middle security levels work this way, pairing a post-quantum algorithm with a classical one. Defense in depth, built into the signature.

Binance Warns Of An iPhone Wallet Risk. Binance has warned about an iPhone vulnerability that could put wallet credentials at risk. The flaw, called worse_query, is described as a sandbox escape affecting iOS 26.7.1, 27.0.1 and 27.2. Binance says it could allow a malicious app to read local files from other apps, which could include seed phrases, private keys and login credentials depending on how each app stores them. Exploiting it requires malicious code to run on the phone first. Public proof-of-concept code exists, and no thefts have been reported. Apple released updates on November 9 but has not said whether they fix this specific flaw. Binance's advice: install the latest iOS, update your apps, remove software from untrusted sources, and if an app may have been compromised, move your assets to a new wallet on a clean device. Deleting the app alone is not enough. Same lesson as this month's other incidents: keys are only as safe as the device and the software around them. Quantum resistance protects the signature layer. Device hygiene protects everything else. You need both.

Static Upgrade vs Rotating Keys. 2 ways to answer the quantum threat. A one-time upgrade publishes the public key at first spend, needs one big migration and then another, strands the wallets that miss the window, and leaves old keys exposed forever. Rotating keys reveal the key only as funds move on, upgrade each wallet at its own next spend, have no window to miss, and leave old keys guarding an empty address. One design repeats the problem at every threshold. The other removes it.

Myth: Quantum computers break everything. They don't. Two different algorithms matter, and they do very different things. Shor's algorithm breaks the math behind signatures like ECDSA. Given a public key, it can derive the private key. That is the real exposure, and it is why a visible public key is the thing to worry about. Grover's algorithm gives hashing and symmetric encryption only a square-root speedup. A 256-bit hash still leaves 128 bits of quantum security, and bigger hashes answer it. So the weak point is the signature, and only where the public key is visible. QuanChain keeps value behind an address hash and rotates keys on every spend. Know which threat you are actually facing.

NSA And CISA Hand Buyers A Vendor Checklist. NSA, CISA and Australia's ACSC have published a set of practical questions for judging a supplier's post-quantum readiness, released on November 4. The guidance is built for acquisitions, contract renewals and ongoing supplier reviews. Reporting on it describes 31 questions in five phases, from locating where cryptography is used to educating stakeholders. Early questions ask whether a vendor keeps a cryptographic bill of materials, whether cryptography is hardcoded or tied to hardware, and whether firmware can accept post-quantum signatures without replacing the device. The message is plain. Your post-quantum readiness depends on your vendors' readiness, transparency and roadmaps. For anyone building financial rails, that is a hard dependency to carry. QuanChain's upgrade path lives in the protocol: stronger security levels are derived at the next spend, and value at rest sits behind an address hash. The checklist is for buyers. The better design reduces how many answers you need.

WASM, Not EVM. Here Is Why. QuanChain's contracts run on WebAssembly, not the EVM, and the whitepaper gives the reasons. WASM bytecode is platform independent and well standardized. Rust's type system and ownership model prevent entire classes of bugs, while Solidity has well-documented issues like reentrancy and integer overflow. Quantum cryptography through EVM precompiles is architecturally awkward, whereas in WASM it is a set of native host functions. And WASM integrates naturally with all three channels. Industry adoption points the same way: Polkadot, NEAR and Cosmos also use WASM. Solidity support through the Solang compiler is deferred, not ruled out. A runtime picked to fit the security model, not copied from habit.

Two Threats. Often Confused. Two different quantum threats get mixed together. QuanChain's design answers each one separately. Threat A is exposure. On most chains the public key that protects value is published on-chain at or before the first spend. A cryptographically relevant quantum computer running Shor's algorithm can derive the private key from it, and harvest now, decrypt later means adversaries are already archiving the data. Threat B is the treadmill. Quantum hardware will keep improving, so every chain will keep having to upgrade. Each migration leaves stranded wallets whose keys stay on-chain, and a share of users always miss the window. The answers are different too. SpendAndRotate keeps live public keys off the protected surface. The oracle chooses when each wallet upgrades, as part of its next spend. Fix only one and the other stays open.

Channels Anchor To Each Other. QuanChain's three channels are anchored to each other in a hierarchy. Channel 1 is the root. The other channels are anchored upward to their parent at regular block intervals. Each anchor carries the Merkle root of the child channel's blocks since the last anchor, the child's current block height, validator signatures attesting to it, and the current quantum threat level. The result is that an adversary cannot manipulate Channel 2 or Channel 3 state without also controlling Channel 1 consensus. Three channels for three jobs, one security model underneath them.

UK Regulator: Have A Quantum Plan By 2028. The UK's financial regulator has put dates on quantum readiness. In a November 4 blog post, Mark Francis, the FCA's Director of Specialists, pointed firms to the NCSC's milestones: a migration plan by 2028, high-priority migration work by 2031, and migration across all systems, services and products by 2035. He added that firms should not wait for those dates and should be ready sooner where it is safe to be. The ask is practical. Firms need to map where they use cryptography, including what is held by suppliers, and senior managers are expected to commit the time, investment and resources to meet the deadlines. The FCA is trialling a self-assessment tool with an initial group of firms and plans to consult on cyber-resilience guidance that includes post-quantum controls. This lands the same week as the NSA and CISA's vendor questions. Regulators on both sides of the Atlantic are asking the same thing: do you know what you run, and do you have a plan? QuanChain's design takes the plan into the protocol. Wallets upgrade at their next spend as the oracle's reading moves, and value at rest sits behind an address hash. The dates are set. The question is who is ready.

Security Measured In Dollars. Most chains describe security in bits. QuanChain describes it in dollars. The cracking-cost model prices an attack on each security level by the cheapest path available to an attacker. Grover's search looks for an input that hashes to your address. For a 256-bit hash that is about 2^128 quantum operations. The birthday attack, a collision search, is cheaper at about 2^85 operations, though the whitepaper notes it still far exceeds any wallet balance. Shor's attack on the key only applies if a public key is exposed, which child rotation is designed to prevent. The effective cost is the minimum of the paths that apply, priced at about 5 million dollars per logical qubit-hour. Bit-strength tells you how hard something is. Dollars tell you whether anyone will do it.

What An Anchor Actually Contains. What actually goes into a CCRP anchor? Each anchor is a snapshot of QuanChain's state: block height, block hash and state root. It records the current LQCp/h reading and the number of migrations since the last anchor, plus a Merkle root of those migrations. A timestamp, the count of attesting validators and two aggregate signatures complete it. Serialized, it is about 188 bytes or more. That small package is posted to four other chains. Because it includes the quantum threat reading and the migration count, it creates a tamper-evident record of QuanChain's quantum security posture on blockchains it does not control. A short record, written on chains QuanChain does not control.

Six Layers. One Chain. QuanChain is built in layers, each with one job. At the top is the interface: a JSON-RPC and WebSocket API, and three channels for transactions, smart contracts and data. Beneath them sits Proof of Coherence consensus, which weighs stake and performance equally and adds a bonus for validators running higher security levels. Below that are the engines: the TADEQS security framework with its twenty levels, the quantum threat oracle, and CCRP anchoring to four other chains. At the foundation are four network layers, libp2p, Turbine, a DAG mempool and a fast path, over RocksDB storage and a Blake3 content store. Quantum security is not a patch on top. It is one of the layers the rest is built around.

The Security Level Is In The Path. On QuanChain the security level is part of the wallet's derivation path. Wallets follow an extension of BIP-44: m / 4400' / 8421' / account' / security_level' / index. The level is one of the components, and it sets the default level for the wallet's children. That path produces the seed material, which is expanded to 64 KB for the parent's entropy pool. Child keys are then derived with HKDF-SHA256, with the path, the security level and the purpose included in its info field. The result is that keys for different security levels are cryptographically independent, even when they come from the same seed. One seed. Independent keys at every level.

It Started With A Fake Job Interview. Binance has published its incident report on the $6.3 billion theft, and it began with a fake job interview. In September, a software engineer was approached on a legitimate job-hunting platform by someone posing as a project director at a fictitious company. A fake HR representative then held a live video call, and a second interview ended with a coding assignment. Running that code installed custom malware that Binance says its endpoint security tools did not detect. By October 20, the attackers had used that machine and an internal AI tool to compromise two more employees working on the wallet infrastructure, obtaining credentials and a container deployment token. On October 29 they used those credentials to deploy a malicious script and reach the wallet signing service. As of November 3, about $2.85 billion of the stolen assets had been frozen or intercepted. The FBI has attributed the theft to North Korea's TraderTraitor group. Notice what was attacked. Not an algorithm. A person, then a laptop, then a token. Quantum resistance does not fix that, and nobody should claim it does. It protects a different layer: the keys and signatures themselves, against a computer that does not exist yet. Both layers need to hold.

Seventeen Transaction Types. Three Channels. QuanChain defines seventeen transaction types, spread across its three channels. ⚛️Channel 1 carries thirteen. Wallets: Transfer, WalletRegistration, SpendAndRotate (the default for every wallet send), ReturnToParent for consolidation, RecoveryTransaction for emergency recovery with the parent key, and Migration, which is now superseded by SpendAndRotate with a level change. The network: Stake, Unstake, Delegate, Undelegate, GovernanceVote, GovernanceProposal, and AnchorSubmit for validators only. ⚛️Channel 2 carries ContractDeploy and ContractCall. ⚛️Channel 3 carries DataStore and DataPin. Pinning prevents garbage collection. Unstaking and undelegating start a 14 day unbonding period. Seventeen is a long list. The default is one.

Every Block Records The Quantum Threat. Every QuanChain block header carries the same fields on all three channels. ⚛️ Link. A Blake3 parent hash chains each block to the last. ⚛️ Prove. A Merkle root of the transactions, and a state root. ⚛️ Sign. The validator's security level, and a signature sized to that level. ⚛️ Record. The oracle's current quantum threat level. Each channel adds its own extensions to the common header. The threat level is not something you look up elsewhere. It is written into the permanent record of every block.

Foxconn Wants To Build The Quantum Computers. Foxconn's chairman, Young Liu, told CNBC the company wants to become the world's largest quantum computer manufacturer, without owning the underlying technology. The plan is to build machines for the companies that develop it. Liu said they are at least two years from being commercially viable, and that quantum computers would not replace CPUs and GPUs but would sit alongside them in hybrid workflows. Component costs are substantial even before a complete machine is assembled. My read, not Foxconn's: when the world's largest contract manufacturer starts planning for quantum production, the hardware race is moving from labs toward manufacturing. Nobody knows how fast that changes the cost of an attack. That is why QuanChain's oracle tracks the cost per logical qubit-hour, and why wallets upgrade at their next spend as it moves. The cost of a quantum computer is not a constant. The security design should not assume it is.

Seventeen Transaction Types. Three Channels. QuanChain defines seventeen transaction types, spread across its three channels. ⚛️ Channel 1 carries thirteen. Wallets: Transfer, WalletRegistration, SpendAndRotate (the default for every wallet send), ReturnToParent for consolidation, RecoveryTransaction for emergency recovery with the parent key, and Migration, which is now superseded by SpendAndRotate with a level change. The network: Stake, Unstake, Delegate, Undelegate, GovernanceVote, GovernanceProposal, and AnchorSubmit for validators only. ⚛️ Channel 2 carries ContractDeploy and ContractCall. ⚛️ Channel 3 carries DataStore and DataPin. Pinning prevents garbage collection. Unstaking and undelegating start a 14 day unbonding period. 17 is a long list. The default is one.

Every Transaction Passes These Checks. Every QuanChain transaction carries a security_level field, and every validator enforces the same checks. Signature. It must match the declared security level and the expected size for that level. Both parts of a hybrid or composite signature must verify independently. Level. It must be between 1 and 20. Reserved levels 16 to 19 are rejected until governance activates them. Level 20 is accepted only for wallet registration and recovery. Rotation. A SpendAndRotate must include a valid Merkle derivation proof for the new child, and a forwarding rule that points from the current active child to the new one. Migration to a higher level is handled through the same SpendAndRotate path, with no special migration transaction needed for routine upgrades. The rules are short. That is the point.