LimitlessSorry, looks like there will not be.
Sorry, looks like there will not be.
Jeremy | Limitless参与话题 89消息总数 208
该用户的聊天记录定位。
聊天记录
共 208 条，显示第 151-200 条clob markets use an order book. amm is an automated market maker market, think like a uniswap v2 liquidity pool. if you can place limit orders on the market it is a clob, also all clobs have a diamond symbol by them
clob markets use an order book. amm is an automated market maker market, think like a uniswap v2 liquidity pool. if you can place limit orders on the market it is a clob, also all clobs have a diamond symbol by them
The AMM markets have no issue earning XP, the CLOB markets fix is in progress.
The AMM markets have no issue earning XP, the CLOB markets fix is in progress.
There were many accounts trying to game the competition. They do not want to release any more information as it helps those actors to understand our detection rules. The leaderboard was released, rewards will be sent tomorrow.
There were many accounts trying to game the competition. They do not want to release any more information as it helps those actors to understand our detection rules. The leaderboard was released, rewards will be sent tomorrow.
I didn't get an answer to that.
I didn't get an answer to that.
They will be sent by end of day tomorrow.
They will be sent by end of day tomorrow.
<@990666584462852117> they are looking to do improvements today, please let me know if those are still not showing up tomorrow, then if you DM me all your info I'll look into it
<@990666584462852117> they are looking to do improvements today, please let me know if those are still not showing up tomorrow, then if you DM me all your info I'll look into it
It's not a bug, and you don't need REST at all. A binary Limitless market is a single order book keyed to the Yes/Up token (positionIds[0] = Yes, [1] = No) — both REST and the orderbookUpdate stream carry that same one ladder. The NO side mirrors the size because of the merge/split identity: 1 Yes + 1 No = $1, so a buy-Yes at p is the same liquidity as a sell-No at 1 − p. The contracts are shared, so size is genuinely identical — only the price flips to 1 − p. That's the real NO depth, not a fake one. So just derive NO from the Yes book you're already receiving — no polling, no 429s: `// from each orderbookUpdate (the Yes book) const noAsks = data.bids.map(b => ({ price: 1 - b.price, size: b.size })); // BUY No const noBids = data.asks.map(a => ({ price: 1 - a.price, size: a.size })); // SELL No // best No ask = 1 − best Yes bid; best No bid = 1 − best Yes ask` If your NO depth looks wrong, the likely culprit is copying the size (correct) without flipping the price to 1 − p. Fetch REST once on subscribe to seed state, then maintain everything from the WS stream.
It's not a bug, and you don't need REST at all. A binary Limitless market is a single order book keyed to the Yes/Up token (positionIds[0] = Yes, [1] = No) — both REST and the orderbookUpdate stream carry that same one ladder. The NO side mirrors the size because of the merge/split identity: 1 Yes + 1 No = $1, so a buy-Yes at p is the same liquidity as a sell-No at 1 − p. The contracts are shared, so size is genuinely identical — only the price flips to 1 − p. That's the real NO depth, not a fake one. So just derive NO from the Yes book you're already receiving — no polling, no 429s: `// from each orderbookUpdate (the Yes book) const noAsks = data.bids.map(b => ({ price: 1 - b.price, size: b.size })); // BUY No const noBids = data.asks.map(a => ({ price: 1 - a.price, size: a.size })); // SELL No // best No ask = 1 − best Yes bid; best No bid = 1 − best Yes ask` If your NO depth looks wrong, the likely culprit is copying the size (correct) without flipping the price to 1 − p. Fetch REST once on subscribe to seed state, then maintain everything from the WS stream.
There will be some improvements pushed out tomorrow
There will be some improvements pushed out tomorrow
I don't have the eta, but the team is aware and the distributions will be made.
I don't have the eta, but the team is aware and the distributions will be made.
Its been reported, some may just have a wide spread, there are some large liquidity providers on the platform
Its been reported, some may just have a wide spread, there are some large liquidity providers on the platform
Currently deploying an update, the team is working on it and there will be more improvements on Monday
Currently deploying an update, the team is working on it and there will be more improvements on Monday
@everyone **WE'RE GIVING AWAY $1,000,000 DURING THIS WORLD CUP!** ⚽️ Trade WC markets on Limitless, earn XP, climb the leaderboard, and compete for your share of an up to 1,000,000 USDC prize pool More activity = bigger prize share Your road starts now → http://limitless.is/wc2026 https://x.com/trylimitless/status/2065809210374291627
@everyone **WE'RE GIVING AWAY $1,000,000 DURING THIS WORLD CUP!** ⚽️ Trade WC markets on Limitless, earn XP, climb the leaderboard, and compete for your share of an up to 1,000,000 USDC prize pool More activity = bigger prize share Your road starts now → http://limitless.is/wc2026 https://x.com/trylimitless/status/2065809210374291627
Season 4 is running now through the end of October https://limitless.exchange/blog/points-season-4-announcement
Season 4 is running now through the end of October https://limitless.exchange/blog/points-season-4-announcement
They won't be releasing those analytics, they spent all day filtering out accounts that broke the rules and making it public gives a map on how to avoid detection next time. Its similar to how we don't release the exact airdrop formula.
They won't be releasing those analytics, they spent all day filtering out accounts that broke the rules and making it public gives a map on how to avoid detection next time. Its similar to how we don't release the exact airdrop formula.
no I don't have any updates
no I don't have any updates
Feel free to dm me to talk about this further Your detail payload's status: FUNDED and the orderbook's readiness are governed by different fields. FUNDED can be present even while a slot is not yet OPEN — so it tells you nothing about whether the book is readable. The book is gated purely by the slot's state == "OPEN" && tradable == true from the timeline endpoint. So: - Stop gating on status from get-market. It doesn't expose tradable. - Drive off GET /markets/timeline, take the slot whose state == "OPEN" and tradable == true, use that slot's slug for GET /markets/{slug}/orderbook. The doc text for the timeline slug field says this explicitly ("use it to fetch the orderbook… once tradable"). - For pre-warming the next 5-min slot, watch countdownSec/endAt on the current slot, grab the next slot's slug while it's still PRE_OPEN, and start reading its book the moment tradable flips true.
Feel free to dm me to talk about this further Your detail payload's status: FUNDED and the orderbook's readiness are governed by different fields. FUNDED can be present even while a slot is not yet OPEN — so it tells you nothing about whether the book is readable. The book is gated purely by the slot's state == "OPEN" && tradable == true from the timeline endpoint. So: - Stop gating on status from get-market. It doesn't expose tradable. - Drive off GET /markets/timeline, take the slot whose state == "OPEN" and tradable == true, use that slot's slug for GET /markets/{slug}/orderbook. The doc text for the timeline slug field says this explicitly ("use it to fetch the orderbook… once tradable"). - For pre-warming the next 5-min slot, watch countdownSec/endAt on the current slot, grab the next slot's slug while it's still PRE_OPEN, and start reading its book the moment tradable flips true.
Hey, this is best asked in our [Builders Chat](https://t.me/LimitlessBuildersChat) on Telegram. But this sounds reasonable to me, (I asked Claude to reference docs.limitless.exchange/llms.txt to answer) Endpoint — you have it right, but the readiness gate is the issue - Path/method: GET /markets/{slug}/orderbook — keyed by marketSlug, not tokenId. (The tokenId actually comes back inside the response; you don't pass it in.) - Auth: correct — public/unauthenticated. - Response shape: bids, asks (each {price, size}), plus adjustedMidpoint, lastTradePrice, maxSpread, minSize, and tokenId. Note it's expressed as bids/asks on a single book, not separate YES/NO books (see the YES/NO note below). So your request format is fine. The 400 is a state gate, not a format error. Why you're getting 400 "Market is not active" in FUNDED The order book for BTC 5-minute markets is only live when the slot is actually trading, and "FUNDED" is not that state. For recurring crypto slots the lifecycle the docs define is: PRE_OPEN → OPEN → SETTLING → SETTLED (plus FAILED) The critical rule from the timeline docs: ▎ A slot becomes tradable only when state == "OPEN" AND tradable == true — not merely when the start time arrives. FUNDED is the on-chain funding/collateralization status of the market contract — it means the slot exists and is capitalized, but it maps to the PRE_OPEN phase where the book isn't accepting orders yet. That's exactly the window that returns Market is not active. So to answer your core question directly: the order book does not function in FUNDED/PRE_OPEN. It functions only once the slot flips to OPEN + tradable. Correct read pattern 1. Don't drive off the market-detail FUNDED field. Instead resolve the currently tradable slug from GET /markets/active (returns only the open slot), or use GET /markets/timeline to look ahead at upcoming slots. 2. Gate your orderbook call on state == "OPEN" && tradable == true. Only then call GET /markets/{slug}/orderbook. 3. For zero-gap coverage on the 5-min cadence, poll the timeline near slot end and pre-warm the next slug's subscription during PRE_OPEN, then start reading the book the instant it transitions to OPEN. (One other 400 cause to rule out, unrelated to yours: the endpoint also rejects with 400 if the market is an AMM market that doesn't support an order book. Your message text — "Market is not active" — is the state gate, not this one.) YES/NO and GTC post-only makers - The endpoint returns one book (bids/asks) tied to the tokenId in the response — it's the CLOB for that outcome token. To get "the NO side," you read the complementary token's book; a bid on YES at price p is economically the ask on NO at (1 − p). There isn't a separate ?side=NO parameter — the directionality is YES bids/asks plus the price-complement relationship. - GTC post-only maker orders rest on this same book once it's OPEN. They won't appear (and can't be posted) while the slot is FUNDED/PRE_OPEN, which is consistent with the 400 you're seeing — the matching engine for that slot isn't accepting resting liquidity yet. Bottom line: your endpoint, slug-keying, and unauthenticated assumptions are all correct. The fix is purely the state check — wait for OPEN + tradable:true (driven by /markets/active or /markets/timeline) rather than calling the book in FUNDED. One caveat worth flagging: the docs describe the recurring-market states as PRE_OPEN/OPEN/SETTLING/SETTLED/FAILED, while your market-detail payload is surfacing FUNDED. If your detail endpoint exposes a separate tradable/state field, gate on that directly; if it only gives you FUNDED, switch to /markets/active as the source of truth for "is the book readable right now."
Hey, this is best asked in our [Builders Chat](https://t.me/LimitlessBuildersChat) on Telegram. But this sounds reasonable to me, (I asked Claude to reference docs.limitless.exchange/llms.txt to answer) Endpoint — you have it right, but the readiness gate is the issue - Path/method: GET /markets/{slug}/orderbook — keyed by marketSlug, not tokenId. (The tokenId actually comes back inside the response; you don't pass it in.) - Auth: correct — public/unauthenticated. - Response shape: bids, asks (each {price, size}), plus adjustedMidpoint, lastTradePrice, maxSpread, minSize, and tokenId. Note it's expressed as bids/asks on a single book, not separate YES/NO books (see the YES/NO note below). So your request format is fine. The 400 is a state gate, not a format error. Why you're getting 400 "Market is not active" in FUNDED The order book for BTC 5-minute markets is only live when the slot is actually trading, and "FUNDED" is not that state. For recurring crypto slots the lifecycle the docs define is: PRE_OPEN → OPEN → SETTLING → SETTLED (plus FAILED) The critical rule from the timeline docs: ▎ A slot becomes tradable only when state == "OPEN" AND tradable == true — not merely when the start time arrives. FUNDED is the on-chain funding/collateralization status of the market contract — it means the slot exists and is capitalized, but it maps to the PRE_OPEN phase where the book isn't accepting orders yet. That's exactly the window that returns Market is not active. So to answer your core question directly: the order book does not function in FUNDED/PRE_OPEN. It functions only once the slot flips to OPEN + tradable. Correct read pattern 1. Don't drive off the market-detail FUNDED field. Instead resolve the currently tradable slug from GET /markets/active (returns only the open slot), or use GET /markets/timeline to look ahead at upcoming slots. 2. Gate your orderbook call on state == "OPEN" && tradable == true. Only then call GET /markets/{slug}/orderbook. 3. For zero-gap coverage on the 5-min cadence, poll the timeline near slot end and pre-warm the next slug's subscription during PRE_OPEN, then start reading the book the instant it transitions to OPEN. (One other 400 cause to rule out, unrelated to yours: the endpoint also rejects with 400 if the market is an AMM market that doesn't support an order book. Your message text — "Market is not active" — is the state gate, not this one.) YES/NO and GTC post-only makers - The endpoint returns one book (bids/asks) tied to the tokenId in the response — it's the CLOB for that outcome token. To get "the NO side," you read the complementary token's book; a bid on YES at price p is economically the ask on NO at (1 − p). There isn't a separate ?side=NO parameter — the directionality is YES bids/asks plus the price-complement relationship. - GTC post-only maker orders rest on this same book once it's OPEN. They won't appear (and can't be posted) while the slot is FUNDED/PRE_OPEN, which is consistent with the 400 you're seeing — the matching engine for that slot isn't accepting resting liquidity yet. Bottom line: your endpoint, slug-keying, and unauthenticated assumptions are all correct. The fix is purely the state check — wait for OPEN + tradable:true (driven by /markets/active or /markets/timeline) rather than calling the book in FUNDED. One caveat worth flagging: the docs describe the recurring-market states as PRE_OPEN/OPEN/SETTLING/SETTLED/FAILED, while your market-detail payload is surfacing FUNDED. If your detail endpoint exposes a separate tradable/state field, gate on that directly; if it only gives you FUNDED, switch to /markets/active as the source of truth for "is the book readable right now."
I'll look into it
I'll look into it
Hey Aapieh, the refund has now been processed for this market.
Hey Aapieh, the refund has now been processed for this market.
No, it doesn't look like it. The order book is active with BTC, but it looks like much less activity on the other markets.
No, it doesn't look like it. The order book is active with BTC, but it looks like much less activity on the other markets.
The leaderboard's been updated
The leaderboard's been updated
try clearing your browser cache. Also, the last reward was a partial distribution, the rest should go out later today
try clearing your browser cache. Also, the last reward was a partial distribution, the rest should go out later today
By end of day it is expected they will have finished checking for rules violations
By end of day it is expected they will have finished checking for rules violations
you can dm me and i'll talk to the guy running that
you can dm me and i'll talk to the guy running that
@everyone Traders and Builders! Two more relevant features are getting shipped: Receive window. Attach a timestamp and a window (1 ms to 10 s) to any order. Anything stale or future-dated gets rejected with HTTP 425 instead of filling a book that has already moved. Binance-style semantics, fully opt-in: omit the fields and nothing changes for you. Post-only. For resting (GTC) orders. The order is rejected if it would immediately match, so you are guaranteed to land as a maker. All three (including the previously announced Self-trade prevention) are live on the Create Order endpoint: https://docs.limitless.exchange/api-reference/trading/create-order#optional-fields
@everyone Traders and Builders! Two more relevant features are getting shipped: Receive window. Attach a timestamp and a window (1 ms to 10 s) to any order. Anything stale or future-dated gets rejected with HTTP 425 instead of filling a book that has already moved. Binance-style semantics, fully opt-in: omit the fields and nothing changes for you. Post-only. For resting (GTC) orders. The order is rejected if it would immediately match, so you are guaranteed to land as a maker. All three (including the previously announced Self-trade prevention) are live on the Create Order endpoint: https://docs.limitless.exchange/api-reference/trading/create-order#optional-fields
Check the resolution rules for each market
Check the resolution rules for each market
In general, higher rate limits are coming. But, you can DM me your wallet address and I'll put in a request for a higher rate limit.
In general, higher rate limits are coming. But, you can DM me your wallet address and I'll put in a request for a higher rate limit.
With our new NAVI partnership comes this challenge. https://navi.limitless.exchange/
With our new NAVI partnership comes this challenge. https://navi.limitless.exchange/
@everyone [Limitless Esports](https://x.com/lmtless_esports) is now the official prediction market partner for the world's leading esports club, NAVI. https://x.com/natusvincere/status/2065071651591475254
@everyone [Limitless Esports](https://x.com/lmtless_esports) is now the official prediction market partner for the world's leading esports club, NAVI. https://x.com/natusvincere/status/2065071651591475254
You can DM me
You can DM me
I'll put out an announcement when the results are out.
I'll put out an announcement when the results are out.
Season 4 of our points program recently began https://limitless.exchange/blog/points-season-4-announcement Also, if you provide liquidity, look for the diamond by the market, we reward LPs and it details how for each.
Season 4 of our points program recently began https://limitless.exchange/blog/points-season-4-announcement Also, if you provide liquidity, look for the diamond by the market, we reward LPs and it details how for each.
Yes you can stil trade if you've made your picks
Yes you can stil trade if you've made your picks
You can enter
You can enter
I imagine end of day 11th, getting clarification
I imagine end of day 11th, getting clarification
until the 11th
until the 11th
So "Entries close at half-time of the Portugal match - Wed 10 Jun, ~21:30 (Portugal vs Nigeria). Picks lock after that." is for your picks. But you can trade until the deadline. and the challenge goes to the 11th
So "Entries close at half-time of the Portugal match - Wed 10 Jun, ~21:30 (Portugal vs Nigeria). Picks lock after that." is for your picks. But you can trade until the deadline. and the challenge goes to the 11th
<@904767045898469476> You can place the trades any time during the challenge.
<@904767045898469476> You can place the trades any time during the challenge.
Asking about that, I see how that can be interpreted 2 different ways
Asking about that, I see how that can be interpreted 2 different ways
You can trade any packs
You can trade any packs
External wallets are allowed, but rewards will be sent to the linked smart wallet
External wallets are allowed, but rewards will be sent to the linked smart wallet
Looks like no minimum
Looks like no minimum
Cumulative
Cumulative
@everyone The Final Warm-Up is Live $5,000 prize pool. Call the last international friendlies before the World Cup. https://uefa.limitless.exchange
@everyone The Final Warm-Up is Live $5,000 prize pool. Call the last international friendlies before the World Cup. https://uefa.limitless.exchange
Yes, if you want to automate the trading you need to use your external wallet.
Yes, if you want to automate the trading you need to use your external wallet.
There can be a brief amount of time for the new markets to launch.
There can be a brief amount of time for the new markets to launch.
We will launch more categories, I don't have the timeline, but they want to slow roll it out to make sure the experience is perfect.
We will launch more categories, I don't have the timeline, but they want to slow roll it out to make sure the experience is perfect.
Also, we have the new User Generated Markets. 50% of the fees go to the creators of the market, while 50% of the fees are shared wit Liquidity Providers. You can create your own crypto price markets (more coming soon) to earn creator and market maker fees here https://limitless.is/ugm
Also, we have the new User Generated Markets. 50% of the fees go to the creators of the market, while 50% of the fees are shared wit Liquidity Providers. You can create your own crypto price markets (more coming soon) to earn creator and market maker fees here https://limitless.is/ugm
Yes that can factor into it
Yes that can factor into it