Funding and connections
The cheapest true coordination signal available, and the one most often misread — including by us, twice.
First funding
Every wallet was funded by something. The page walks back to the first inbound SOL and names the source where it can.
First funding never changes, so it is cached permanently once resolved.
Siblings
Other wallets funded by the same source. If one intermediary wallet funded eight addresses that all bought the same launch, those eight are one participant wearing eight hats — which changes what "eight buyers" meant.
Why an exchange funder is not a link
Here is the trap. If the funding source is a recognised exchange, the other wallets it funded are strangers. Binance funds millions of addresses. Bybit funds millions. Sharing one tells you nothing at all.
So an exchange source is stored and displayed, and it is never treated as a connection. Where the source is an exchange, no sibling list is shown — because listing eleven unrelated strangers under a heading that implies a crew is worse than showing nothing.
The same rule applies to the walked-back origin, not just the direct funder: the walk deliberately stops at an exchange, so an exchange can appear as an origin too.
Fresh intermediaries
The interesting case is a crew that uses a new intermediary wallet every time and draws from the same account behind it. Direct-funder siblings would find nothing; walking back one more hop finds the pattern.
That is what the origin walk is for, and it is why "came out of the same account" is shown separately from "funded by the same wallet".
Connections between two wallets
A direct check between any two addresses, graded by evidence strength:
- Direct transfer — one sent to the other. Strongest.
- Shared funder or origin — both came from the same place, discounted heavily if that place is an exchange.
- Co-buying — they appear in the same launches, repeatedly.
- Token overlap — they hold the same things, with no timing evidence. Weakest, and on its own close to meaningless.
A partial result is never cached. If the lookup failed halfway, the answer would be "no links found", which is indistinguishable from a real negative and would poison the pair with a false all-clear until the cache expired.