release: 2.50.7 — Limitless hosted writes documented + SDK error string fixed + operator multisig wording

realfishsam · realfishsam · commit c0343e82d0a2 · 2026-06-18T13:33:16.000+03:00
diff --git a/changelog.md b/changelog.md
@@ -2,6 +2,29 @@
 
 All notable changes to this project will be documented in this file.
 
+## [2.50.7] - 2026-06-18
+
+### Fixed
+
+- **`sdks/typescript/pmxt/hosted-routing.ts`** + **`sdks/python/pmxt/_hosted_routing.py`**: `HOSTED_TRADING_VENUES` includes `limitless` (since 2.50.3 wired the `limitless_buy` / `limitless_sell_polygon` / `limitless_sell_base_pull` / `cancel_limitless_*` schemas), but the `NotSupported` error message thrown to callers attempting hosted trading on an unsupported venue still said "Hosted trading is only supported for Polymarket and Opinion". A caller who hit the error would believe Limitless was unsupported even though it would have worked, and anyone reading the SDK source to figure out which venues are hosted-tradable saw a directly contradictory pair (the set says yes, the error string says no). Updated both SDKs to "Polymarket, Opinion, and Limitless".
+
+### Docs
+
+- **Limitless hosted writes documented across the docs surface.** The 2.50.3 release wired Limitless through the hosted trading path but no doc page reflected it, so the docs collectively asserted Limitless was read-only / self-hosted-writes-only. Updated nine claim sites across six files:
+  - `docs/trading-quickstart.mdx:9` — "Hosted writes today: Polymarket, Opinion, and Limitless."
+  - `docs/authentication.mdx:83` — same.
+  - `docs/security.mdx:54` — "Hosted (Polymarket, Opinion, Limitless): PMXT never sees the venue private key."
+  - `docs/guides/escrow-lifecycle.mdx:9` — escrow funding line now lists Polymarket, Opinion, and Limitless as the "today" set.
+  - `docs/guides/escrow-lifecycle.mdx:20` — "Hosted exchange clients (Polymarket, Opinion, Limitless) expose an `escrow` namespace."
+  - `docs/guides/self-hosted.mdx:15` — hosted-writes list updated; Limitless removed from the self-hosted-only list of venues.
+  - `docs/guides/self-hosted.mdx:20` — "consumer app against Polymarket, Opinion, or Limitless".
+  - `docs/concepts/hosted-trading.mdx:9` — "trade Polymarket, Opinion, and Limitless" in the funding-once paragraph.
+  - `docs/concepts/hosted-trading.mdx:18` — "trading across Polymarket, Opinion, and Limitless".
+  - `docs/concepts/hosted-trading.mdx:51` — added a Limitless settlement sentence: "buys are settled on Polygon directly from escrow; sells use a Base-side pull leg that draws against the user's Polygon escrow" (the Polymarket and Opinion settlement descriptions were already there).
+  - `docs/concepts/hosted-trading.mdx:119` — Hosted-vs-self-hosted comparison table: "Trading venues | Polymarket, Opinion, Limitless".
+  - `docs/concepts/hosted-trading.mdx:131` — "What's supported today" table: added a Limitless row (Yes / Yes / "Polygon buy leg, Base pull-sell leg") and removed Limitless from the Kalshi/Smarkets/etc. read-only row.
+- **`docs/concepts/hosted-trading.mdx:89` — operator multisig wording.** The previous wording said "A multisig replacement is planned but not yet deployed" on one line while line 93 said `operator` is `immutable`. Read straight through, that reads like an in-place rotation that the contract design forbids. Rewrote to "Because `operator` is `immutable` on the deployed contracts, switching to a multisig would mean deploying new escrow contracts and migrating user balances — not an in-place rotation." Same facts, no contradiction.
+
 ## [2.50.6] - 2026-06-18
 
 ### Docs
