# The Problem

<figure><img src="/files/RiDA66yrXojWlPsXTvaS" alt=""><figcaption></figcaption></figure>

Blockchain and artificial intelligence (AI) are two transformative technologies that are increasingly converging in innovative ways. However, decentralized **AI systems face critical challenges in interoperability, incentive alignment, and scalability - issues** that are often overlooked in speculative AI-token projects \[1].&#x20;

* Up to **85% of AI projects fail** due to weak use cases, poor integration, or unsustainable business models \[2].
* Over **60% of AI-related crypto tokens** exhibit pump-and-dump behavior within 30 days of launch \[3].
* User retention across Web3 applications remains critically low, often **below 12%** after 30 days \[4].

These conditions have led to:

* Loss of user trust
* Drainage of ecosystem liquidity
* Minimal real-world adoption
* Poor user retention (<12%) \[4].

**The result?**&#x20;

A bloated, noisy landscape where the few truly valuable AI x Web3 projects struggle to stand out - choking innovation and investor confidence.

We call this the **99% Useless AI Crisis -** and it’s what Xeleb aim to solve.

Let's explore what we're cooking...!

***

**References**

\[1] Vid Kersic, Muhamed Turkanovic: *"A Review on Building Blocks of Decentralized Artificial Intelligence"*, ICT Express, 2025 (Elsevier)&#x20;

\[2] Gartner: *"Why 85% of AI Projects Fail and What to Do About It"*, Gartner Research, 2023&#x20;

\[3] Chainalysis: *"Crypto Crime Report 2025"*, Chainalysis Research, 2025

\[4] Dune Analytics: *"Web3 User Retention Dashboard"*, hildobby, 2024


---

# 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://xeleb.gitbook.io/xeleb-protocol/about-xeleb-protocol/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.