MoversSomeguy↓416Afi↓374Grethos↓352Abhi | AP Collective @ Token 2049 🇸🇬↓281aadvark↓263TradeAnton Boiarchuk↓5.7%Cuzzo 🛡️↓4.2%Biti8↓3.6%vitalik.eth↑1.2%VouchesMLO990 WHUF → Serpin TaxtMLO496 WHUF → CirrusMLO100 WHUF → Phoenix 🐦‍🔥MLO100 WHUF → OSFReviewsCoinbase Ventures 🛡️positive · 75 upvotesgabriel shapiropositive · 64 upvotes一川drive 🔴positive · 32 upvotesaiobkhan ✨positive · 25 upvotes
Profile· Questionable@reflectmoneyOn Ethos
Reflect

Reflect

5 reviews, 0% of them positive.0% positive · 5 reviews· Influence factor 30, above 6% of accounts

The record

From 5 activities · Apr 2026

Reflect, a Solana-based yieldcoin protocol, faced severe backlash following the April 2026 Drift Protocol exploit that wiped out USDC+ holdings. Users allege deliberate misrepresentation of the product as low-risk and diversified, deletion of 'INSURED' claims, and inadequate communication and compensation plans in the aftermath. The protocol has been accused of pivoting to new products while affected users face years-long recovery timelines with minimal transparency, and of refusing to acknowledge the complete loss of user funds.

“Lied about diversification, deleted the 'INSURED' claim, parked 100% on Drift, refusing compensation while running a com”Reflect (@reflectmoney) is a Solana-based yieldcoin protocol backed by @a16zcrypto, co-founded by Nico (@0xNIC0). On April 1, 2026, Reflect's flagship product USDC+ was effectively wiped out following the exploit on Drift Protocol. The loss itself is not the basis of this slash. The basis is the deliberate misrepresentation that preceded the exploit, and the conduct that has followed it. The core misrepresentation Reflect marketed USDC+ and USDT+ as low-risk, diversified, and at one point explicitly insured (!!!). On the day of the exploit, users learned that 100% of the backing for these products was sitting in a single integration: Drift. The diversification language in the product docs and the "FUNDS ARE INSURED" claim in Reflect's communications were both materially false at the moment they mattered. Reflect's first public statement after the exploit contained the line "FUNDS ARE INSURED." That sentence was then quietly edited out of the post rather than corrected. Evidence of the original wording and the deletion was captured by @Punk_Monke: https://x.com/Punk_Monke/status/2039430976372412463 Four months before the incident, on December 4, 2025, Nico had publicly positioned Reflect as "scalable, secure, verifiable and low-risk cash yield": @0xNIC0: https://x.com/0xNIC0/status/1996525858430017730 Post-exploit conduct After freezing mints and redemptions, Reflect: 1. Limited replies on both the main account and the founder's account 2. Never publicly disclosed the exact Drift exposure percentage 3. Provided no Discord or Telegram for affected users to coordinate 4. Made no concrete commitment to compensate affected USDC+ or USDT+ holders 5. Began publicly positioning a "Reflect v2" relaunch as the path forward @Punk_Monke summarized this directly: https://x.com/Punk_Monke/status/2040052940124393724 In the weeks following the exploit, with no compensation framework on the table, Reflect: 1. May 1, 2026: Announced @arifkazi_ as Head of Growth. New hire, no parallel announcement on using operating capacity to make users whole. 2. May 6, 2026: Posted a thread about "sharpening thinking" on market direction, framing the incident as a clarity moment rather than a remediation obligation. 3. May 7, 2026: Launched "a new Reflect" with tranching, new architecture, new partners, new look. Marketed as a clean slate. 4. May 7 to 11, 2026: Attended conferences in Miami including Consensus and side events with Multicoin, Figure, and Kamino. 5. May 12, 2026: Announced partnership with @BlockworksAdv to bring "mature risk-analysis and allocation methodologies to Solana DeFi." The same team that ran a 100% single-protocol exposure 6 weeks earlier is now positioning itself as the risk infrastructure layer. @FabianoSolana called this out directly: https://x.com/FabianoSolana/status/2052491964998647849 @Lodzhal has been asking for an update on user funds across multiple replies for 6 weeks straight, including pinging a16z directly. No public response. Some publicly documented user losses @MacnBTC, $100k to $450: https://x.com/MacnBTC/status/2043690628740235714 @Tola_niii: https://x.com/Tola_niii/status/2043691886141989101 @enesonchain, 200 down to 135 with no exit liquidity: https://x.com/enesonchain/status/2043611417224302608 @Tola_niii on the lack of refund communication: https://x.com/Tola_niii/status/2042238727502614970 @basq0x calling them grifters, noting a16z backing: https://x.com/basq0x/status/2040975062514454890 Founder track record A separate account, @drift_trades, has publicly alleged that Nico has a pattern of abandoning projects when conditions get hard, citing both an earlier NFT project and the $Dark token: @drift_trades: https://x.com/drift_trades/status/2041290116061388827 This is one source and should be weighed accordingly, but it is on the record and consistent with the current pattern: when the protocol broke, the response was to limit replies, delete claims, and pivot the narrative to v2. Ethos founder Serpin has already negatively flagged Reflect too: https://x.com/serpinxbt/status/2041199677677121821 Team members publicly affiliated with Reflect on X - Nico (@0xNIC0): co-founder and CEO - Vini (@vinikloppel): design engineer - Daniel (@_danielpavel): engineering - Jacob (@stablecoinjesus): creative director - Arif (@arifkazi_): head of growth, joined May 1, 2026 after the exploit TLDR: - Project: Reflect (@reflectmoney), Solana yieldcoin protocol, a16zcrypto-backed - Products affected: USDC+, USDT+ - Marketed as: low-risk, diversified, insured - Actual exposure at time of exploit: 100% on Drift Protocol - Trigger event: Drift Protocol exploit on April 1, 2026 - Aggravating conduct: deletion of "FUNDS ARE INSURED" claim without correction, no compensation framework 6 weeks on, full pivot to v2 relaunch, ongoing BD and partnership announcements - Existing Ethos sentiment: 0% positive across 3 reviews - Already publicly flagged by Ethos founder @serpinxbt A protocol can fail. A protocol can integrate something that gets exploited. Those alone are not slashable. What is slashable is telling users their funds are diversified and insured, parking 100% of those funds in a single venue, losing all of it, deleting the insurance claim instead of owning it, and then running a comeback arc on stage at Miami while the people who funded the original protocol are still holding bricked positions. Current Ethos score does not reflect this. A slash is appropriate.3lixbt (🗣️,🤝) · 1543· 5mo ago · negative4
5 of 5 · most upvoted first