diff --git a/docs/authentication.mdx b/docs/authentication.mdx
@@ -80,7 +80,7 @@ deposit_tx = client.escrow.deposit_tx(amount=10.0)
 
 See [Trading quickstart](/trading-quickstart) for the full 60-second flow
 and [Escrow lifecycle](/guides/escrow-lifecycle) for the approve / deposit /
-withdraw mechanics. Hosted writes today: Polymarket and Opinion.
+withdraw mechanics. Hosted writes today: Polymarket, Opinion, and Limitless.
 
 ### Self-hosted / direct venue credentials (advanced)
 
diff --git a/docs/concepts/hosted-trading.mdx b/docs/concepts/hosted-trading.mdx
@@ -6,7 +6,7 @@ description: "The hosted-default execution path — how PMXT routes orders, the
 Hosted trading is PMXT's default execution path. You provide an API key and a wallet; your [USDC](/concepts/prediction-markets-101#usdc) sits in a non-custodial [`PreFundedEscrow`](/concepts/prediction-markets-101#prefundedescrow) smart contract on [Polygon](/concepts/prediction-markets-101#polygon) that can only move funds against an EIP-712 signature from your wallet; orders are built server-side, signed in your browser/server with your private key, and submitted by PMXT to the underlying venue. You never run a local server, never integrate with venue-specific signature schemes, and never expose your private key over the wire.
 
 <Info>
-  **One chain to fund: Polygon.** All hosted trading uses a single Polygon-based `PreFundedEscrow` contract for every supported venue. Fund USDC on Polygon once and your same wallet and key trade Polymarket *and* Opinion (and future venues). For non-Polygon venues like Opinion (on BSC), PMXT handles cross-chain settlement transparently — you never sign anything on a chain other than Polygon. Pass any EVM-compatible private key.
+  **One chain to fund: Polygon.** All hosted trading uses a single Polygon-based `PreFundedEscrow` contract for every supported venue. Fund USDC on Polygon once and your same wallet and key trade Polymarket, Opinion, *and* Limitless (and future venues). For non-Polygon venues like Opinion (on BSC), PMXT handles cross-chain settlement transparently — you never sign anything on a chain other than Polygon. Pass any EVM-compatible private key.
 </Info>
 
 ## When hosted mode is right
@@ -15,7 +15,7 @@ Hosted is the right default for:
 
 - **Web and mobile apps** — your backend holds the `pmxt_api_key`; users keep their own private keys on their devices.
 - **Trading bots that don't need sub-100ms latency** — typical hosted round-trip is ~150–300ms including the venue submit.
-- **Multi-venue strategies** — you stay on one HTTP surface even when you're trading across Polymarket and Opinion.
+- **Multi-venue strategies** — you stay on one HTTP surface even when you're trading across Polymarket, Opinion, and Limitless.
 - **Anyone who doesn't want to operate infrastructure.**
 
 A hosted trade has three actors: **your client** (holding the `pmxt_api_key` and, for writes, the user's `private_key`), **`trade.pmxt.dev`** (PMXT's hosted trading API — routes orders, operates against the escrow contract under user-signed authorization, talks to the venue), and **the venue** (Polymarket's CLOB, Opinion's matching engine, etc. — sees PMXT as the submitter).
@@ -48,7 +48,7 @@ Step-by-step:
 1. **Build.** The SDK calls `POST /v0/trade/build-order` with the catalog UUIDs (`market_id`, `outcome_id`), side, and amount. The server resolves the venue-native fields (token IDs, salt, expiry, fees), packages them into the venue's EIP-712 typed-data shape, and returns a `built_order_id` plus the payload to sign.
 2. **Sign.** The SDK signs the typed-data payload locally with your `private_key`. This step never leaves your process. See [Signing](/guides/signing) for the exact shape.
 3. **Submit.** The SDK calls `POST /v0/trade/submit-order` with the `built_order_id` and the signature. The server attaches the signature to the prepared order and submits to the venue.
