# Polymarket Token in 2026?

- Space: [Trueo](https://snapshot.box/s:truemarkets.eth.md)
- Author: 0x3b43172F7018366E0259759bf947Af0131b36D82
- State: Closed
- Voting type: Single choice
- Start: 2026-04-29 15:41 UTC
- End: 2026-05-02 15:41 UTC
- Votes: 35
- Quorum: 500,000 voting power
- Open in Snapshot: https://snapshot.box/#/s:truemarkets.eth/proposal/0xd7aab70ae4205de5bf9069e09455ed6858df13c01300fe13d561d94dec376de2

## Results

- \#1: [8]: 3,154,495.33 voting power, 31.4%
- \#2: [16]: 8,701.58 voting power, 0.1%
- \#3: [24]: 0 voting power, 0.0%
- \#4: [32]: 6,892,721.3 voting power, 68.5%

## Proposal

### **Voting Title**

Polymarket Token in 2026?

---

### **Market Description**

This market will resolve to "Yes" if Polymarket launches an official token before January 1st, 2027 (00:00 PST). 

Otherwise, this market will resolve to "No." 

The token must be fungible, officially released by Polymarket, and communicated publicly through official Polymarket channels, for this market to resolve to "Yes."

NFT launches, promotional offerings, tokenized point systems, or token launches in collaboration with other projects and communities do not count as official tokens launched by Polymarket for the purpose of this market.


View on Trueo: https://trueo.com/market/0xa96ac028da2431f87fa02fb72aef948f2ef4e737

---

### **Voting Description**

This vote addresses a dispute regarding the "Polymarket Token in 2026?" on Trueo. Initially, the Resolver proposed the outcome as "Yes". The Disputer challenged this outcome, but the Oracle Council refused the dispute, maintaining the outcome as "Yes". Subsequently, the Escalated Disputer contested the Oracle Council's decision, requesting a re-vote by $TRUE Holders.

---

### **Reasons For Dispute**

Rules state: 

“…token launches in collaboration with other projects and communities do not count as official tokens launched by Polymarket”

pUSD is backed by USDC, technically its launch involves another project (Circle)

---

**Dispute Background**:

- **Initial Resolution**: Resolver proposed the outcome as "Yes".
- **Dispute and Arbitration**: Disputer challenged the outcome, but the Oracle Council refused the dispute, maintaining the outcome as "Yes".
- **Escalated Dispute**: Escalated Disputer contested the new outcome, requesting a re-vote.

---

### **Voting Items Description**

$TRUE Holders are now required to vote on the following items:

- **#1** - Keep the outcome as **Yes**, and Don't Slash. [8]
- **#2** - Set the outcome to **No**, and Don't Slash. [16]
- **#3** - Set the outcome to **CANCELED**, and Don't Slash. [24]
- **#4** - Set the outcome to **RESET**, and Don't Slash. [32]

---

### **Additional Info**

- **Market**: 0xa96ac028da2431f87fa02fb72aef948f2ef4e737
- **Resolver**: 0x2f17a2517841ab9C00bc14257afD72B49FEDFa32
- **Disputer**: 0xb095ed6D9103e195246ba6041091Baf1f8B4Aa55
- **Escalated Disputer**: 0xF2795af1e59a6C2B320A68d1d68c9E9c1C048d2A

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

