Jasmin Corbett

Hello! Please send me a direct message, and our team will respond quickly to assist you with your requests. twitter.com/messages/compo…

@0xfyury Hello! Please send me a direct message, and our team will respond quickly to assist you with your requests.

@StaniKulechov What about user lending weth on arb? Are we fucked ?

rsETH has been frozen on Aave V3 and V4, the asset does not have any borrowing power as a measure due to KelpDAO bridge exploit that happened outside of Aave. Both Aave V3 and V4 does not have further exposure to rsETH.

@hej_crypto Hello,we're sorry to hear that. We’d love to assist you here! Please feel free to send us a DM so we may take a closer look

@StaniKulechov @aave If I repay borrowed USDC, can I withdraw my ETH on Arbitrum? Plz help me

@MANGEBRANT Hello,we're sorry to hear that. We’d love to assist you here! Please feel free to send us a DM so we may take a closer look .

@StaniKulechov I have normal Eth on ethereum chain (core) that i cant withraw or loan more for "This asset is frozen due to an Aave Protocol Governance decision. More details"* And when i go to details there doesnt say anything about eth on mainchain?only about rsETH and wrsETH?

@NicoleWils57067 Hello @NicoleWils57067 we're sorry to hear that. We’d love to assist you here! Please feel free to send us a DM so we may take a closer look

@LayerZero_Core @KelpDAO @_SEAL_Org My cross-chain transaction has been stuck for several hours. Can it continue? If not, please refund my tokens.

We’re fully aware of the rsETH exploit and have been in active remediation with the @KelpDAO team since the incident and continue to monitor. All other applications remain safe. We are still identifying the root cause alongside @_SEAL_Org and others. We will publish a complete post-mortem with @KelpDAO as soon as we have all information.

Withdrawal failures are currently attributable to the pause enacted after the April 1 exploit, which involved a compromised multisig, oracle tampering, and exceeded withdrawal limits. Finalization of fund recovery and reimbursement plans is in progress. Please DM me for further assistance

@DriftProtocol @tether What about the tokens not listed in affected assets / leftover assets? LBTC isn’t listed there. What about those deposits?

Today, Drift is announcing a collaboration with @tether and other partners totaling up to nearly $150 million to support our commitment to a relaunch with USDT at the center, and a path to user recovery. These funds encompass a $100M revenue-linked credit facility, an ecosystem grant, and loans to market makers, designed to fund a dedicated user recovery pool. Learn more 👇

@Ositavalent A pause triggered by the April 1 exploit (compromised multisig, oracle manipulation, withdrawal limit issues) is causing current withdrawal disruptions. Fund arrangements and reimbursement plans are being finalized. Direct message me for further assistance

@0xNIC0 @reflectmoney After the long silence, you write a bunch of garbage again, without addressing the main issue, when will users be refunded, while put all USDC+ in a single protocol?

A lot of questions have come in about USDC+ and single-venue allocation. Given everything that's happened, it's worth walking through the reasoning directly. What follows is personal, not an official statement from Reflect. Every architectural decision at Reflect starts from one principle: the protocol does not take custodial control over user assets. Full stop. That principle is what led to single-venue allocation for USDC+ beta, and the reasoning is important to understand. Distributing collateral across multiple venues means rebalancing between them. The question is: who does the rebalancing and on what basis? If the team moves collateral between venues at its own discretion, that action starts to look like custody. It doesn't matter what the smart contracts say if the team is the one deciding where funds sit. This isn't a theoretical distinction. The SEC recently clarified that DeFi interfaces operating in a non-custodial, non-discretionary manner may operate without broker-dealer registration, while those that exercise discretionary control over user assets fall inside the regulatory perimeter. Where a protocol sits on that line matters, and it informed how Reflect was built from day one. I was not willing to cross that line. The standard was that rebalancing must happen permissionlessly, on-chain, driven by allocation weights determined through independent risk analysis rather than the team's own judgment. That required the smart contract infrastructure to support multi-venue routing, and an independent risk framework to inform the allocation decisions. This is not the easy path. But I believe it's the right one, and that the space will ultimately move in this direction. Both remain a core focus for the team. Drift was the lending venue that USDC+ launched on. Moving collateral away from it to another venue after launch would have been the same kind of discretionary team action over user assets that the entire architecture was designed to prevent. None of this changes the outcome for the people affected, and I understand that. Building with conviction doesn't guarantee the outcome. I'm not sharing this to explain away what happened. I'm sharing it because the people who used Reflect beta deserve to understand the architecture and the thinking behind it. Building the right way is slower. It's harder. But I didn't start Reflect to take shortcuts. More to come. Official updates through @reflectmoney.