-4. **Settle.** The venue matches the order. On Polymarket, fills come from the CLOB and are settled on Polygon via the CTF exchange. On Opinion, settlement uses a dual-signature cross-chain flow.
+4. **Settle.** The venue matches the order. On Polymarket, fills come from the CLOB and are settled on Polygon via the CTF exchange. On Opinion, settlement uses a dual-signature cross-chain flow into a BSC-side `VenueEscrow`. On Limitless, buys are settled on Polygon directly from escrow; sells use a Base-side pull leg that draws against the user's Polygon escrow.
 
 `create_order` is a convenience wrapper that chains build → sign → submit in one call. `build_order` and `submit_order` are the lower-level primitives if you want to inspect or modify the typed-data before signing.
 
@@ -86,7 +86,7 @@ Current operator addresses (immutable on the deployed contracts above):
 - BSC `VenueEscrow.operator`: `0x84194eae9c63C1e3A769976bb762506d3443156d`
 - Polygon `PreFundedEscrow.settlementOracle`: `0x8aD93c0D15bC655b460dD700B1E25C86D1a728EE`
 
-The operator address is currently an EOA controlled by PMXT. A multisig replacement is planned but not yet deployed; this page will be updated when it lands.
+The operator address is an EOA controlled by PMXT. Because `operator` is `immutable` on the deployed contracts, switching to a multisig would mean deploying new escrow contracts and migrating user balances — not an in-place rotation.
 
 ### Trust model
 
@@ -116,7 +116,7 @@ Self-hosted runs `pmxt-core` on your own machine; the SDK talks to `localhost`.
 | **Writes** | `trade.pmxt.dev/v0/trade/{build,submit}-order` | Direct to the venue API |
 | **Custody** | Non-custodial: USDC in `PreFundedEscrow`, movable only against your EIP-712 signature | You retain venue-native custody |
 | **Latency** | ~150–300ms round-trip | Limited by venue + your network |
-| **Trading venues** | Polymarket, Opinion | Every venue PMXT supports |
+| **Trading venues** | Polymarket, Opinion, Limitless | Every venue PMXT supports |
 | **Read-only venues** | All catalog venues via Router | All catalog venues via Router |
 | **Infra to run** | None | One local process |
 | **Regulatory posture** | Non-custodial escrow; user retains beneficial ownership and unilateral withdrawal | You as direct counterparty to the venue |
@@ -129,7 +129,8 @@ Choose self-hosted when you need **sub-100ms latency**, want to use **raw venue
 | ----- | ------------- | ------------ | ----- |
 | Polymarket | Yes | Yes | Polygon escrow, CLOB exchange |
 | Opinion | Yes | Yes | Cross-chain (BSC settlement, dual-signature) |
-| Kalshi, Limitless, Smarkets, Probable, Myriad, Metaculus, etc. | No | Read-only via catalog | Use [self-hosted](/guides/self-hosted) for writes |
+| Limitless | Yes | Yes | Polygon buy leg, Base pull-sell leg |
+| Kalshi, Smarkets, Probable, Myriad, Metaculus, etc. | No | Read-only via catalog | Use [self-hosted](/guides/self-hosted) for writes |
 
 If a venue you need isn't here, run pmxt-core locally and pass raw venue credentials — see [Self-hosted](/guides/self-hosted).
 
diff --git a/docs/guides/escrow-lifecycle.mdx b/docs/guides/escrow-lifecycle.mdx
@@ -6,7 +6,7 @@ description: "Deposit, trade, withdraw — how USDC moves through PMXT's non-cus
 Hosted trading on PMXT settles through a non-custodial `PreFundedEscrow` smart contract on **Polygon** (chainId 137). USDC sits in the escrow under your wallet's beneficial ownership; PMXT cannot move funds without an EIP-712 signature from your wallet. This page walks through the full lifecycle: approve, deposit, trade, withdraw.
 
 <Info>
