# The Problem

Besides Telegram and traditional media, X/Twitter remains the most popular news outlet for Cryptocurrencies to gather insights and data into new and existing projects. Investors, especially in DeFi, often rely on 'Key Opinion Leaders' in the space for information and suggestions around what to buy. However, there are many self pronounced 'influencers' on Twitter, and it can be very hard for investors to make a distinction between good and bad projects, especially as KOLs could have bad intentions.

To the delight of many investors and developers, 2024 has seen a significant uptick in Cryptocurrency prices and volumes after a 2-year slump following the Luna and FTX debacles. While good news for the overall market, more money in rotation also means more bad actors. As such, many 'influencers' have risen who aim to take advantage of the new momentum in Crypto and who launched and improperly advertized new cryptocurrencies.

As such, there is a clear 'Information Overload' problem in Crypto. Investors scrolling on X see tens of projects being 'shilled' every day, and need to make wise and informed decisions on what to invest in, as each and every project is advertized as 'The Next Pepe'. This problem has caused the rise of Crypto analytics tools, such as contract scanners. However, most of these utilities are primarily based on price and tokenomics data, and we believe there is a gap with limited competition in tools to assess market trends and provide token insights. Social 'data' and trends can give important insights into the potential of tokens and their community.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://social-edge.gitbook.io/social-edge-or-product-docs/introduction/the-problem.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
