Baskets
Who the fee was pointed at.
Every row was read out of the bytes of a launch transaction, not off a website. The UpdateFeeSharesV2 payload is a list whose entries are a 32-byte address followed by a u16 of basis points. That is the whole of what a launchpad in this category installs.
4 launches decoded
1 distinct recipient
And 3 that carried no fee share at all
These are kept on the page rather than dropped from it. Quietly filtering them would turn “every launch we decoded routes to one wallet” into a sentence about a list we had already tidied — which is the shape of most statistics that turn out to be wrong.
What this list is not
A census. It is what has actually been decoded, by hand, and it will stay short because reading a launch means walking a mint’s signatures back to its birth — which for a coin with forty thousand transactions is not something a page load can promise.
Decode one yourself: pull the birth transaction, find the instruction whose first eight bytes are 6ffb31064e4e6a12, skip the four-byte vector length, and read 32 bytes of address followed by two bytes of basis points, little-endian.