01
Final Code
Our patented execution and result-finalization architecture. It runs approved programs and produces authoritative execution receipts.
Public research update · July 2026
Execute. Govern. Finalize. Preserve.
ZWEICHAIN-Q is a post-quantum-ready finality and evidence layer connecting our patented Final Code architecture, Goodhills Quantum OS, NAMAZU/TGL, and a bounded EVM compatibility lane.
One ecosystem, five distinct roles
Useful autonomous systems need more than computation. They need identity, bounded authority, recoverability, finality, and durable evidence.
02
Goodhills Quantum OS
The resilience and control plane for cryptographic agility, policy, key rotation, recovery, software provenance, and emergency response.
03
ZWEICHAIN-Q
A post-quantum-ready finality and evidence layer using PQ authorization, validator quorums, append-only records, and signed checkpoints.
04
NAMAZU / TGL
Real-world data, risk, property, and digital-twin-oriented signals for traceable calculations, observations, and attestations.
05
Optional EVM lane
A compatibility path for Solidity, ABI tooling, logs, escrow, and Ethereum interoperability where those capabilities add concrete value.
How the layers work together
1. ProposeA human or autonomous function proposes an operation.
2. GovernGHQOS applies identity, capability, key, policy, and recovery rules.
3. ExecuteFinal Code or another approved executor performs the authorized program.
4. ObserveNAMAZU/TGL supplies traceable real-world data and risk signals where required.
5. PreserveZWEICHAIN-Q records authorization, result, finality, and evidence.
What we verified locally
The July 2026 research sequence progressed from real PQ signatures to a four-validator network, then to real EVM execution and a cold-versus-warm benchmark.
v0.1
Real post-quantum protocol mechanics
ML-DSA-65, ML-DSA-87, SLH-DSA, key epochs, tamper rejection, and dual-signed checkpoints.
v0.2
Four-validator networked development chain
Four independent JVM validators, real localhost transport, 3-of-4 finality, safe halt below quorum, persistence, and restart.
v0.3A
Post-quantum EVM reality check
Real Solidity execution, deterministic ZQ-to-EVM account mapping, effective EVM msg.sender, matching roots, and no Ethereum ECDSA private key in the tested ZQ authority path.
v0.3A.1
Cold versus persistent-warm EVM benchmark
9,530 raw rows, 8,680 recorded samples, 850 warmups, complete v0.3A acceptance, and full v0.2 regression.
Headline local measurements
Means measured on one Windows development machine. These are not Ethereum-mainnet throughput results.
| Measured path | Mean |
|---|---|
| Native ZQ transition core | 0.001895 ms |
| Native ZQ receipt path | 0.099978 ms |
| ML-DSA-65 verification | 0.761787 ms |
| Cold external EVM event increment | 2163.103 ms |
| Warm persistent EVM execution | 12.204 ms |
| Warm EVM end-to-end wrapper path | 22.056 ms |
Scientific correction: the first multi-second EVM result was dominated by cold process startup and initialization. Keeping the EVM implementation warm reduced the measured mean by roughly two orders of magnitude.
Final outcome B
Keep EVM as a bounded, optional compatibility lane.
Native ZQ remains the primary route for structured evidence, identity, key rotation, Final Code receipts, and NAMAZU/TGL records. EVM remains available when Solidity, Ethereum tooling, programmable contracts, escrow, or interoperability provide real value.
Execute through Final Code. Govern identity, policy, keys, and recovery through GHQOS. Use NAMAZU/TGL for real-world signals. Preserve authorization, result, and finality through ZWEICHAIN-Q.
Scope and claim discipline
What this work demonstrates
Real PQ signatures, PQ-authorized EVM execution, validator agreement, key rotation, deterministic roots, restart behavior, and a measured cold-versus-warm execution boundary.
What it does not claim
It is not production-audited consensus, a production wallet, Ethereum-mainnet throughput, proof that Ethereum is post-quantum secure, or proof that ZWEICHAIN-Q is “quantum-proof.”
Primary technical references
Public research update · 2026年7月
実行し、統治し、確定し、証拠を残す。
ZWEICHAIN-Qは、特許化されたFinal Code、Goodhills Quantum OS、NAMAZU/TGL、そして限定的なEVM互換レーンを接続する、耐量子readyなfinality / evidence layerです。
一つのecosystem、五つの役割
有用なautonomous systemには、計算だけでなく、identity、bounded authority、recovery、finality、durable evidenceが必要です。
01
Final Code
認可されたprogramを実行し、authoritativeな結果とexecution receiptを生成する、私たちの特許化されたarchitectureです。
02
Goodhills Quantum OS
cryptographic agility、policy、key rotation、recovery、software provenance、emergency responseのcontrol planeです。
03
ZWEICHAIN-Q
PQ authorization、validator quorum、append-only record、signed checkpointを用いる、耐量子readyなfinality / evidence layerです。
04
NAMAZU / TGL
real-world data、risk、property、digital twin oriented signalを、traceableなcalculation / attestationとして提供します。
05
Optional EVM lane
Solidity、ABI tooling、log、escrow、Ethereum interoperabilityに具体的価値がある場合のcompatibility pathです。
各layerの接続
1. Proposehumanまたはautonomous functionがoperationを提案します。
2. GovernGHQOSがidentity、capability、key、policy、recovery ruleを適用します。
3. ExecuteFinal Code等のapproved executorが認可されたprogramを実行します。
4. ObserveNAMAZU/TGLが必要なreal-world data / risk signalを提供します。
5. PreserveZWEICHAIN-Qがauthorization、result、finality、evidenceを記録します。
ローカルで検証したこと
2026年7月のresearch sequenceでは、real PQ signatureからfour-validator network、real EVM execution、cold / warm benchmarkまで進みました。
v0.1
Real post-quantum protocol mechanics
ML-DSA-65、ML-DSA-87、SLH-DSA、key epoch、tamper rejection、dual-signed checkpoint。
v0.2
Four-validator networked development chain
4つの独立JVM validator、real localhost transport、3-of-4 finality、quorum不足時のsafe halt、persistence / restart。
v0.3A
Post-quantum EVM reality check
real Solidity execution、deterministic ZQ-to-EVM mapping、effective msg.sender、matching roots、tested ZQ authority pathにEthereum ECDSA秘密鍵を置かない構成。
v0.3A.1
Cold vs persistent-warm EVM benchmark
raw 9,530 rows、recorded 8,680 samples、warmup 850 samples、v0.3A acceptanceおよびv0.2 regressionはPASS。
ローカル測定の平均値
一台のWindows開発機での測定です。Ethereum mainnet throughputを示すものではありません。
| Measured path | Mean |
|---|---|
| Native ZQ transition core | 0.001895 ms |
| Native ZQ receipt path | 0.099978 ms |
| ML-DSA-65 verification | 0.761787 ms |
| Cold external EVM event increment | 2163.103 ms |
| Warm persistent EVM execution | 12.204 ms |
| Warm EVM end-to-end wrapper path | 22.056 ms |
Scientific correction： 最初の複数秒のEVM結果は、cold process startupとinitializationが支配していました。EVMを常駐させることで、測定平均は約2桁改善しました。
Final outcome B
EVMは限定されたoptional compatibility laneとして保持する。
structured evidence、identity、key rotation、Final Code receipt、NAMAZU/TGL recordにはnative ZQを主経路とします。Solidity、Ethereum tooling、programmable contract、escrow、interoperabilityに具体的価値がある場合にEVMを利用します。
Final Codeで実行し、GHQOSでidentity・policy・key・recoveryを統治し、NAMAZU/TGLでreal-world signalを提供し、ZWEICHAIN-Qでauthorization・result・finalityを保存する。
範囲とclaim discipline
このworkが示すこと
real PQ signature、PQ-authorized EVM execution、validator agreement、key rotation、deterministic root、restart behavior、cold / warm execution boundaryです。
このworkが主張しないこと
production-audited consensus、production wallet、Ethereum mainnet throughput、Ethereumがpost-quantum secureである証明、ZWEICHAIN-Qが“quantum-proof”である証明ではありません。