# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
This site has an agentic ask interface you may use to query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pumpkin.xyz/index.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

---

# Pumpkin Document

### Disclaimer

This document is provided for informational purposes only and does not constitute investment, legal, tax, or financial advice. Pumpkin may restrict access based on jurisdiction and eligibility. Features described herein may evolve, be delayed, or be discontinued.

### Abstract

Pumpkin is a decentralized trading network whose core business is live trading: a single product surface where realtime streaming and realtime execution converge into a verifiable, replayable market experience.

Pumpkin combines:

* Multi-chain spot aggregation across Solana, Base, BSC, and the broader EVM ecosystem.
* A self-built ZK perpetuals engine, where exchange state transitions are accepted only with valid proofs.
* A trading-grade media stack: audio, video, screen sharing, OBS ingest, multi-host sessions, gifts, and recordings.
* An ecosystem economy anchored by Pumpkin Seeds, supported by explicit fee-routing primitives: Builder Code (extra user-paid) and rebates (distributed from trading fees, including permissioned multi-level structures).

Pumpkin’s thesis is simple: markets are a conversation before they are a chart. Most platforms split this conversation (rooms, chats, influencers) from execution (terminals, orderbooks). That split destroys speed, truth, and incentives. Pumpkin removes it by creating the Live Market Layer: a network where context, action, verification, and replay share the same timeline.


# 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
" %}


# The Pumpkin Story

### Discovery begins with markets—and with people

A user opens Pumpkin and selects a market. The market page looks like a professional terminal: chart, depth, funding, positions. But it also answers a question most terminals ignore:

**Who is explaining this market right now?**

Each market page surfaces live rooms actively discussing the instrument. This isn’t a recommendation widget; it is a structural bridge between information and action.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FDtoxWa9YPhF2L6dCjXw3%2Fscreenshot-20260118-015226.png?alt=media&amp;token=b5f1eb7f-ed23-4c7f-9cd5-934c118d10c9" alt=""><figcaption></figcaption></figure>

### A room is not a video—it is an execution surface

The user enters a room. The room is a trading environment:

* The room cover displays verifiable performance signals.
* The host and guests can disclose realtime positions (with safety controls).
* Host trades appear in the room instantly as events in chat and bullet comments.
* The user can follow a trade in one tap, without leaving the room.

### Strategy is published as an object, not a suggestion

The host publishes a strategy card during the stream. The card is structured:

* instrument, direction, entry type
* optional risk template (position sizing constraints)
* and an explanation tied to the live context

### Execution becomes truth in realtime

If the trade is spot, the UI is backed by onchain receipts.\
If the trade is perps, the UI is backed by the ZK perps event pipeline.

The result appears in the room as a verified event. This is the crux of the Live Market Layer: the stream becomes a truthful market record, not a performance show.

### The session becomes a replayable artifact

When the stream ends, it doesn’t vanish. Pumpkin records it and indexes it with markers so users can jump to specific moments: entry, scaling, stop moves, exits, or funding events.

### Contribution becomes a weekly economy

Each week, contribution is measured and rewarded through Pumpkin Seeds. This closes the loop: a user’s trading, a creator’s content, and a builder’s tools all connect into the same incentive substrate.


# Architecture

Pumpkin is designed so that trading events and media events are first-class citizens of the same timeline. The system is organized into three layers, but the product behaves like a single surface.

