BTC $69,272.25 -6.02%
ETH $1,959.06 -4.46%
BNB $637.57 -6.01%
XRP $1.01 -2.91%
SOL $79.11 -4.71%
TRX $0.3142 -0.88%
DOGE $0.0641 -4.51%
ADA $0.1685 -2.66%
BCH $218.62 -4.66%
LINK $9.76 -3.39%
HYPE $71.86 -0.28%
AAVE $111.34 -6.36%
SUI $0.7804 -4.60%
XLM $0.1429 -2.38%
ZEC $929.53 -5.64%
AAPL $357.10 +0.32%
AMZN $268.20 +0.75%
GOOGL $300.92 +2.02%
MSFT $522.51 +0.16%
META $625.52 -0.86%
NVDA $163.94 +1.90%
TSLA $398.70 +3.03%
SNDK $931.88 -2.80%
INTC $61.12 +0.49%
SPCX $140.71 +0.77%
MU $798.73 +0.84%
AMD $577.66 +2.23%
BTC $69,272.25 -6.02%
ETH $1,959.06 -4.46%
BNB $637.57 -6.01%
XRP $1.01 -2.91%
SOL $79.11 -4.71%
TRX $0.3142 -0.88%
DOGE $0.0641 -4.51%
ADA $0.1685 -2.66%
BCH $218.62 -4.66%
LINK $9.76 -3.39%
HYPE $71.86 -0.28%
AAVE $111.34 -6.36%
SUI $0.7804 -4.60%
XLM $0.1429 -2.38%
ZEC $929.53 -5.64%
AAPL $357.10 +0.32%
AMZN $268.20 +0.75%
GOOGL $300.92 +2.02%
MSFT $522.51 +0.16%
META $625.52 -0.86%
NVDA $163.94 +1.90%
TSLA $398.70 +3.03%
SNDK $931.88 -2.80%
INTC $61.12 +0.49%
SPCX $140.71 +0.77%
MU $798.73 +0.84%
AMD $577.66 +2.23%

compensation

All
Article
Flash

SignalPlus: The network attack originated from a third-party Telegram account being hacked, resulting in a loss of less than $82,000, and full compensation will be provided

The cryptocurrency derivatives trading tool platform SignalPlus announced that it was attacked in the early hours of November 4, originating from a third-party Telegram account that was hacked, affecting a small number of accounts that had not enabled IP whitelisting.The team stated that they quickly identified and controlled the intrusion. As a precautionary measure, they have revoked all associated API keys with their centralized trading platform partners and temporarily suspended terminal services. The official statement indicated that the total loss was less than $82,000, and affected users will receive full compensation. They expect to fully restore services in the coming days, with subsequent updates and operational guidelines to be released through official channels.This evening, Binance also issued a statement indicating that it has taken precautionary measures regarding the potential security issues reported by the third-party platform SignalPlus, actively revoking all API keys associated with SignalPlus.Binance emphasized that its own system was not affected and that user funds are secure. Binance reminded SignalPlus users to log directly into their Binance accounts to check their positions and open orders, and not to rebind API keys until the issues with SignalPlus are completely resolved. They also advised to always enable IP whitelisting.

first_img Binance: The compensation ratio for stolen assets has increased to 90%, and withdrawals are still planned to resume on Sunday

Binance released a security incident update stating that the company had previously reserved over $6.34 billion of company funds to cover the stolen losses, with the coverage ratio at that time being approximately 80%, which has now increased to 90%. BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC have achieved 100% coverage, while the remaining related tokens will continue to be purchased through market and over-the-counter channels until the coverage ratio for all tokens reaches 100%. Binance stated that the financial impact of the stolen funds will be borne by the platform, not the users.The replenished funds come from a partial drawdown of the user security asset fund SAFU, a portion of the contract insurance fund, and Binance's company funds. The partial drawdown of SAFU is expected to occur within the next 24 hours. The remaining 10% consists of assets outside the aforementioned ten tokens with lower liquidity, and the time required for purchase may be longer.Binance completed a new reserve proof snapshot on October 31 at 00:00 (UTC) and updated it on the reserve proof page. The complete zero-knowledge proof is expected to take 40 to 50 hours to generate, approximately by November 3 (UTC). Withdrawal services will continue to progress according to the previous schedule, with plans to reopen on Sunday, November 1.Binance introduced that SAFU was established in July 2018 and is held and managed by Nest Clearing and Custody Limited, regulated by the Abu Dhabi Global Market Financial Services Regulatory Authority. The company commits to replenishing the scale of SAFU to approximately $1 billion and clarifies that the partial drawdown of SAFU is for purchasing the remaining 10% of assets. After withdrawing the balance exceeding the stipulated level, the contract insurance fund remains above the coverage level required by the existing risk management framework; if the balance falls below the requirement, Binance will make up the difference with company funds.

first_img User daN’SKi: Polymarket requires a signed agreement to refund funds

