Build the Quantum Canary hook: a Uniswap v4 hook whose only purpose is to feed, forever and without any owner, the ETH bounty of the Quantum Canary, an immutable contract already live on Ethereum mainnet at 0x626517225096671868609c1bbf9c1b416a4efd9a. That contract exposes canaryAddress() (the address whose secp256k1 private key nobody knows; ETH sent there can only ever be moved by a quantum computer) and isTripped() (true once that balance has dropped below its threshold).

Token: the standard launch token, name "Quantum Canary", symbol "CANARY", 1,000,000,000 fixed supply, plain transfers. Pool paired with native ETH.

Hook, named QuantumCanaryHook:

1. afterSwap only (plus the permission flags it needs for return deltas). On every swap it takes a flat 1% fee on the ETH side of the trade: on a buy (ETH in) 1% of the ETH paid, on a sell (ETH out) 1% of the ETH received. The fee is taken from the PoolManager as native ETH and sent in the same transaction straight to the canary address read from the Quantum Canary contract. The hook never holds ETH or tokens between transactions and has no withdraw function.
2. Constructor arguments: the PoolManager and the Quantum Canary contract address (static addresses). It stores both as immutables and reads canaryAddress() once in the constructor into an immutable.
3. No owner, no admin, no fee setter, no pause, no upgrade, no selfdestruct, no delegatecall. The fee percentage is a constant.
4. Retirement: when isTripped() on the Quantum Canary returns true, the hook stops taking any fee and swaps proceed untouched for ever after; the canary has done its job. Read isTripped() in afterSwap with a staticcall guarded so that a revert of the canary never blocks swaps (treat a revert as not tripped).
5. Callbacks refuse any caller other than the PoolManager; permissions match the declared flags; the hook must work with the launch pool's fee tier and tick spacing chosen by the policy.
6. Tests: fee goes to the canary address on buys and sells, exact amounts; nothing is retained by the hook; no fee after a simulated trip (mock canary contract); callbacks reject non-PoolManager callers; fuzz swap sizes.
7. README: explain in plain language that 100% of the hook fee goes to the Quantum Canary bounty, that no human can redirect or withdraw it, that the requester keeps 0% of the supply, and how anyone can verify the flow on chain.