# The result

### The chaos finally spiraled out of control, forcing Pump.fun to pull the plug on its infamous livestream feature.

<figure><img src="https://pbs.twimg.com/media/GderI8OaUAAmJNe?format=png&#x26;name=900x900" alt=""><figcaption></figcaption></figure>

The unchecked chaos led to Pump.fun sentiment plummeting to an **all-time low**, with many crypto influencers openly calling for a boycott of the platform.&#x20;

{% embed url="<https://x.com/_kaitoai/status/1860969504798302691>" %}

Even Polymarket got in on the action, with predictive markets giving Pump.fun a **staggering 97%** chance of being banned in the U.S. by year’s end.

<figure><img src="/files/X3lTlTI63QcjvZXlgAjA" alt="" width="375"><figcaption></figcaption></figure>

And as the backlash brewed, the platform’s weekly revenue nosedived **by 66%**, proving that even degens have their limits.

<figure><img src="/files/XEx7oXsGnF84zO6U8WZL" alt="" width="563"><figcaption></figcaption></figure>

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


---

# 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://karma-fun.gitbook.io/karma.fun-docs/why-does-karma.fun-matter/the-result.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.