# The Live Market

### The missing primitive in Web3 trading

DeFi solved custody. It did not solve coordination.

Every market move begins as a realtime coordination problem: information appears, interpretation spreads, positioning forms, and the chart catches up. Yet most trading products treat the chart as the beginning of the story, and streaming as marketing that happens elsewhere.

That separation causes three structural failures:

* Speed failure: Alpha decays during context switching.
* Truth failure: Screenshots substitute for verification; performance becomes narrative.
* Incentive failure: The people who create actionable context (streamers, builders) monetize indirectly, outside the execution layer that captures the value.

### Pumpkin’s answer: trading as a shared timeline

Pumpkin makes the trading experience a single timeline where:

* markets route users to the rooms where the market is being explained,
* rooms route users back to execution with one-tap follow,
* execution produces verifiable events (proof-backed for perps, receipt-backed for spot),
* and the entire session becomes replayable history.

This is not “social trading.” It is market infrastructure: a Live Market Layer that binds attention to action and action to proof.

{% @mermaid/diagram content="flowchart LR
A\[Realtime context in rooms] --> B\[Instant execution in the same surface]
B --> C\[Verification: proofs + receipts]
C --> D\[Reputation and discoverability]
D --> E\[More attention concentrates where truth is]
E --> A
" %}


---

# 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://docs.pumpkin.xyz/getting-started/the-live-market.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.