PolymarketWill share numbers and change dates when finalized
Will share numbers and change dates when finalized
Danzu参与话题 46消息总数 275
该用户的聊天记录定位。
聊天记录
共 275 条，显示第 201-250 条yes last restart is completing
yes last restart is completing
This is a CLOB release so its independent from that. But checking again on the taker rebates payouts etc
This is a CLOB release so its independent from that. But checking again on the taker rebates payouts etc
1h estimated, multiple releases ([status page](https://status.polymarket.com/))
1h estimated, multiple releases ([status page](https://status.polymarket.com/))
Yes, maintenance ongoing
Yes, maintenance ongoing
**Scheduled CLOB maintenance June 10, between 4:00 and 5:00 AM UTC @here** Release for latency and release-process improvements. **What to expect:** - Intermittent trading during the restart. Orders may not match. - Post-only window after restart (2 min) before normal matching resumes. **Heads-up on rate limits:** we're moving to a new rate limit system. In the next few days, current limits will be reduced ahead of that switch. Exact numbers and timing to come. Flagging now so you can plan. Post-only: only orders explicitly set with postOnly: true and cancels are accepted. Regular limit orders without the flag, market orders, and any taking liquidity will be rejected. See POST /order API reference for the post-only flag. Subscribe to our status page for live updates: https://status.polymarket.com/
**Scheduled CLOB maintenance June 10, between 4:00 and 5:00 AM UTC @here** Release for latency and release-process improvements. **What to expect:** - Intermittent trading during the restart. Orders may not match. - Post-only window after restart (2 min) before normal matching resumes. **Heads-up on rate limits:** we're moving to a new rate limit system. In the next few days, current limits will be reduced ahead of that switch. Exact numbers and timing to come. Flagging now so you can plan. Post-only: only orders explicitly set with postOnly: true and cancels are accepted. Regular limit orders without the flag, market orders, and any taking liquidity will be rejected. See POST /order API reference for the post-only flag. Subscribe to our status page for live updates: https://status.polymarket.com/
checking on this with the team
checking on this with the team
autoredeem being patched rn
autoredeem being patched rn
Update: - A change pushed yesterday should have also alleviated the frequency of the tick size issue, but the problem still remains. Prio1 is latency with the trading team focused first on latency patches. - The team is working on another latency patch. Various spam patterns putting pressure on the gateway. Yesterday's reduction in cancel batch size was to prevent that, but there are other patterns emergenging that they are working on. Will update on the ticksize as soon as the engineers get back to progressing on it
Update: - A change pushed yesterday should have also alleviated the frequency of the tick size issue, but the problem still remains. Prio1 is latency with the trading team focused first on latency patches. - The team is working on another latency patch. Various spam patterns putting pressure on the gateway. Yesterday's reduction in cancel batch size was to prevent that, but there are other patterns emergenging that they are working on. Will update on the ticksize as soon as the engineers get back to progressing on it
Flagging
Flagging
today/tomorrow
today/tomorrow
Team is aware and making some changes
Team is aware and making some changes
Yes I perhaps got confused on the feedback. The shares amount should be the max you can get at that limit price based on your balance
Yes I perhaps got confused on the feedback. The shares amount should be the max you can get at that limit price based on your balance
but in $. I thought as a user you could also want to buy at that price but with your input quantity. E.g I put 1000$ order and click on price level, it switches to market stays at 1000$
but in $. I thought as a user you could also want to buy at that price but with your input quantity. E.g I put 1000$ order and click on price level, it switches to market stays at 1000$
Good feedback, agree overall. It should change to a limit order at that price, with a prefilled normal size
Good feedback, agree overall. It should change to a limit order at that price, with a prefilled normal size
Can you DM with browser console log screenshot when this happens?
Can you DM with browser console log screenshot when this happens?
Thank you for the report, flagged!
Thank you for the report, flagged!
Resolved now
Resolved now
Team is on it, should be fixed by eod Tue
Team is on it, should be fixed by eod Tue
not chain related, new product
not chain related, new product
Should be tomorrow! And if can't Tuesday bundled with a CLOB release
Should be tomorrow! And if can't Tuesday bundled with a CLOB release
Well normally we would do a weekly release instead of 2-3, but we had to find a fix for the latency quickly hence the continuous release process. Also changes in devops and pipeline will help in making the downtime much shorter, and we could then move it to less eventful hours so it affects the least users.
Well normally we would do a weekly release instead of 2-3, but we had to find a fix for the latency quickly hence the continuous release process. Also changes in devops and pipeline will help in making the downtime much shorter, and we could then move it to less eventful hours so it affects the least users.
It's now looking a lot better, and more iterations to do
It's now looking a lot better, and more iterations to do
There are more changes in testing for optimizing stability and latency overall, as well as the tick size error fix I'm checking on ETA for
There are more changes in testing for optimizing stability and latency overall, as well as the tick size error fix I'm checking on ETA for
a lot of spam hitting the matching engine directly. There's now a gateway receiving the requests and handling load better, ensuring matching doesn't get "overloaded" and then causing latency spikes due to it
a lot of spam hitting the matching engine directly. There's now a gateway receiving the requests and handling load better, ensuring matching doesn't get "overloaded" and then causing latency spikes due to it
Yes maintenance in this case means pushing new releases and changes. We have been iterating fast on CLOB changes across ghost fills and latency the last weeks. Unfortunately atm, by design, everytime we push a CLOB change with a release it requires a restart, hence maintenance
Yes maintenance in this case means pushing new releases and changes. We have been iterating fast on CLOB changes across ghost fills and latency the last weeks. Unfortunately atm, by design, everytime we push a CLOB change with a release it requires a restart, hence maintenance
<@1401963406193328168> knows, will reconfirm
<@1401963406193328168> knows, will reconfirm
Actually scaled the team recently and very senior hires from Aave, Chainlink etc. Some tech debt remaining but almost covered.
Actually scaled the team recently and very senior hires from Aave, Chainlink etc. Some tech debt remaining but almost covered.
<a:peepocandle:754850445263896647>
<a:peepocandle:754850445263896647>
Have some faith 🕯️
Have some faith 🕯️
You said this last time before the latest latency update
You said this last time before the latest latency update
No actually, the new deposit wallet version is delayed to [11th](https://x.com/PolymarketDevs/status/2063044968633995576), will mention on Discord too for clarity. Today nothing was pushed, load spike and an autoscaling issue which caused the situation.
No actually, the new deposit wallet version is delayed to [11th](https://x.com/PolymarketDevs/status/2063044968633995576), will mention on Discord too for clarity. Today nothing was pushed, load spike and an autoscaling issue which caused the situation.
The issue was fixed, ping if you see anything odd again. Sorry for that
The issue was fixed, ping if you see anything odd again. Sorry for that
Latency was more important than anything.
Latency was more important than anything.
It should be solved before wc don’t worry
It should be solved before wc don’t worry
Reported internally
Reported internally
Tick size bug is being worked on. Latency reduction was more important and that release caused increased tick size issue. Esports is a separate team shipping it..
Tick size bug is being worked on. Latency reduction was more important and that release caused increased tick size issue. Esports is a separate team shipping it..
I don’t think these are ghost fills, it must be a confusion with other order submission issues. Please dm any specific transaction or address log we can dig deeper in
I don’t think these are ghost fills, it must be a confusion with other order submission issues. Please dm any specific transaction or address log we can dig deeper in
No sir sorry, should get tomorrow. The fix ideally will be next week, will confirm on timeline/approach
No sir sorry, should get tomorrow. The fix ideally will be next week, will confirm on timeline/approach
Checking internally
Checking internally
Both this and the phantom order cancellation issues are with the team and being worked on
Both this and the phantom order cancellation issues are with the team and being worked on
It was tested last release but it was causing slight latency regression so it's being worked on further
It was tested last release but it was causing slight latency regression so it's being worked on further
Team is aware and fix is planned for it guys
Team is aware and fix is planned for it guys
Re-checking internally, I was told today
Re-checking internally, I was told today
No, this is a clob release. Taker tier is independent of that.
No, this is a clob release. Taker tier is independent of that.
up/down 5min
up/down 5min
Maintenance done, trading is back up
Maintenance done, trading is back up
The CLOB didn't restart yet, it's in pipeline
The CLOB didn't restart yet, it's in pipeline
This release should help especially with crypto 5min markets.
This release should help especially with crypto 5min markets.
Means we didn't communicate here as I wasn't around, but the team has been on this already.
Means we didn't communicate here as I wasn't around, but the team has been on this already.