@xedred01 The pause initiated after the April 1 exploit—marked by a compromised multisig, oracle manipulation, and withdrawal limit breaches—has led to withdrawal failures. Final steps for fund recovery and reimbursement are being completed. Send me a Dm for further assistance.

@0xNIC0 what about reimbursement of users? i see nothing about that is mentioned yet. all the long statements doesnt mean anything if u cant take necessary actions to gain user trust back

@galgocrypto Withdrawal issues stem from a pause activated after the April 1 exploit, which involved a compromised multisig, oracle manipulation, and breached withdrawal limits. Fund recovery and reimbursement plans are being finalized. Please DM me for further assistance

@0xNIC0 Hey Nico, how does Drift recovery plan with Tether affects Reflect protocol and users? Are we getting our funds back?

@Usoppu The pause in withdrawals was triggered by the April 1 exploit, which included a compromised multisig, oracle manipulation, and exploited withdrawal limits. Finalization of fund recovery and reimbursement is underway. Kindly send a DM for further assistance

@DriftProtocol @tether good luck and congrats to everyone exposed to this! I have $5k in reflect money myself so finger crossed will be able to get some compensation from this.

@Gleepglop3 Due to the April 1 incident—featuring a compromised multisig, oracle manipulation, and withdrawal limit breaches—withdrawals remain paused. Reimbursement arrangements and fund restoration are being concluded. For further assistance kindly send a Dm.

@DriftProtocol @tether Why is it asking me to sign up in the next 7 days to get my refund but the connect wallet button doesn't work nor the view your allocation button? Why did you wipe my account to zero?! You need a snapshot now that I need to sign up for with another token? WTF

@7RWcrypto We acknowledge the Drift protocol issue where profitable positions can’t be closed at entry value due to price exploit. A formal reimbursement plan is available for affected users. Please DM for further assistance

@DriftProtocol ???When can I withdraw it?

Interim Update We recognize the impact this has had across our users and the builders who have integrated with us - many of whom rely on Drift as core infrastructure. We’re actively working on next steps and will share more once details are finalized.

@EnricoPassaniti A pause triggered by the April 1 exploit (compromised multisig, oracle manipulation, withdrawal limit issues) is causing current withdrawal disruptions. Fund arrangements and reimbursement plans are being finalized. DM me for further assistance

@solana @DriftProtocol @uselulo Still no response so far. Would really appreciate some clarity on this situation. @Solana @DriftProtocol

🚨 I lost 8.88 SOL — and the timing makes it worse. Thread 👇 #Crypto #DeFi #solana #SOL

@GauravK358 A pause triggered by the April 1 exploit (compromised multisig, oracle manipulation, withdrawal limit issues) is causing current withdrawal disruptions. Fund arrangements and reimbursement plans are being finalized. Kindly send a DM for further assistance

@DriftProtocol I have ~$62k stuck in perp collateral on Drift — this is not just numbers, it’s a major part of my capital. I understand investigations take time, but timely updates on recovery structure and withdrawals are extremely important for users like me.🙏🙏🙏

@LeeTimo1 The pause in withdrawals was triggered by the April 1 exploit, which included a compromised multisig, oracle manipulation, and exploited withdrawal limits. Finalization of fund recovery and reimbursement is underway. For further assistance kindly send a Dm

