聊天记录
共 275 条，显示第 1-50 条
**Scheduled trading maintenance Sunday Jul 12, 6 - 7 AM UTC @here**
We are releasing a patch for order fill edge cases and improving consistency across matching and order state.
What to expect:
- Trading intermittent for up to ~1 hour. Maintenance starts at ~06:00 UTC.
- Brief post-only window after restart (2 min) before normal matching resumes. Cancels accepted.
Post-only: only orders explicitly set with postOnly: true are accepted. Regular limit orders without the flag, market orders, and any taking liquidity will be rejected. Cancels for existing orders will still go through.
**Scheduled trading maintenance Sunday Jul 12, 6 - 7 AM UTC @here**
We are releasing a patch for order fill edge cases and improving consistency across matching and order state.
What to expect:
- Trading intermittent for up to ~1 hour. Maintenance starts at ~06:00 UTC.
- Brief post-only window after restart (2 min) before normal matching resumes. Cancels accepted.
Post-only: only orders explicitly set with postOnly: true are accepted. Regular limit orders without the flag, market orders, and any taking liquidity will be rejected. Cancels for existing orders will still go through.
Yes, it was up a while back but team was monitoring
Yes, it was up a while back but team was monitoring
Can you DM your address?
Can you DM your address?
**Scheduled trading maintenance Fri Jul 10, 04:00 – 05:00 UTC @here**
What to expect:
- Trading intermittent for up to ~1 hour during the window. Orders won't match.
- Post-only window after restart (2 min) before normal matching resumes.
Post-only: only orders explicitly set with postOnly: true and cancellation of open orders are accepted. Regular limit orders without the flag, market orders, and any taking liquidity will be rejected.
Subscribe to our status page for live updates: https://status.polymarket.com/
**Scheduled trading maintenance Fri Jul 10, 04:00 – 05:00 UTC @here**
What to expect:
- Trading intermittent for up to ~1 hour during the window. Orders won't match.
- Post-only window after restart (2 min) before normal matching resumes.
Post-only: only orders explicitly set with postOnly: true and cancellation of open orders are accepted. Regular limit orders without the flag, market orders, and any taking liquidity will be rejected.
Subscribe to our status page for live updates: https://status.polymarket.com/
**Scheduled maintenance - Thursday, July 9, 09:00–12:00 UTC**
We're running a planned database upgrade tomorrow. Trading works as normal, no downtime expected.
Heads up during the window: **Rewards, Referrals, and Notifications may temporarily show stale data**. This resolves automatically once we're done, no action needed. Funds and positions are not affected.
**Scheduled maintenance - Thursday, July 9, 09:00–12:00 UTC**
We're running a planned database upgrade tomorrow. Trading works as normal, no downtime expected.
Heads up during the window: **Rewards, Referrals, and Notifications may temporarily show stale data**. This resolves automatically once we're done, no action needed. Funds and positions are not affected.
https://klipy.com/gifs/embarrassed-kid-2
https://klipy.com/gifs/embarrassed-kid-2
Also fyi guys, this was a third party dependency, not a release regression or related issue.
Also fyi guys, this was a third party dependency, not a release regression or related issue.
Wow I take this personally
Wow I take this personally
Things are normalizing, but still investigating
Things are normalizing, but still investigating
Team is on it, will update guys
Team is on it, will update guys
This release is on gateway for the expiration change and connected to the fake fill issue.
There's an upcoming latency-focused release, will give ETA as soon as testing is done
This release is on gateway for the expiration change and connected to the fake fill issue.
There's an upcoming latency-focused release, will give ETA as soon as testing is done
Heads up: We're performing scheduled maintenance today at 8pm ET for up to 30 minutes. No downtime is expected and trading should continue as normal, but there may be brief instability during this window.
[Status Page](https://status.polymarket.com/)
Heads up: We're performing scheduled maintenance today at 8pm ET for up to 30 minutes. No downtime is expected and trading should continue as normal, but there may be brief instability during this window.
[Status Page](https://status.polymarket.com/)
Seems so. I am gathering context from eng as they test the solutions
Seems so. I am gathering context from eng as they test the solutions
I remember coinbase fully down everytime I wanted to sell BTC during pumps
I remember coinbase fully down everytime I wanted to sell BTC during pumps
RTDS issues are mainly spam related. The team is working through solutions but no ETA till tested etc.
RTDS issues are mainly spam related. The team is working through solutions but no ETA till tested etc.
not yet
not yet
Hey guys, sorry wasn't around. RTDS work in progress, no ETA until the fixes are tested
Hey guys, sorry wasn't around. RTDS work in progress, no ETA until the fixes are tested
checking
checking
This is frontend-specific, in the logic of how CLOB API keys are cycled. The team is working on it now. If you are affected it's because the frontend is showing open orders for your new API key which got created, instead of the old one
This is frontend-specific, in the logic of how CLOB API keys are cycled. The team is working on it now. If you are affected it's because the frontend is showing open orders for your new API key which got created, instead of the old one
Do you still see elevated latency? It seemed transient during patch
Do you still see elevated latency? It seemed transient during patch
It should be fixed now
It should be fixed now
Should be fixed in ~3min, deploying
Should be fixed in ~3min, deploying
Yes, team is already on it, will revert shortly
Yes, team is already on it, will revert shortly
Flagged to the team again
Flagged to the team again
A patch for this was just pushed, you should be able to trade
A patch for this was just pushed, you should be able to trade
Please DM your account address, will help check logs
Please DM your account address, will help check logs
There is ongoing analysis and some UI improvements in the work before .25c are introduced to other games fyi, so depending on that we will announce and proceed.
Happy to omit *potentially*, fact is it will be announced upfront correctly, and status can be fetched from gamma.
There is ongoing analysis and some UI improvements in the work before .25c are introduced to other games fyi, so depending on that we will announce and proceed.
Happy to omit *potentially*, fact is it will be announced upfront correctly, and status can be fetched from gamma.
@here following up on this: we tested 0.25c tick sizes yesterday. Today's games stay at 1c.
We'll announce when 0.25c goes live for the rest of the World Cup games, potentially starting tomorrow.
@here following up on this: we tested 0.25c tick sizes yesterday. Today's games stay at 1c.
We'll announce when 0.25c goes live for the rest of the World Cup games, potentially starting tomorrow.
Sorry. Getting some clarity internally and will revert
Sorry. Getting some clarity internally and will revert
Dm address please, we’ll check
Dm address please, we’ll check
perps or prediction? Which error is shown?
perps or prediction? Which error is shown?
The cashout would disappear only once all the legs are resolved. That's when you can redeem if all legs hit.
Atm the top game is still to be played. Cashout depends on offers from makers, there might be no quote available to sell this combo until it completes.
The cashout would disappear only once all the legs are resolved. That's when you can redeem if all legs hit.
Atm the top game is still to be played. Cashout depends on offers from makers, there might be no quote available to sell this combo until it completes.
Regulations
Regulations
This was done only for today's market and will be expanded onwards based on results
This was done only for today's market and will be expanded onwards based on results
came here to say this, too slow
came here to say this, too slow
lol, I was saying that it's all quite automated and the flow is structured, but there are some conditions that cause payout/calculation schedule issues at times. There's an active eng work stream to refactor and unify all of the rebates/rewards systems to minimize those.
lol, I was saying that it's all quite automated and the flow is structured, but there are some conditions that cause payout/calculation schedule issues at times. There's an active eng work stream to refactor and unify all of the rebates/rewards systems to minimize those.
Fyi, yesterday's maker rebates will be paid out today. Will ping when payout is done.
Fyi, yesterday's maker rebates will be paid out today. Will ping when payout is done.
all the eggplants
all the eggplants
All is being seen. Discussing internally
All is being seen. Discussing internally
Team is aware. This is how the program has been structured. We should have an update today on how to prevent and adjust this
Team is aware. This is how the program has been structured. We should have an update today on how to prevent and adjust this
metamask big number problem, any
metamask big number problem, any
Yes will get these up, I know they were reviewing them.
Yes will get these up, I know they were reviewing them.
__Update on a variety of topics, issues and upcoming fixes__
**Latency**
- Spam contributed to latency spikes, the upcoming tiered rate limit system, as well as a release on async processing improvement will help reduce latency
- Crypto-market cancel latency is still rough, the above should help but crypto markets are the hardest to reduce latency on
**Rate limit tiers (live tomorrow, 12-1am ET)**
- Tomorrow is observation only, no rate limits are being changed
- The system for introducing rate limit tiers is the only thing being released. You will have heads up and details before rate limit changes go into effect.
- The tiers will be per-wallet, with orders and cancels in separate buckets, so order spam won't choke your cancels. Per-market limits aren't technically doable yet.
**
Queuing tiebreak / cancellation fixes**
- The June 24 release fixed cases in which under load, the in-memory order book and DB could drift apart causing stale cancellation states. There are still edge cases around this that are being actively worked on.
- Subsequent release fixed a salt exploit where salt was being used as a tiebreak during matching for orders within the same timestamp granularity. Granularity was increased to prevent this.
**Ghost fills**
- There were multiple report of ghost fills last week. A couple cases weren’t covered, but primarily driven by the automated banning having some edge cases and not processing those bans
- Reminder: deposit wallets were built to kill ghost-fill paths, but they can still occur in old wallets, which are then banned permanently
__Update on a variety of topics, issues and upcoming fixes__
**Latency**
- Spam contributed to latency spikes, the upcoming tiered rate limit system, as well as a release on async processing improvement will help reduce latency
- Crypto-market cancel latency is still rough, the above should help but crypto markets are the hardest to reduce latency on
**Rate limit tiers (live tomorrow, 12-1am ET)**
- Tomorrow is observation only, no rate limits are being changed
- The system for introducing rate limit tiers is the only thing being released. You will have heads up and details before rate limit changes go into effect.
- The tiers will be per-wallet, with orders and cancels in separate buckets, so order spam won't choke your cancels. Per-market limits aren't technically doable yet.
**
Queuing tiebreak / cancellation fixes**
- The June 24 release fixed cases in which under load, the in-memory order book and DB could drift apart causing stale cancellation states. There are still edge cases around this that are being actively worked on.
- Subsequent release fixed a salt exploit where salt was being used as a tiebreak during matching for orders within the same timestamp granularity. Granularity was increased to prevent this.
**Ghost fills**
- There were multiple report of ghost fills last week. A couple cases weren’t covered, but primarily driven by the automated banning having some edge cases and not processing those bans
- Reminder: deposit wallets were built to kill ghost-fill paths, but they can still occur in old wallets, which are then banned permanently
oh no, my bad. I meant before we even introduce the tiers we will have a flag to know when you would theoretically be at limit. Atm internally there are no final draft numbers yet
oh no, my bad. I meant before we even introduce the tiers we will have a flag to know when you would theoretically be at limit. Atm internally there are no final draft numbers yet
Writing a broader update on the topics you guys asked for. No rate limit changes, just adding the system for it today. We will notify of new rate limit numbers and launch date ahead of time ofc
Writing a broader update on the topics you guys asked for. No rate limit changes, just adding the system for it today. We will notify of new rate limit numbers and launch date ahead of time ofc
DM address, taking a look
DM address, taking a look
**__Scheduled Maintenance windows - Wednesday, July 1__** @here
**Trading Release (12:00 AM – 1:00 AM ET)**
The new tiered rate limit system will be introduced for observation. Tiers will be tested and makers will be flagged when they would be crossing the upcoming new limits. Final tiered limits and launch date TBD.
What to expect:
Trading intermittent for up to ~1 hour during the window. Orders may not match.
Post-only window after restart (2 min) before normal matching resumes.
-------------------
**Backfill for Position-Data Correction (7:00 AM – 11:00 AM ET)**
Some incorrect position data is being backfilled and may cause stale positions for 10–15 minutes for users over the maintenance window. Trading is unaffected.
**__Scheduled Maintenance windows - Wednesday, July 1__** @here
**Trading Release (12:00 AM – 1:00 AM ET)**
The new tiered rate limit system will be introduced for observation. Tiers will be tested and makers will be flagged when they would be crossing the upcoming new limits. Final tiered limits and launch date TBD.
What to expect:
Trading intermittent for up to ~1 hour during the window. Orders may not match.
Post-only window after restart (2 min) before normal matching resumes.
-------------------
**Backfill for Position-Data Correction (7:00 AM – 11:00 AM ET)**
Some incorrect position data is being backfilled and may cause stale positions for 10–15 minutes for users over the maintenance window. Trading is unaffected.
DM me with any console error log for this please
DM me with any console error log for this please
This is known. Resting limit orders can be also not filled and cancelled. The fix are maker rebates which are on fills, and reducing traditional LP incentives
This is known. Resting limit orders can be also not filled and cancelled. The fix are maker rebates which are on fills, and reducing traditional LP incentives
Team is aware of the latency, will report as soon as I have updates
Team is aware of the latency, will report as soon as I have updates
Polymarket