-  **You fund Polygon only.** USDC always sits in the Polygon `PreFundedEscrow` — the single funding location for *every* hosted venue (Polymarket today, Opinion today, more coming). For venues that don't live on Polygon (e.g. Opinion on BSC), PMXT operates an internal cross-chain leg that holds outcome tokens on the venue's chain; you neither fund nor sign anything on that side. Pass any EVM-compatible private key — the same key handles every venue.
+  **You fund Polygon only.** USDC always sits in the Polygon `PreFundedEscrow` — the single funding location for *every* hosted venue (Polymarket, Opinion, and Limitless today; more coming). For venues that don't live on Polygon (e.g. Opinion on BSC), PMXT operates an internal cross-chain leg that holds outcome tokens on the venue's chain; you neither fund nor sign anything on that side. Pass any EVM-compatible private key — the same key handles every venue.
 </Info>
 
 ## Why escrow at all?
@@ -17,7 +17,7 @@ For Opinion, the same Polygon escrow balance funds a cross-chain settlement leg
 
 ## The `client.escrow` namespace
 
-Hosted exchange clients (Polymarket, Opinion) expose an `escrow` namespace. Every method **builds an unsigned transaction**. Your wallet — MetaMask, ethers `Wallet`, viem, web3.py, etc. — is responsible for signing and broadcasting it. PMXT never holds your private key.
+Hosted exchange clients (Polymarket, Opinion, Limitless) expose an `escrow` namespace. Every method **builds an unsigned transaction**. Your wallet — MetaMask, ethers `Wallet`, viem, web3.py, etc. — is responsible for signing and broadcasting it. PMXT never holds your private key.
 
 | Method (Python / TypeScript) | Description |
 | ---------------------------- | ----------- |
diff --git a/docs/guides/self-hosted.mdx b/docs/guides/self-hosted.mdx
@@ -12,12 +12,12 @@ Pick self-hosted if **any** of these apply:
 - **Sub-100ms latency** — local submission removes a network hop. Matters for latency-sensitive arb / market-making.
 - **Raw venue credentials** — Polymarket L2 API keys, Kalshi RSA, Smarkets session cookies. Hosted mode doesn't accept these.
 - **Regulatory custody** — you must be the direct counterparty with no intermediary in the custody path.
-- **Venues hosted mode can't write to yet** — hosted writes are Polymarket + Opinion. Self-hosted writes work on every venue PMXT supports (Kalshi, Limitless, Smarkets, Probable, Myriad, Metaculus, etc.).
+- **Venues hosted mode can't write to yet** — hosted writes are Polymarket, Opinion, and Limitless. Self-hosted writes work on every venue PMXT supports (Kalshi, Smarkets, Probable, Myriad, Metaculus, etc.).
 - **OSS contribution** — you're hacking on `pmxt-core` itself.
 
 ## When hosted is still the better choice
 
-Everyone else. [Hosted](/concepts/hosted-trading) is simpler to deploy (no local process), gives you on-chain custody you control via the timelock, and PMXT's server never sees a private key. If you're building a consumer app, a research notebook, or any non-latency-critical service against Polymarket or Opinion, stop here and use hosted.
+Everyone else. [Hosted](/concepts/hosted-trading) is simpler to deploy (no local process), gives you on-chain custody you control via the timelock, and PMXT's server never sees a private key. If you're building a consumer app, a research notebook, or any non-latency-critical service against Polymarket, Opinion, or Limitless, stop here and use hosted.
 
 ## 1. Install pmxt-core
 
diff --git a/docs/security.mdx b/docs/security.mdx
@@ -51,7 +51,7 @@ For on-chain venues (Polymarket, Limitless, Probable, Opinion, Baozi), "venue cr
 
 Credential type is a property of the venue, not of PMXT. See [Supported Venues](/concepts/venues) for the full credential matrix. The difference between modes is **where the credential lives**:
 