On October 30, X user daN'SKi (@TheNotoriousSKi) posted that the prediction market platform Polymarket requires users affected by its so-called security incident to disclose personal identification information and sign a legally binding contract before their funds will be returned. The post stated that this requirement contradicts the platform's previous claim that all affected users would receive full compensation and questioned its legality. The post included multiple screenshots of documents, with the text on the pages showing a sample settlement and release agreement.On October 29, Polymarket stated on X that a third-party service provider of its international platform Polymarket.com had been breached, the issue has been identified and resolved, and the incident has been referred to the relevant law enforcement agencies, with affected users set to receive full compensation. The platform had suspended trading but later announced that trading had fully resumed and stated that it would fully compensate all affected traders. According to CNBC, Polymarket informed users on Discord that funds with losses below $10,000 would be restored by October 30, while users with losses above that amount would need to sign a waiver agreement to receive compensation.CNBC cited data analysis from Betting Intelligence and Polysights, stating that on that day, one account withdrew at least $2.7 million from 710 wallets. Sources told CNBC that the issue stemmed from the website performance monitoring service DebugBear being breached, and Polymarket has referred the incident to UK law enforcement. The Polymarket US platform was not affected by this incident. In June of this year, Polymarket also stated that a third-party vendor had been breached and promised refunds to affected users.

first_img Backbone Labs bOSMO contract vulnerability leads to support exhaustion, Osmosis announces compensation plan

The liquid staking token bOSMO issued by Backbone Labs nearly exhausted its contract support after a large redemption in the Osmosis community pool. A disclosure on the Osmosis forum on October 15 revealed that approximately 40,508 OSMO were designated for compensation to 1,037 accounts. The disclosure author Johnny Wyles stated that the staking contract has overpaid for each redemption since at least April 2026, settling at approximately 1.676 OSMO per bOSMO, while the declared exchange rate of the contract was about 1.117 OSMO.The vulnerability repeatedly counted the OSMO staked on Backbone's own validators, allowing redeemers to receive about 50% more assets, at the cost of diluting the support for remaining holders. The defect was exposed when preparing to liquidate the community pool position, and the passed governance proposal 1049 authorized the withdrawal of the Margined managed treasury position and the destruction of the reclaimed OSMO when it ceased managing liquidity operations. The pool's bOSMO treasury holds approximately 1.137 million bOSMO, accounting for about 97% of the total supply of the token; the redemption transaction executed on October 9 at 21:59 ET destroyed 776,000 bOSMO and began unbinding approximately 1.3 million OSMO.Compensation is based on the qualified balance at block 72,237,940, calculated at 1.1174 OSMO per bOSMO. bOSMO purchased after the snapshot is not included in the compensation, and underlying holders in the liquidity pool and other contracts are also included;

Ostium announced the second phase of the compensation plan: providing two methods of payment in installments with USDC and equity conversion

Ostium has released a design update on the second phase of the compensation plan for liquidity providers (OLP). This plan offers two compensation mechanisms for users who have losses exceeding 1,000 USDC and have not opted for Convenience Allocation:Default Plan A (USDC Installment Payment): Funding sources include recovered and future recovered funds (distributed proportionally after deducting the first phase portion), a specific share of revenue from the Ostium protocol and Gateway (initially 50% of Ostium opening fees), and potential partner incentives or revenue sharing.Optional Plan B (Ostium Labs Equity Conversion): Users who meet securities regulation requirements can convert part of their unrecovered losses into Ostium Labs equity at the valuation of the next round of financing, with the same class of shares as the team, and a total holding percentage for participating users subject to a fully diluted cap.The second phase portal is scheduled to launch on October 30, and eligible users can proportionally claim the allocated funds from Plan A; if they choose equity conversion, the portion of losses converted to equity will no longer be eligible for subsequent installment payments under Plan A, thereby helping to accelerate the repayment process for the remaining unconverted funds.Ostium emphasizes that this compensation plan is voluntarily initiated by the official and does not guarantee the full recovery of lost funds; specific implementation details and parameter scales are still being refined.

Drift's compensation plan has caused dissatisfaction, with a loss of about 1 dollar for every 100 dollars

The perpetual contract protocol Drift (now Velocity) Foundation has opened claims and redemptions for the security incident on April 1. Affected users can claim newly issued compensation tokens DFX at a rate of 1 DFX for every $1 of verified loss. DFX is a Solana standard SPL asset, with a fixed total supply of approximately 299.5 million tokens, corresponding to about $295.4 million in verified losses, and no further issuance will occur.Users can destroy DFX on the official portal and redeem it for USDT at the redemption price, or trade it on secondary markets like Raydium. The redemption price is determined by the balance of the recovery pool divided by the number of DFX tokens that have not yet been destroyed. Currently, there are about 3.11 million USDT in the pool, with a redemption price of approximately $0.0104, allowing for about $1 back for every $100 lost, covering about 1% of the losses, which has caused dissatisfaction in the community, believing there is a significant gap from the expected full compensation.The plan also includes a maximum support commitment of $127.5 million from Tether, up to $20 million from partners, as well as subsequent sources such as transaction fee sharing from the new trading platform Velocity and the recovery of stolen funds, most of which are upper limits or installment arrangements, and were not included in the pool on the opening day. After the DFX launch, the redemption price remains around $0.0104, while the secondary market trading price has risen from about $0.01 to approximately $0.03, with a 24-hour increase of about 210%, and liquidity at that time was around $200,000. The tokens can be freely transferred, and the trading price does not have to equal the redemption price; buyers are mainly concerned with subsequent funding, protocol revenue, recovered funds, as well as the impact of early redemptions and the destruction of unclaimed portions after the window closes on January 1, 2028.
app_icon
ChainCatcher Building the Web3 world with innovations.