Data point guide · Team & development Pro

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.

The trade-off

A public team is accountable. Anonymous projects can still work, but are harder to judge.

Good to know

Unknown when the website couldn't be read or the team is still being checked; that is not the same as 'no'.

How to use it in Lode Crypto Score

Like every data point, Public team 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.

More in Team & development

• Built before launch How long the team's GitHub existed before the token launched.
• 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.