-- **Hosted (Polymarket, Opinion):** PMXT never sees the venue private key. You sign EIP-712 locally against the `PreFundedEscrow` domain; PMXT's operator submits with its own key for gas. See [Hosted trading](/concepts/hosted-trading).
+- **Hosted (Polymarket, Opinion, Limitless):** PMXT never sees the venue private key. You sign EIP-712 locally against the `PreFundedEscrow` domain; PMXT's operator submits with its own key for gas. See [Hosted trading](/concepts/hosted-trading).
 - **Self-hosted (any venue):** the venue credential lives on your machine, in your `pmxt-core` process.
 
 ## Recommendations
diff --git a/docs/trading-quickstart.mdx b/docs/trading-quickstart.mdx
@@ -6,7 +6,7 @@ description: "Place your first hosted trade in 60 seconds — API key, escrow de
 From a fresh `pmxt_api_key` to a confirmed position on Polymarket in under a minute. For the full hosted model, see [Hosted trading](/concepts/hosted-trading).
 
 <Info>
-Hosted writes today: **Polymarket** and **Opinion**. Other venues are read-only via the hosted catalog; use [self-hosted](/guides/self-hosted) to trade them.
+Hosted writes today: **Polymarket**, **Opinion**, and **Limitless**. Other venues are read-only via the hosted catalog; use [self-hosted](/guides/self-hosted) to trade them.
 </Info>
 
 ## 1. Get an API key
diff --git a/sdks/python/pmxt/_hosted_routing.py b/sdks/python/pmxt/_hosted_routing.py
@@ -261,7 +261,7 @@ def ensure_hosted_trading_supported(client: Any) -> None:
     if venue not in HOSTED_TRADING_VENUES:
         venue_label = venue or "unknown"
         raise NotSupported(
-            "Hosted trading is only supported for Polymarket and Opinion; "
+            "Hosted trading is only supported for Polymarket, Opinion, and Limitless; "
             f"{venue_label} is not supported with pmxt_api_key."
         )
 
diff --git a/sdks/typescript/pmxt/hosted-routing.ts b/sdks/typescript/pmxt/hosted-routing.ts
@@ -72,7 +72,7 @@ export function ensureHostedTradingSupported(client: HostedClientLike): void {
     if (!client.pmxtApiKey) return;
     if (!HOSTED_TRADING_VENUES.has(client.exchangeName)) {
         throw new NotSupported(
-            `Hosted trading is only supported for Polymarket and Opinion; ${client.exchangeName} is not supported with pmxtApiKey.`,
+            `Hosted trading is only supported for Polymarket, Opinion, and Limitless; ${client.exchangeName} is not supported with pmxtApiKey.`,
         );
     }
 }

Original file line number	Diff line number	Diff line change
`@@ -261,7 +261,7 @@ def ensure_hosted_trading_supported(client: Any) -> None:`
`261`	`261`	`if venue not in HOSTED_TRADING_VENUES:`
`262`	`262`	`venue_label = venue or "unknown"`
`263`	`263`	`raise NotSupported(`
`264`		`- "Hosted trading is only supported for Polymarket and Opinion; "`
	`264`	`+ "Hosted trading is only supported for Polymarket, Opinion, and Limitless; "`
`265`	`265`	`f"{venue_label} is not supported with pmxt_api_key."`
`266`	`266`	`)`
`267`	`267`
Original file line number	Diff line number	Diff line change
`@@ -72,7 +72,7 @@ export function ensureHostedTradingSupported(client: HostedClientLike): void {`
`72`	`72`	`if (!client.pmxtApiKey) return;`
`73`	`73`	`if (!HOSTED_TRADING_VENUES.has(client.exchangeName)) {`
`74`	`74`	`throw new NotSupported(`
`75`		- `Hosted trading is only supported for Polymarket and Opinion; ${client.exchangeName} is not supported with pmxtApiKey.`,
	`75`	+ `Hosted trading is only supported for Polymarket, Opinion, and Limitless; ${client.exchangeName} is not supported with pmxtApiKey.`,
`76`	`76`	`);`
`77`	`77`	`}`
`78`	`78`	`}`