Hi stackers,
We’ve just brought native Central Limit Order Book (CLOB) trading to sports markets on Predyx. Now we’re rolling it out with NFL, soccer, and other sports.
The idea is pretty simple — instead of an AMM setting the price, traders can place limit orders and trade against each other directly.
We’re planning to have at least one NFL game market every day throughout the NFL season, alongside soccer markets from some of the major leagues and a few other popular sports.
Here are a couple of the first markets:
Real Madrid vs Inter Milan:
https://beta.predyx.com/market/real-madrid-vs-inter-milan-sep-8-1788888386
Seattle Seahawks vs New England Patriots:
https://beta.predyx.com/market/seattle-seahawks-vs-new-england-patriots-sep-10-1788887308
TBH, it’s still early, so we’re less interested in pitching the feature and more interested in hearing what you think. Any feedback on the CLOB or the overall sports trading experience is much appreciated.
A few specific questions:
- How would you rate your overall Predyx experience so far?
- What’s the biggest pain point when using Predyx?
- What’s the one thing you’d most like us to build or improve next?
Even a one-line answer is useful. We’re trying to figure out what to build next, and actual user feedback is probably more valuable than another internal discussion.
Looking forward to hearing your thoughts and suggestions.
@Coinsreporter @grayruby @BlokchainB @Undisciplined @OT @Wumbo @south_korea_ln @SimpleStacker @ACYK @softglitter2d @ken @DarkStacker @itsTomekK @needcreations_
@Solomonsatoshi @afpsniper88
@kepford @Cje95 @Jer @denlillaapan @gsc360
The low trading volume and added complexity makes these markets tough.
Leaving standing orders isn't very attractive for a few reasons:
I'd recommend trying out a hybrid model, where limit orders can be placed in markets that have an underlying low liquidity market maker.
Thank you.
We understand all these trade-offs. However this is mostly due to the link w trading volume, or less traders participation.
We just implemented it to be future ready. We already have hybrid model, we tested it earlier but it is not as efficient as either of LMSR and CLOB.
In future we will rollout liquidity farming to solve the issue of low liquidity on CLOB.
I think there are some different UI choices that might be more appealing to general (i.e. non-trader) users.
For instance, instead of just having people set their limit orders, frame it as "How likely do you think this is?" and "How much are you willing to bet on that?"
I like the feed with the days games and then you can click and make a prediction. Cool idea.
Thank you so much.
We'll be doing a lot more such cool things very soon.
Liquidity; more people.
We can't win big unless we have more fish to scalp, hashtag mixing metaphors. The BIPtard contracts were so great because there were plenty of idiot bettors around we could profit off.
Every other (non-sports) contract is too low liquidity to do anything much with :/
GROWTH, GROWTH! BRING MORE PEEPS
Thank you.
#1573399
Yes I agree , many contracts are low liquidity, the good thing about them, most are user created, which is empowering.
However we're going to implement liquidity injection on-flight markets very soon.
What about a “yield” product for users that acts like counterparty on markets ?
Cool!!
Not CLOB feedback but a security heads-up from poking at the beta, since I figured you would want to know before it grows.
Your public, unauthenticated markets endpoint (GET /api/markets) returns each market creator object with its full roles array and internal user _id. So anyone can enumerate it and immediately see which accounts are privileged — right now it exposes a creator test456 with roles ["USER","ADMIN","SUPERADMIN"], plus several SUPPORT / TRUSTED_CREATOR accounts, and raw Google googleusercontent avatar URLs for some. Publishing who holds admin/superadmin is a gift to anyone planning credential-stuffing or phishing — they now know exactly which handles to target. I would drop roles and _id from the public creator projection (return just username + reliabilityScore), and proxy avatars instead of leaking the Google URL.
Smaller, lower confidence: the frontend config ships VUE_DEFAULT_BUY_FEE=0.0045 and VUE_DEFAULT_SELL_FEE=0.0035, but the live per-market fees object is buy 0.0035 / sell 0.0045 — the two defaults look swapped relative to the real values. Harmless if those constants are never used as a fallback, but worth a grep in case a market ever renders without its fees and quotes the wrong side.
Happy to send repro details privately. Nice work on the CLOB rollout.