Dexible

Introducing Dexible v2.0, the slumbering giant of #DeFi wakes. Dexible will revolutionize on-chain capital deployment and shake up how aggregators work. Our team will combine 2 years of user testing with a new model for token incentives with $DXBL. Read on, anon 👇 1/x

Once again, we want to apologize for the events that occurred. We are committed to finding the best solution for our community and will keep you updated on any further developments. Sincerely, The Dexible Team 6/6

Should Dexible not find any joint ventures, the business will become insolvent, and we will be required to close our business. We understand that this would be a significant loss for our users, and we regret the impact that closing would have. 5/6

Dear Dexible users, We want to express our sincerest apologies for the events that occurred last Friday. We understand that the exploit caused immense frustration, inconvenience, and loss to our users. 1/6

@FixedFloat @MetaSleuth Hello @FixedFloat team, The Dexible team has also sent messages your way to engage. Please respond ASAP

@MetaSleuth @DexibleApp Hello, If funds were stolen and a fraudster used our service, then write a letter to our security service by mail info@fixedfloat.com so that they can help you figure out what happened

Today @DexibleApp was exploited by 0x684083f312ac50f538cc4b634d85a2feafaab77a in Ethereum and Arbitrum. Total Loss is ~$2M. Initial fund came from @FixedFloat Attacker's funds have across chains onto BSC and ETH, ~930.6 Ether on Ethereum has already been fully laundered into @TornadoCash , with funds on BSC still being laundered into TC continuously. See in metasleuth ⬇️ metasleuth.io/result/eth/0x6…

@AshurCapital A remediation plan is being discussed with the team. Please join the community discussion on Discord.

@DexibleApp Will you make the exploited traders whole? Since this is an exploit on your vulnerable contract

Dear Dexible community, we regret to inform you that in the early hours of February 17th, a hacker exploited a vulnerability in our newest smart contract. This allowed the hacker to steal funds from any wallet that had an unspent spend approval on the contract. 1/5

The full post-mortem report is posted as a PDF in Telegram and Discord. The team is now working and communicating with the affected to develop a coordinated remediation plan. The team is in communication with nearly all affected users. UI will be updated and paused. 3/3

All our operations are currently paused and all impacted contracts have been paused. You can revoke spend allowances using these addresses. Please find these typed out in our Discord, Telegram, or documentation. 2/3

We are actively working on a remediation plan but we wanted to first focus on triage on the scope of the hack and who was affected. We've outlined the details and scope. You can find a full post-mortem in our Discord announcements channel. 1/3

@neon___glow @wasgiventhatday @ZoomerAnon @BlockTower @spreekaway @zachxbt We produced a full report and published it in our Discord community.

@wasgiventhatday @ZoomerAnon @BlockTower @DexibleApp @spreekaway @zachxbt What happened exactly? Exploit?

Looks like @BlockTower just lost $1,4m of TRU via @DexibleApp. Please cancel all outstanding orders on Dexible! @spreekaway @zachxbt etherscan.io/tx/0x138daa4cb…

@pcaversaccio Let’s be serious instead of making light of affected wallet addresses, please.

"There's no excuse for an exploit, but these things happen." - are you fucking kidding me

Update: 17 traders were affected total, 4 on Mainnet, 13 on Arbitrum. Out of 36 on Arbitrum, only 13 were exploited. Out of 14 unique on Ethereum, 4 were exploited. A few big whales were exploited accounted for ~85%

We need to assemble a list of all affected community members. Enter Discord and provide block explorer information as soon as possible so we can have an accurate picture of those those records.

@DollarCakeCry Jokes aside, please be sure you get the help you need if you were affected. File a support ticket on Discord soon. We now have assembled a full list of txns into spreadsheet, but we don't know who is who

@DexibleApp yeah i know but its like going to a funeral of someone that got assassinated and say theres no excuse for John getting assassinated, but hey this thing happen time to time!

@DollarCakeCry exploits happen in DeFi. The Dexible contracts on Mainnet, Arbitrum, and BSC are not the first, nor the last. More info here on the architecture and contracts: dexible.gitbook.io/dexible/dxbl/d… rekt.news

@DexibleApp wtf "There's no excuse for an exploit, but these things happen." not the best to say really...

@Parap38935571 @rektautist @peckshield Team members were not responsible, and team members were exploited too.

@rektautist @peckshield @DexibleApp maybe it was the team

Hi @DexibleApp, you may need to ask users to revoke allowance! (The loss is already >$1.5M). Here is one hack tx: etherscan.io/tx/0x138daa4cb…

@peckshield @cryptendi Protocol was paused ✅ at 5:00 AM UTC this morning.

@cryptendi @DexibleApp The protocol should be now paused.