Lode Research
Data point guide · Team & development Pro
Built before launch
How long the team's GitHub existed before the token launched.
Higher
The team was building long before it sold a token.
Lower
The code appeared with (or after) the token: possibly built around the sale.
The trade-off
Years of prior work suggest a product; none suggests a token looking for one.
Good to know
Only for tokens with a public GitHub. Launch date can be the first-listing date, which overstates it.
Known for41% of tokens today
SourceGitHub
Updatedonce per token
PlanPro
How to use it in Lode Crypto Score
Like every data point, Built before launch has three switches. Show it as a column. Filter on it: set a range, and choose whether tokens with no data stay in. Or let it Score: pick the direction and how much it counts next to everything else. A missing value is never counted as a bad one unless you say so.
Try it on today's data.Build your own ranking of about 2,000 tokens in a few minutes. No picks, no signals: your criteria.
Create a free account More in Team & development
- Public team Whether the project's website names the people behind it: at least two personal LinkedIn profiles, or a team section with named people or their personal X accounts that we checked by hand. Code on GitHub doesn't count here (see the development data points). Names are in the token's detail panel.
- Active developers Different people who committed code in the last 180 days.
- Commits (180d) Code changes pushed in the last 180 days.
- Development trend Commits in the last 180 days divided by the 180 days before.
- Website status Whether the project's website responds.
- Token age Days since the token launched (or first listed, if the launch date is unknown).
A screening tool, not investment advice. Scores measure how well a token fits the criteria you choose; they are not forecasts.