{% @mermaid/diagram content="flowchart TB
subgraph media\["Media Layer"]
M((Media))
LR\[Live Rooms]
CH\[Chat + Bullet Trading Comments]
GF\[Gifts]
RP\[Recording + Replay]
M --- LR
M --- CH
M --- GF
M --- RP
end

subgraph trading\["Trading Layer"]
T((Trading))
SA\[Spot Aggregator]
ZE\[ZK Perps Engine]
RE\[Risk Engine + Account State]
T --- SA
T --- ZE
T --- RE
end

subgraph eco\["Ecosystem Layer"]
E((Ecosystem))
SE\[Pumpkin Seeds]
BC\[Builder Code: extra user-paid add-on]
RB\[Rebates: from trading fees]
VA\[Vaults: coming soon]
E --- SE
E --- BC
E --- RB
E --- VA
end

LR -->|trade intents| T
T -->|verified events| CH
T -->|markers| RP

E --> T
E --> M
" %}

#### Wallet and onboarding

Pumpkin uses [Privy](https://www.privy.io/) for login and wallet provisioning, supporting email/social login and mainstream external wallets (e.g., MetaMask, OKX Wallet). Privy-generated addresses are secured by Privy’s wallet infrastructure.


# Media Layer

Pumpkin’s media layer is designed for one purpose: to make live trading credible and scalable.

### Live Streaming (Trading-grade)

Pumpkin supports:

* audio
* video
* screen sharing
* OBS ingest
* multi-host participation (up to 9)
* gifts (single and multi-recipient)
* real-time trading bullet comments

{% @mermaid/diagram content="

flowchart LR
OBS\[OBS Ingest] --> ING\[Ingest Service]
ING --> LL\[Low-Latency Delivery]
HOST\[Hosts/Guests] --> SFU\[WebRTC SFU]
SFU --> LL
LL --> VIEW\[Viewers]
VIEW --> BUS\[Realtime Bus: chat/trades/gifts]" %}

#### Why this matters for live trading

A live trading room is interactive: viewers ask questions, follow trades, watch guests debate, and react instantly. Low-latency and multi-host capacity are core requirements—not optional media features.

### Recording & Replay

Pumpkin records sessions and indexes them with event markers so users can replay the market narrative, not just watch a video.

{% @mermaid/diagram content="flowchart LR
LIVE\[Live Room] --> REC\[Recording Pipeline]
LIVE --> EVT\[Trading + Room Events]
EVT --> IDX\[Marker Indexer]
REC --> REP\[Replay Player]
IDX --> REP" %}

Markers can include:

* strategy publish moments
* entry/exit events
* stop updates
* funding events
* liquidation risk warnings
* major chat highlights


# Trading Layer

Pumpkin’s trading layer is designed to support live trading. That imposes a stricter requirement than “a DEX UI”:

* execution must be fast enough to follow a room in realtime,
* state must be verifiable enough to prevent performance theater,
* and the terminal must be powerful enough for professional flows without leaving the surface.

***

### Spot Aggregation (Multi-chain)

Pumpkin supports onchain spot trading across Solana, Base, BSC, and the broader EVM ecosystem, aggregating liquidity across mainstream DEX venues and routing paths.

#### Routing philosophy: optimize expected outcome, not only quoted price

A real router optimizes a composite objective:

* output after impact and fees
* execution success probability
* latency penalties
* slippage bounds
* fallback path reliability

{% @mermaid/diagram content="flowchart LR
Q\[Quote Collection] --> P\[Path Generation]
P --> S\[Simulation + Slippage Bounds]
S --> X\[Execution + Fallback]
X --> R\[Receipt Parsing]
R --> U\[Fill Events + Trace Links]" %}

### ZK Perpetuals Engine

#### Design goal

Deliver high-performance perpetual trading with:

* deterministic matching and risk rules,
* verifiable accounting (PnL, funding, liquidation),
* and an execution layer that cannot “cheat” via hidden ledger manipulation.

#### The exchange as a provable state machine

Pumpkin models the perps exchange as a state machine with a canonical committed state root:

**State includes (conceptual):**

* account collateral balances
* open positions (size, entry, funding index)
* open orders
* market configs and risk parameters
* fee accumulators (protocol, rebates, builder add-ons)
* event log commitments (for audit and replay)

Each batch applies a set of inputs (orders, cancels, oracle samples, funding updates, liquidations) and produces a new state root.

A proof attests:\
**“Given previous root and batch inputs, the new root is correct.”**

Only verified proofs are accepted onchain.

{% @mermaid/diagram content="flowchart TB
U\[Signed Orders + Cancels] --> SQ\[Sequencer: batch builder]
O\[Oracle Samples + Funding Inputs] --> SQ
SQ --> EX\[Deterministic Matching + Risk Transition]
EX --> PR\[Prover: generate validity proof]
PR --> VC\[Onchain Verifier]
VC --> SR\[State Root Update]
SR --> EV\[Event Commitments + Receipts]" %}

#### Matching policy: price-time priority

Pumpkin uses price-time priority by default:

* highest priority to best price
* within the same price level, earliest time first
* deterministic partial-fill rules
* deterministic tie-breaking

This matters because the matching rule must be:

1. understandable to traders, and
2. enforceable inside the proof.

#### Risk enforcement as circuit invariants

Risk is enforced as invariants inside the state transition, not as a discretionary system setting. Examples:

* positions cannot transition into invalid margin states except via defined liquidation transitions
* leverage caps and position limits are enforced deterministically
* liquidation eligibility is computed from approved price constructions

#### Price constructions: last, index, and mark

Pumpkin supports multiple price types:

* **Last price:** executed trade price
* **Index price:** external reference aggregation
* **Mark price:** used for liquidation safety

Candle series can be derived from each type to provide transparency and reduce manipulation risk.

#### Liquidation as a deterministic, provable transition

Liquidation events are part of the same proven state machine.

{% @mermaid/diagram content="flowchart LR
M\[Mark Price Update] --> C\[Margin Check]
C -->|Healthy| H\[No Change]
C -->|Below Threshold| L\[Liquidation Transition]
L --> U\[State Update + Event Commitment]" %}

### Trading Terminal Innovations

Pumpkin’s terminal is designed as an execution environment that can keep up with live trading. These features are not “nice-to-haves”; they reduce follow friction, improve comprehension, and increase safety.

#### Multi-chart split (15 layouts)

Users can view multiple charts simultaneously with 15 layouts—critical for correlation monitoring, hedging, and multi-market sessions.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2F4kMT3TkWiP78Vxve7hK8%2Fscreenshot-20260118-023445.png?alt=media&amp;token=5c55ad5a-47a7-4f1b-9f02-0540dc614a85" alt=""><figcaption></figcaption></figure>

#### Fully modular UI layout

Trading components (chart, order panel, orderbook, positions, fills, alerts) are movable and resizable, allowing both beginners and professionals to build a workflow that matches their execution style.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FbhnD7TNfjMDthqgfyGfI%2Fscreenshot-20260118-023757.png?alt=media&amp;token=5918225e-cdb2-48b1-b0b4-7cff47e0c4f5" alt=""><figcaption></figcaption></figure>

#### Sound alerts for critical events

Users can configure sound alerts for:

* TP/SL triggers
* funding events
* auto-deleveraging events
* liquidation proximity warnings

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FoV7biFYr2foMZc8OgsTu%2Fscreenshot-20260118-023915.png?alt=media&amp;token=4071c318-87a0-4612-8758-e9bd11fb8ddc" alt=""><figcaption></figcaption></figure>

#### Position management: merge vs split

Positions can be managed in merged mode or split mode.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2F1UagME6DS90BWe414bWI%2Fscreenshot-20260118-024044.png?alt=media&amp;token=21cdbe20-5903-456e-92bd-b058f6bc2670" alt=""><figcaption></figcaption></figure>

#### Trade-on-chart workflows

Pumpkin supports professional workflows:

* click-to-order on the chart
* drag-to-set TP/SL
* chart markers and annotations
* reverse position

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FbREWXWHPf3jW103BKfGO%2Fscreenshot-20260118-024441.png?alt=media&amp;token=08ee2797-e204-4734-b8c4-38a10fdbc4f9" alt=""><figcaption></figcaption></figure>

#### Themes (six styles)

Pumpkin offers six trading themes to improve long-session comfort.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FIRLTyz79zFPPkUNiUBmE%2Fscreenshot-20260118-024602.png?alt=media&amp;token=6c29c9bf-a550-4b84-9aa2-ec5bad4dcda3" alt=""><figcaption></figcaption></figure>

#### Position direction modes: hedged vs one-way

* **Hedged mode:** hold long and short simultaneously (execution-friendly).
* **One-way mode:** single net position (capital efficient, professional/MM friendly).

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FJfiGEevgRLpH923ExMtf%2Fscreenshot-20260118-024840.png?alt=media&amp;token=b54f31ae-8c4d-48e2-81df-822c45d5f2ee" alt=""><figcaption></figcaption></figure>


# Streaming Becomes Execution

### Market ↔ Room binding

Pumpkin binds markets and rooms bidirectionally:

* Market pages surface rooms explaining the market now.
* Rooms surface the market execution surface and trade objects.

This binding makes discovery and execution mutually reinforcing.

### Verified performance on room covers

Room covers display verified performance signals so discovery rewards truth rather than marketing. Verification is anchored to:

* proof-backed perps events, and
* receipt-backed spot events.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FcuUxWsO51vLwnazDQQnp%2Fscreenshot-20260118-025607.png?alt=media&amp;token=6e48a41b-c6a1-4f84-9cfb-47e931dca1d6" alt=""><figcaption></figcaption></figure>

### Realtime positions for hosts and guests

In-room position displays let viewers understand exposure while it happens. Because disclosure must be safe, the system can support configurable controls,  such as:

* show/hide per market
* delayed display

### 6.4 Trades pushed into chat and bullet comments

Host trades are emitted as realtime events into chat and bullet comments, creating a social order tape. Viewers can tap to follow, open the chart, or set an alert.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2F9FK9bvnvfsTpoflcRaab%2Fscreenshot-20260118-025904.png?alt=media&amp;token=8f00bdff-af8a-47d3-bc89-ae204c7a97ff" alt=""><figcaption></figcaption></figure>

### Strategy publishing and instant copying

Hosts can publish strategy objects; viewers can copy instantly with risk guardrails and full fee transparency.

{% @mermaid/diagram content="flowchart LR
H\[Host publishes strategy] --> V\[Viewer taps Follow]
V --> P\[Preview: fees + builder add-on]
P --> R\[Risk checks + restrictions]
R --> E\[Execute]
E --> M\[Marker + verified event]" %}


# Gifts

Gifts in Pumpkin are not cosmetic decorations. They are a native economic primitive inside the Live Market Layer: a direct, realtime way for audiences to reward creators and guests, reinforce social proof, and amplify discovery—without pushing monetization outside the product.

To preserve consistency across mobile app stores and the web, Pumpkin uses a dual-rail value system:

* **Coins**: the spending unit used to send gifts
* **Crystals**: the earning unit received by gift recipients

This separation enables clean settlement, flexible redemption, and predictable user experience across platforms.

{% @mermaid/diagram content="flowchart TB
%% USERS
S\[Sender / Viewer] -->|Send gift| G\[Gift action in Live Room]
G -->|Recipient gets| C\[Crystals credited]

%% COINS ACQUISITION
subgraph Coins Acquisition
A1\[iOS/Android App] -->|Apple Pay / Google Play| COIN\[Coins balance]
W1\[Web] -->|Fiat or Crypto| COIN
end

%% SENDER USES COINS
COIN -->|Spend Coins| G

%% RECIPIENT REDEMPTION
subgraph Crystal Redemption
C -->|App| COIN\_APP\[Coins]
C -->|Web| COIN\_WEB\[Coins]
C -->|Web| CRYPTO\[Crypto]
C -->|Web| FIAT\[Fiat]
end
" %}

#### 1) Core mechanics

**1.1 Spending: gifts require Coins**

A viewer must hold Coins to send gifts. Coins are consumed at the moment a gift is delivered (to one person or multiple recipients in the room).

**1.2 Receiving: gifts generate Crystals**

Recipients do not receive Coins directly. They receive Crystals, which represent earned value attributable to gifts received during live sessions.

Crystals are a unified “earned balance” across Pumpkin platforms, while redemption options vary by platform to satisfy different payment rails and user needs.

#### 2) How users obtain Coins

Pumpkin supports platform-specific purchasing flows:

* **In-app (Android/iOS):** Coins are purchased using
  * **Google Play Billing** (Android)
  * **Apple Pay / Apple In-App Purchase** (iOS)
* **Web:** Coins are obtained via exchange using
  * **crypto → coins**, or
  * **fiat → coins**

#### 3) How recipients redeem Crystals

Crystals can be redeemed differently depending on platform:

* **In-app (Android/iOS):**
  * **Crystals → Coins**
* **Web:**
  * **Crystals → Coins**
  * **Crystals → Crypto**
  * **Crystals → Fiat**


# Fees

### Fees

* **Gift fee**

A $100 gift sent by Alice is settled as: Bob receives $90 in Crystals, Bob’s referrer receives $1 in Crystals, and the live-room owner/creator receives $1 in Crystals (with the remaining portion allocated to protocol fees and other applicable distributions).

{% @mermaid/diagram content="flowchart TB
A\[Alice sends $100 Gift] --> S\[Gift Settlement Engine]

S --> B\[Bob + $90 Crystals]
S --> R\[Bob's Referrer + $1 Crystals]
S --> O\[Room Owner  + $1 Crystals]
S --> P\[Protocol + $8 Crystals]" %}

* **Spot fee:** 1% on-chain trading fee
* **Perps fee:** maker/taker tiered by rolling 14-day volume

<table><thead><tr><th width="140.89453125">VIP Level</th><th width="308.19140625">14-Days Trading Vol </th><th>Maker Fees</th><th>Taker Fees</th></tr></thead><tbody><tr><td>VIP 0</td><td>≥ 0 USDT</td><td>0.02%</td><td>0.05%</td></tr><tr><td>VIP 1</td><td>≥ 2,500,000 USDT</td><td>0.018%</td><td>0.045%</td></tr><tr><td>VIP 2</td><td>≥ 10,000,000 USDT</td><td>0.015%</td><td>0.04%</td></tr><tr><td>VIP 3</td><td>≥ 50,000,000 USDT</td><td>0.01%</td><td>0.035%</td></tr><tr><td>VIP 4</td><td>≥ 100,000,000 USDT</td><td>0.005%</td><td>0.03%</td></tr><tr><td>VIP 5</td><td>≥ 500,000,000 USDT</td><td>0%</td><td>0.02%</td></tr></tbody></table>


# API

Pumpkin provides powerful APIs for real-time trading, please refer to the following links for usage instructions.

API Management: [https://www.pumpkin.xyz/api-manage](https://test-pumpex-www.pumpkin.date/api-manage)

English API document: [https://openapi-docs.pumpkin.xyz](https://openapi-docs.pumpkin.xyz/)

Chinese API document: <https://openapi-docs.pumpkin.xyz/index_zh.html>


# Pumpkin Seeds

Pumpkin Seeds are the system that ties traders, creators, and incentives into one coherent economy.

### Season model

**Season 1:** approximately 12 weeks\
**Accounting cadence:** weekly\
**Distribution day:** every Tuesday, based on the prior week’s contribution

This weekly rhythm creates predictable engagement and allows users to plan behavior around a clear incentive calendar.

### Four contributor classes

Seeds primarily reward four categories of contribution:

#### (1) Real traders: genuine fills and long-term activity

Pumpkin seeds reward sustained, real activity rather than superficial volume.

#### (2) Loss subsidy: weekly net-loss users receive pumpkin seeds

Users with net losses in a week receive Seeds subsidies to reduce attrition and encourage learning. This is a deliberate retention mechanism: it turns losses into a continuing relationship rather than an exit point.

#### (3) Liquidation subsidy: controlled and capped

Rules:

* at most one liquidation subsidy per week
* at most three times per season per user

This is designed to reinforce risk awareness, not encourage reckless leverage.

#### (4) Streaming rewards: high-quality creators and active rooms

Seeds reward creators who produce valuable content and drive meaningful activity. Metrics can include active viewer minutes, retention, strategy usage, and verified engagement.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FVlWinvUn27Thlix2IPyq%2Fscreenshot-20260118-031007.png?alt=media&amp;token=08bc34e7-70d1-45b3-8949-a035b6e33a17" alt=""><figcaption></figcaption></figure>

### Weekly transparency as a product requirement

Pumpkin seeds must not feel like a black box. A formal Seeds UI should show:

* weekly breakdown by category
* why the user qualified
* what actions improve next week’s score

### Seeds buyback program (coming soon)

Pumpkin will allocate a portion of platform profits to buy back pumpkin seeds. This creates two potential pathways for users:

* holding pumpkin seeds for future TGE conversion, and
* selling pumpkin seeds through buyback-driven demand.


# Referral & Affiliates

Pumpkin supports both standard referral and permissioned multi-level rebate structures.

### Referral

Pumpkin’s standard referral program is enabled by default.\
Rebate rate: 10% of eligible trading fees generated by referred users.

### Affiliates

For partners, communities, and operators, Pumpkin offers a permissioned Affiliate (multi-level) rebate program. This program is not enabled by default and requires approval and configuration through Pumpkin BD.

Please refer to the following link for Pumpkin Affiliate instructions.

[https://agent.pumpkin.xyz](https://agent.pumpkin.xyz/)

Maximum rebate share: up to 50%+ of eligible trading fees, depending on:

partner tier and negotiated configuration,

structure depth and level splits,

qualification rules and performance thresholds,

anti-abuse and risk controls.

{% @mermaid/diagram content="flowchart TB
L0\[Partner] --> L1\[Level 1]
L1 --> L2\[Level 2]
L2 --> U\[Trader]
U --> F\[Trading fees]
F --> R0\[Rebate -> L0]
F --> R1\[Rebate -> L1]
F --> R2\[Rebate -> L2]
F --> Rn\[Rebate -> ...]" %}


# Official Links

Website: [https://pumpkin.xyz](https://pumpkin.xyz/)

App Download: <https://www.pumpkin.xyz/guide>

API Document: [https://openapi-docs.pumpkin.xyz](https://openapi-docs.pumpkin.xyz/)

Discord: <https://discord.gg/pumpkin>

Telegram Channel: <https://t.me/pumpkin_global>

Telegram Global Group: <https://t.me/pumpkinglobal_group>

Twitter: <https://twitter.com/pumpkin_global>

Facebook: <https://www.facebook.com/pumpkin.global.official>

Linkedin: [https://www.linkedin.com/company/pumpkinglobal](https://www.linkedin.com/company/pumpkinglobal/)

Youtube: <https://www.youtube.com/@Pumpkin.global.official>

Instagram: <https://www.instagram.com/pumpkin.global.official>

Threads: <https://www.threads.net/@pumpkin.global.official>

Tiktok: <https://www.tiktok.com/@pumpkin_global>

Linktree: <https://linktr.ee/pumpkin_global>

{% embed url="<https://play.google.com/store/apps/details?id=com.pumpkin.date>" %}

{% embed url="<https://apps.apple.com/us/app/pumpkin-pro/id1566536854>" %}


# How to use OBS

### Download OBS (Live Streaming Software)

Visit the official OBS website and download the version compatible with your system.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2F1yuOWRVtEfospBMZ1RVp%2Fimage.png?alt=media&amp;token=39c3f9f1-1a7b-4b8c-9118-698da5b47414" alt=""><figcaption></figcaption></figure>

### Get Your Streaming URL

Click the **"OBS"** button to get your unique streaming URL on your host live room.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FcpeumIurX0KtaARhCJZI%2Fimage.png?alt=media&amp;token=c784e9f3-7e00-4dd6-9e47-374a2a5fa23a" alt=""><figcaption></figcaption></figure>

### How to Stream with OBS

#### Open OBS

Once installed, launch OBS and close the welcome wizard. You'll see the main interface.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FAdewZ0EOklGvRUji4Qbg%2Fimage.png?alt=media&amp;token=a7efc928-8c3c-49f6-bfa9-9113523267bb" alt=""><figcaption></figcaption></figure>

1️⃣ This is the live preview window (black until sources are added).

2️⃣ Create and manage different scenes here.

3️⃣ Add video and audio sources for each scene.

#### Add Screen Capture

In the **Sources** panel, click the **"+"**, select **"Screen Capture"**, and click **OK**.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FERpWpdt047057oFEfxqd%2Fimage.png?alt=media&amp;token=d605b9ac-0eb2-414e-8666-dc0ac74f698f" alt=""><figcaption></figcaption></figure>

#### Add Microphone Input

In the **Sources** panel, Click the **"+"** again, select **"Audio Input Capture"**, choose your mic, and click **OK**.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FBRN0o6CMOjFIqkpzY9B6%2Fimage.png?alt=media&amp;token=c6d2e3fe-7324-4313-8fd6-8f87781003a5" alt=""><figcaption></figcaption></figure>

#### Test Your Microphone

Speak into your mic and watch the **Audio Mixer**. If the volume bar moves, your audio is working.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FDvf9G1ZYV5BVb3oRWpl1%2Fimage.png?alt=media&amp;token=83f036b9-15ac-4f04-8fb8-d99e287a3984" alt=""><figcaption></figcaption></figure>

#### **Adjust the Preview Window**

If you’re using two monitors, select the screen you want to stream, then click **OK**.\
You should now see your screen in the preview window.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FFUplGAyT3xPZukqX8qPk%2Fimage.png?alt=media&amp;token=0f42ebcf-fc6f-4b5b-a5c2-176841ab3c69" alt=""><figcaption></figcaption></figure>

#### **Configure Stream Settings**

Go to **Settings** → **Stream**. Set **Service** to **Custom**.

Enter the **Server** and **stream key** from your OBS Streaming section.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FXWk9ARcUXzN4klePD1D8%2Fimage.png?alt=media&amp;token=50954fe0-ab1c-40f4-a8d6-6b633e35db3b" alt=""><figcaption></figcaption></figure>

#### Start Streaming

Back on the homepage, click **"Start Streaming"** to begin. You can now preview your stream inside Pumpkin Vibe.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FYIYdEoUu5QtiKyLtYdl2%2Fimage.png?alt=media&amp;token=eae5bf51-bdba-413d-b353-2e20f9a881d6" alt=""><figcaption></figcaption></figure>

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FOxrznaaCsrSJAwc09Rm2%2Fimage.png?alt=media&amp;token=d06a1920-5aa3-4e78-aa06-d65265d6b1a3" alt=""><figcaption></figcaption></figure>

To stop streaming, click **"Stop Streaming"** in OBS, then click **"Exit OBS"** in Pumpkin live stream.

#### Troubleshooting

If the stream lags, check the bottom-right corner for dropped frames or poor network status.

A red indicator means your connection is unstable. Try switching to a faster network.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2Fhb2NHK6qP9541hpKZeb0%2Fimage.png?alt=media&amp;token=dd6c49c3-cf82-4611-95be-a87d79bbb100" alt=""><figcaption></figcaption></figure>

#### **Recommended OBS Settings**

Your OBS settings impact stream quality and smoothness. We recommend using the following setup for the best performance and viewer experience.

<figure><img src="https://638236114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtLwBst9UyAxgrxJ3W2CW%2Fuploads%2FKJDDVMaNtoqFjx4wIFf4%2Fimage.png?alt=media&amp;token=384073aa-2f9d-4294-8e56-d88a0b04580f" alt=""><figcaption></figcaption></figure>