@DriftProtocol I'd rather know I'm not getting my money so I an plan for that. They have ghosted us now and cashed out. I think it is safe to assume we are not getting any money back. I just hope people are able to name and shame these people and their details

@jason_kellem Withdrawal issues stem from a pause activated after the April 1 exploit, which involved a compromised multisig, oracle manipulation, and breached withdrawal limits. Fund recovery and reimbursement plans are being finalized. Please DM me for further assistance.

@DriftProtocol Are we still not allowing withdrawals?

Hello! Please send me a direct message, and our team will respond quickly to assist you with your requests.

Hey, appreciate that. Yeah, we went deep on this one v3 wasn’t just a quick flag flip. Had to refactor quite a bit of the fee bumping logic, replace by fee handling, and how we validate transactions against mempool policies. The old v2 assumptions were baked into a few core modules, so touching that without breaking mainnet stability took some careful surgery. Worth it though, v3 gives us better fee management and more predictable RBF.

@SparrowWallet Dude that v3 transaction support sounds super legit did you guys have to refactor a ton of the underlying code for that?

Sparrow v2.4.2 has been released to fix issues in the transaction editor and improve certificate pinning for TLS connections. Support has also been added for v3 transactions in the transaction editor. Changelog here: github.com/sparrowwallet/…

@iamkenlot Hello! Please send me a direct message, and our team will respond quickly to assist you with your requests.

@DriftProtocol WHEN WE CAN GET BACK OUR STAKED ASSET？

@darkhai99 The pause initiated after the April 1 exploit—marked by a compromised multisig, oracle manipulation, and withdrawal limit breaches—has led to withdrawal failures. Final steps for fund recovery and reimbursement are being completed. DM me for further assistance

@DriftProtocol Anyone from team and fellow can at least giving some advice ?

@BuysnowRu The pause initiated after the April 1 exploit—marked by a compromised multisig, oracle manipulation, and withdrawal limit breaches—has led to withdrawal failures. Final steps for fund recovery and reimbursement are being completed. DM me for further assistance

@reflectmoney What concrete steps will be taken to compensate for the lost funds? It is очевидent that recovering the stolen funds through Drift is, most likely, no longer possible. At the beginning of the incident, you stated that the funds were insured, but that message was later deleted.

Confirmation of Impact WRT Drift Protocol Incident Over 20 Solana protocols with downstream exposure to Drift were affected. Reflect was among them. How this affects Reflect Beta users USDC+ collateral was allocated to Drift as its lending venue. As a result of the exploit, USDC+ collateral deployed to Drift was impacted. The approximate value of USDC+ collateral allocated to Drift at the time of the incident was ~$1.9M. USDT+ was not affected. USDT+ operates on Reflect’s newer venue routing framework, which distributes collateral across multiple venues, and had no exposure to Drift at the time of the incident. Minting and redemptions for both USDC+ and USDT+ were paused immediately after detection of the exploit. Immediate Actions Taken The team has been in active daily contact with legal counsel, law enforcement, and the Drift team regarding the situation since the day of the incident. Beyond the immediate response, the team is conducting an extensive review of all available options with counsel. This includes monitoring developments around Drift’s own recovery and remediation process, law enforcement proceedings, and third-party recovery efforts underway across the ecosystem. We are not in a position to make specific commitments at this time, but we are taking this seriously and evaluating every avenue available to us. We expect to provide a further update within two weeks. Relaunching Reflect Reflect’s relaunch will follow the completion of a thorough, public review of all yield venues on the Solana network. This review will go beyond conventional smart contract risk and will cover vectors that are not always visible to end users, including multisig configuration changes, admin key activity, governance parameter modifications, and other operational risk factors that this exploit has shown are critical to monitor. We will not relaunch products until this process is complete and we are confident in the protections in place. Where to follow updates All official updates will be shared through @reflectmoney and @0xNIC0. Do not trust information from any other source.