quantic os / home reading

the cryptographic transition layer for Ethereum

Every Ethereum account is one key. Quantic OS puts a second one in front of it.

An account's public key is on chain from its first transaction. A large enough quantum computer turns that public key into the private one. Quantic OS shows you what is exposed, makes you a key built only from hashes, and from then on your QOS moves with that key alone.

system · read from Ethereum

Reading the chain...

why it holds

What a quantum computer can and cannot do here

It can read a wallet's key

Shor's algorithm finds a private key from its public key. Every account that has sent a transaction has shown its public key. Its ordinary signature stops meaning anything.

It cannot read a hash

A policy key is a tree of Winternitz one-time keys made of keccak hashes. Undoing a hash stays a search of about 2128 steps even for a quantum computer. No curve, no logarithm.

It can be caught

The canary is an Ethereum address nobody holds the key to. Whoever signs for it has proven the machine exists: they take the jar, and the day is on chain.

limits, stated

  • A policy protects QOS, and only once it is set. Set it before the day: after the canary sings, an ordinary signature cannot prove who you are.
  • Lose the key and the QOS under it cannot move, ever. Keep it like a seed phrase.
  • QOS under a policy cannot be sold through a router until you move it to a wallet.
  • The pool's only depth is the owner's band, and the owner may remove it.

who earns

Every trade in the ETH and QOS pool pays 1% of its ETH side to the owner, who also holds the pool's one band. The pool's LP fee is 0%. Policies, moves and the canary take no fee.

The pool opens once, at a 1 ETH valuation, with the whole billion QOS in that band. The token has no tax and no owner.