Dexible

Liquidity efficient DeFi algo trading. Set and forget on #ETH #AVAX #POLY #BNB #ARB & #OPT

[Dexible @DexibleApp]

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

[Dexible @DexibleApp]

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

[Dexible @DexibleApp]

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

[Dexible @DexibleApp]

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

[Dexible @DexibleApp]

@FixedFloat @MetaSleuth Hello @FixedFloat team,

The Dexible team has also sent messages your way to engage.

Please respond ASAP

[Dexible @DexibleApp]

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

[Dexible @DexibleApp]

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

[Dexible @DexibleApp]

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

[Dexible @DexibleApp]

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

[Dexible @DexibleApp]

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

[Dexible @DexibleApp]

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

[Dexible @DexibleApp]

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

[Dexible @DexibleApp]

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%

[Dexible @DexibleApp]

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.

[Dexible @DexibleApp]

@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

[Dexible @DexibleApp]

@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: https://t.co/i0eUBM0zpA

https://t.co/DThmH0wDim

[Dexible @DexibleApp]

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

[Dexible @DexibleApp]

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