Find the sources.
Start with a contract address. Resolve the token, identify its launchpad, and discover linked websites, docs and accessible X posts.
TOKEN ECONOMICS · SOLANA
Follow
the fees.
Every token has a story about where the money goes. Put the promises, recipients and evidence on one map.
EXAMPLE MAP / 3DDrag to explore
Project allocation
Creator fees
One fee pool. Multiple possible destinations.
EXAMPLE ECONOMY
An economy, connected.
Select a node. Follow a path. See what backs it up.
Dashed paths show declared uses.
01 / THE PRODUCT
From an address to answers.
Sources. Claims. Transaction evidence.
Map the claims.
Extract fee splits and intended uses. Keep the exact quote and source beside each path. Missing details stay unknown.
Follow the evidence.
Compare declared uses with decoded transactions. Inspect recipients and receipts without confusing a promise with a payment.
02 / THE EVIDENCE
Every connection needs context.
Declared
What the project says. A source, a quote and a date.
Observed
What the chain shows. A transaction, an amount and a time window.
Unknown
What we cannot establish. Kept visible, never filled in with a guess.
Questions, answered.
What does a map show?
Fee pools, recipients and stated uses, with context for each connection. Explore the example map above to see how the paths fit together.
Will a website or X post count as proof?
It can support a declared claim, not prove that funds were spent. Observed transfers need transaction receipts, and some intended uses cannot be verified from transfers alone.
What if a fee split is missing?
It stays unknown. Flumen should preserve missing sources, conflicting claims and unresolved recipients rather than invent a complete map.
How will maps become live?
The first scanner will resolve sources and build declared maps. A launchpad-specific adapter will then add transaction evidence. Refresh times and coverage will be shown explicitly.
LESS GUESSWORK. MORE CONTEXT.