Polymarketyes，the Polymarket team needs to focus on fixing ghost orders rather than scrapping liquidity rewards.
yes，the Polymarket team needs to focus on fixing ghost orders rather than scrapping liquidity rewards.
PPLOVE参与话题 4消息总数 21
该用户的聊天记录定位。
聊天记录
共 21 条，显示第 1-21 条This exploit is the core problem. We’ve never had bot loopholes this severe before.
This exploit is the core problem. We’ve never had bot loopholes this severe before.
The weather prediction markets have turned extremely bleak ever since liquidity rewards were scrapped
The weather prediction markets have turned extremely bleak ever since liquidity rewards were scrapped
The market has turned extremely dismal now that liquidity rewards are gone. Fixing ghost orders should be our top priority. Bad actors must not be allowed to exploit loopholes to earn risk-free rewards, which prevents genuine traders from conducting normal transactions.
The market has turned extremely dismal now that liquidity rewards are gone. Fixing ghost orders should be our top priority. Bad actors must not be allowed to exploit loopholes to earn risk-free rewards, which prevents genuine traders from conducting normal transactions.
ok thanks
ok thanks
<@930737463163494430> Since yesterday, the automatic redemption function seems to have encountered some issues. Previously, when a market closed, auto-redemption would typically complete within 1–2 minutes. However, now it takes half an hour or even several hours to auto-redeem. We kindly request that the technical team look into this issue. thanks！
<@930737463163494430> Since yesterday, the automatic redemption function seems to have encountered some issues. Previously, when a market closed, auto-redemption would typically complete within 1–2 minutes. However, now it takes half an hour or even several hours to auto-redeem. We kindly request that the technical team look into this issue. thanks！
thank
thank
What I am referring to is likely a phantom order issue—fake orders appearing on the order book that simply cannot be executed, while their creators are still able to collect liquidity rewards and maker rebates.
What I am referring to is likely a phantom order issue—fake orders appearing on the order book that simply cannot be executed, while their creators are still able to collect liquidity rewards and maker rebates.
<@930737463163494430> Hello, could you please forward the issues I mentioned to the technical team?
<@930737463163494430> Hello, could you please forward the issues I mentioned to the technical team?
Users of the weather market speculate that these are fake orders or phantom orders, and they request that the technical team verify this.
Users of the weather market speculate that these are fake orders or phantom orders, and they request that the technical team verify this.
Is this what people refer to as "fake orders" or "phantom orders"?
Is this what people refer to as "fake orders" or "phantom orders"?
Recently, an issue has emerged in the weather prediction market: the ask price has been consistently displayed on the web, but when you place a limit order at the bid price to try to match it, the order inexplicably disappears, causing your attempt to execute a marketable limit order to become a resting order instead. I am aware that there used to be high-frequency bots placing and canceling orders, yet you could still get filled by placing limit orders—about 50–60% of 10 orders would go through, since those high-frequency cancellations and placements occurred at a certain frequency. However, in the past few days, these high-frequency ask orders have become untouchable; you can only watch them, and once you place an order, it simply cannot be executed against them. I am wondering whether there has been a recent system update that caused this issue, or whether it is a bug in the order matching engine. This problem has occurred dozens of times in just the past few days, and it has not been noticed by just one or two users. We kindly request that the technical team look into this issue. Has the frequency limit for order placement and cancellation been adjusted, resulting in the current placement/cancellation rate far exceeding previous levels? Or could there be a latency bug in the order matching system that allows the resting order party to monitor whether someone is trying to take their order and cancel it in advance?
Recently, an issue has emerged in the weather prediction market: the ask price has been consistently displayed on the web, but when you place a limit order at the bid price to try to match it, the order inexplicably disappears, causing your attempt to execute a marketable limit order to become a resting order instead. I am aware that there used to be high-frequency bots placing and canceling orders, yet you could still get filled by placing limit orders—about 50–60% of 10 orders would go through, since those high-frequency cancellations and placements occurred at a certain frequency. However, in the past few days, these high-frequency ask orders have become untouchable; you can only watch them, and once you place an order, it simply cannot be executed against them. I am wondering whether there has been a recent system update that caused this issue, or whether it is a bug in the order matching engine. This problem has occurred dozens of times in just the past few days, and it has not been noticed by just one or two users. We kindly request that the technical team look into this issue. Has the frequency limit for order placement and cancellation been adjusted, resulting in the current placement/cancellation rate far exceeding previous levels? Or could there be a latency bug in the order matching system that allows the resting order party to monitor whether someone is trying to take their order and cancel it in advance?
Has the frequency limit for order placement and cancellation been adjusted, resulting in the current placement/cancellation rate far exceeding previous levels? Or could there be a latency bug in the order matching system that allows the resting order party to monitor whether someone is trying to take their order and cancel it in advance?
Has the frequency limit for order placement and cancellation been adjusted, resulting in the current placement/cancellation rate far exceeding previous levels? Or could there be a latency bug in the order matching system that allows the resting order party to monitor whether someone is trying to take their order and cancel it in advance?
Recently, an issue has emerged in the weather prediction market: the ask price has been consistently displayed on the web, but when you place a limit order at the bid price to try to match it, the order inexplicably disappears, causing your attempt to execute a marketable limit order to become a resting order instead. I am aware that there used to be high-frequency bots placing and canceling orders, yet you could still get filled by placing limit orders—about 50–60% of 10 orders would go through, since those high-frequency cancellations and placements occurred at a certain frequency. However, in the past few days, these high-frequency ask orders have become untouchable; you can only watch them, and once you place an order, it simply cannot be executed against them. I am wondering whether there has been a recent system update that caused this issue, or whether it is a bug in the order matching engine. This problem has occurred dozens of times in just the past few days, and it has not been noticed by just one or two users. We kindly request that the technical team look into this issue.
Recently, an issue has emerged in the weather prediction market: the ask price has been consistently displayed on the web, but when you place a limit order at the bid price to try to match it, the order inexplicably disappears, causing your attempt to execute a marketable limit order to become a resting order instead. I am aware that there used to be high-frequency bots placing and canceling orders, yet you could still get filled by placing limit orders—about 50–60% of 10 orders would go through, since those high-frequency cancellations and placements occurred at a certain frequency. However, in the past few days, these high-frequency ask orders have become untouchable; you can only watch them, and once you place an order, it simply cannot be executed against them. I am wondering whether there has been a recent system update that caused this issue, or whether it is a bug in the order matching engine. This problem has occurred dozens of times in just the past few days, and it has not been noticed by just one or two users. We kindly request that the technical team look into this issue.
Me too
Me too
thanks
thanks
thanks
thanks
I didn't know this would happen, and I already deposited $200 into my account. Now I can't withdraw or trade. What should I do?
I didn't know this would happen, and I already deposited $200 into my account. Now I can't withdraw or trade. What should I do?
I didn't know this would happen, and I already deposited $200 into my account. Now I can't withdraw or trade. What should I do?
I didn't know this would happen, and I already deposited $200 into my account. Now I can't withdraw or trade. What should I do?
Has anyone else encountered this issue today when registering a Polymarket account with MetaMask? It shows: Done Approve Tokens Approve token spending for trading Try Again! Error: {"error":"request error","status":400,"statusText":"","data":{"error":"wallet registry validation failed: wallet 0x33E16c51E18703471578a394D6998bD61e2442CA is not registered"}} As a result, I cannot trade, and the balance I deposited into my account cannot be withdrawn either.
Has anyone else encountered this issue today when registering a Polymarket account with MetaMask? It shows: Done Approve Tokens Approve token spending for trading Try Again! Error: {"error":"request error","status":400,"statusText":"","data":{"error":"wallet registry validation failed: wallet 0x33E16c51E18703471578a394D6998bD61e2442CA is not registered"}} As a result, I cannot trade, and the balance I deposited into my account cannot be withdrawn either.
Has anyone else encountered this issue today when registering a Polymarket account with MetaMask? It shows: Done Approve Tokens Approve token spending for trading Try Again! Error: {"error":"request error","status":400,"statusText":"","data":{"error":"wallet registry validation failed: wallet 0x33E16c51E18703471578a394D6998bD61e2442CA is not registered"}} As a result, I cannot trade, and the balance I deposited into my account cannot be withdrawn either.
Has anyone else encountered this issue today when registering a Polymarket account with MetaMask? It shows: Done Approve Tokens Approve token spending for trading Try Again! Error: {"error":"request error","status":400,"statusText":"","data":{"error":"wallet registry validation failed: wallet 0x33E16c51E18703471578a394D6998bD61e2442CA is not registered"}} As a result, I cannot trade, and the balance I deposited into my account cannot be withdrawn either.