break the key. keep the ETH.

The qHOST quantum bounty. A wallet nobody has the key to. Its public key is published. Whoever derives the private key takes everything in it.

in the pot right now
– ETH
● unclaimed · read from chain
0x4811a2cBbf6EF7bC42A9B7BCd6Ee7dd4887f0715

ETH sent here cannot be taken back, by you or by us.

The pot

ETH sitting at one address, on Ethereum and on Robinhood Chain. Its public key is published below. Its private key does not exist anywhere: nobody ever generated one.

How to win

Derive the private key from the public key and send the ETH wherever you want. No form, no permission, no claim process. If you can sign, it is yours.

Why nobody has the key

The public key was not made from a private key. Its x coordinate is the hash of a sentence. Finding the key behind it is the exact problem a quantum computer is supposed to solve.

Add to it

Anyone can send ETH to the address. It only ever goes in. The day it comes out, every elliptic-curve wallet has a problem.

verify it yourself.

Hash the sentence with the counter using keccak-256 and read the result as an x coordinate on secp256k1. Take the point with even y. Hash that public key and keep the last 20 bytes: you get the address above. Nothing else went in.

sentence "qHOST quantum bounty. nobody has this key. 3"
public key 0x04423d552a9f0f637528261a2d8f528e0c88af6665d534a2d1737d81f6395b1e884402e16eebff7355189cc43181331df3ca529b731c242ee29660f98ea7ededb6
address 0x4811a2cBbf6EF7bC42A9B7BCd6Ee7dd4887f0715

The bounty wallet is separate from the canary the bunker contract watches. A move would be a serious signal about elliptic-curve keys, not proof of who built what. Read the limits →

Arm your auto-bunker →Scan your wallet ⌕