On February 14, 2025, Ethos announced that it was bringing Ethos scores to the Kaito dashboard through its Chrome app. With the update, people using @_kaitoai could see not only who had mindshare, but who was most reputable, directly in Kaito.
For anyone trying to judge whose voice carries weight in crypto, that put two different signals on one screen instead of two.
Influence = attention + reputation
Ethos summed up its thinking in a simple formula: influence = attention + reputation.
Attention is what Kaito’s dashboard tracks as mindshare: who people are talking about and paying attention to. Reputation is what Ethos measures.
Each signal on its own tells only part of the story. An account can draw plenty of attention without being trusted, and a highly reputable account may not be the loudest one in the room. Ethos said it wanted to make it easier for its users to see this data side by side.
What changed in the Chrome extension
To make the integration work, Ethos updated its Chrome extension. The update requested a new permission to write to yaps.kaito.ai, which is where the Ethos scores appeared alongside Kaito’s data.
Ethos said the update would be pushed to users automatically on the morning of February 14, 2025, so existing users of the extension did not need to reinstall anything. They would see the new permission request as part of that update.
What it meant for users
With the updated extension, a Kaito user could look at the accounts with the most mindshare and, in the same view, see how reputable those accounts were according to Ethos. Rather than switching between tools to check whether a widely discussed account had a strong reputation, the two pieces of information sat together on the Kaito dashboard.
- From Kaito: who has mindshare
- From Ethos: who is most reputable
- Where: directly in the Kaito dashboard, through the Ethos Chrome app
It was a practical application of the formula Ethos opened with: attention and reputation, shown together, give a fuller picture of influence than either one alone.
This thread first appeared on X.
