0xSaint

@oscail_ @0xjasp @fragmetric @_SEAL_Org Nope. Managed to swap it, though

@0x51x @0xjasp @fragmetric @_SEAL_Org Have you received your BTC yet? I’ve been waiting for my withdrawal for 41 days now

Weekly Buyback #23 573,777 $FRAG was purchased on the open market and transferred to the FRAG Treasury Wallet. Buybacks were funded using 100% of the protocol fees generated during the period.

@LanaAI 50$/month is very pricy. Need pay per request plan.

Too much happening on Solana to keep up? Lana curates the latest headlines to help you stay informed. Open stories, ask questions, and dive deeper in seconds.

@Eli5defi Hope all is well bruv.

Sorry I had to delay this publication; I needed some time to sanitize my devices. I ended up reinstalling everything, and it took a while, lol. I didn’t expect it to be so much work. And yes, the weekly bookmark is back (along with other posts). Feel free to check it out, and if you can, please support me by sharing it. That would mean a lot. :)

@Eli5defi Isn't it 95% of crypto projects, bruh? There is too much scam in crypto.

I've worked on 200+ projects so far, and here’s my honest take on project red flags and green flags. Red Flags: - Pay you generously but no follow-up or questions asked - Obsessed with token PA, but no catalyst and no fundamentals - Name-drops past “big” partnerships too often (Nvidia, Google, etc.) - Doesn’t understand their own tech stack - Keeps changing the brief, and each version contradicts the last - Asks you not to disclose the partnership - Pushes you to use their draft verbatim, instead of your voice - Often uses words like pump, guaranteed, multiple Xs, etc. If a client or project hits several of these, it’s usually best to walk away, no matter how much they’re paying. Green Flags: - Pay you generously, on-time, as per commitment / deliverables - Has clear campaign goals beyond engagement/reach - Understands your strengths and lets you use your voice (unless legally required) - Encourages you to disclose the partnership - Catalyst-driven campaigns: planned, structured, and organized, not random “awareness” pushes Any other signs you’d add to the list?

@KeyShield_Pro Go to hell, ripper.

@Scam_tackle Nah, your mama must be crying ripper. Stop it, ripper 🤡

@0x51x Feeling frustrated after something like this is completely normal. You're helping by posting publicly. Check my pinned thread for patterns that show up in these scams and how to report them safely.

The biggest Crypto victims are: Americans over 50 > They lost $4.4B > Average loss per victim: $100K > 78% had no idea they were being scammed > 38 victims were referred to suicide intervention Nearly 2x more losses than every other age group $11.4B lost to crypto scams last year We talk about hacks but this is even crazier...

@Glixch @fragmetric We have been rugged. People have been waiting for months, yet there are no withdrawals.

@fragmetric Wen support for US? I restake to fragBTC but am considering pulling out because I am region locked for receiving frag rewards. The fragBTC works great, just am not eligible to receive frag.

Weekly Buyback #25 518,608 $FRAG was purchased on the open market and transferred to the FRAG Treasury Wallet. Buybacks were funded using 100% of the protocol fees generated during the period.

@0xjasp @fragmetric @_SEAL_Org I'm having the same issue. Does it mean we got rugged.

@fragmetric could you look into this? @fragmetric has been unresponsive for MONTHS and their discord is off, @_SEAL_Org 🙏

@fragmetric @fragmetric need help.

@fragmetric I need help. The discord link is invalid @fragmetric

@Punk9277 Said the guy who ruined CT for his own greed 👏

to all the founders and teams out there: remember, CT is one of the roughest places on earth the overwhelming majority of the audience here is either here for the money or for the drama all while you’re managing a team, executing, and building through this chaos and noise it can wear you down sometimes but please never let it get the best of you nothing here determines where your project is a year from now what matters, always, is the quiet, consistent work that compounds behind the scenes let’s keep going

@sol_nxxn @solana Seems you're having a ptsd of the past. Btc was free in 2011. Go ahead, cry now.

This is the best call I have ever made And this one actually changed my life Solana.

@arndxt_xo No, it won't replace game dev. Ai is good at showing the images or few sec clips, but developing a game ain't creating an image.

game devs are about to have a full meltdown gpt Image 2 launched just 48 hours ago......and it just proved that building a complete video game, one of the single hardest creative + technical things humans have ever attempted, is now something literally ANYONE can do with zero experience. you dont need a team or coding background

@Eli5defi Thanks for the info. Your info graphics are awesome. You have inspired me to create my own. Sometimes, text editing can be painful when ai hallucinate. Wish could learn a few prompts from you.

As you know, I’ve made a ton of infographics using a mix of AI and manual editing. I just tested recently launched GPT Image 2 against Nano Banana 2 side-by-side using the exact same prompt. Here’s my personal verdict: > GPT Image 2 (Left - Blue Infographics) - Best-in-class text recognition; nearly perfect, only minor errors - Infographic output is ridiculously good - Stronger with complex, multi-element work (infographics, data, design) - Minimal hallucinations - A bit slower than NB - The editing features are a godsend > Nano Banana 2 (Right - Green Infographics) - Feels more “personalized”; probably because I use it for almost everything, and it’s learned from my previous instructions - Infographics output is crazy good but sometimes hallucinate randomly - I can say text recognition is 80-90%, I need to specify the prompt or manually edit later - Lightning-fast; no need for Thinking or Pro mode for simple stuff - More consistent results across images > Which One Should You Use? - Choose GPT Image 2 if you need precision, text accuracy, or complex compositions (e.g., infographics, UI/UX mockups, branded graphics with text, detailed instructional images, or heavy editing workflows). - Choose Nano Banana 2 if you prioritize speed, photorealism, and volume (e.g., social media content, product photography, lifestyle visuals, rapid concept testing, or cinematic scenes).

@Mantle_Official @KelpDAO Can't withdraw $cmETH

An update on the rsETH incident involving @KelpDAO. To our Mantle community, ecosystem builders, and partners, following our initial statement earlier this week, we want to share where things stand, what has been confirmed, and how we are moving forward. 1. Mantle remains fully secure. Our underlying network, official bridges, and core assets have not been compromised. @LayerZero_Core has confirmed in its KelpDAO Incident Statement that the exploit was isolated entirely to KelpDAO's rsETH configuration, with zero contagion to any other asset or application. The attacker did not interact with Mantle contracts or Mantle markets at any point. The localized liquidity pressure observed in recent days reflects spillover from that third-party cross-chain vulnerability, not any issue with Mantle's infrastructure. The protective pauses outlined in our prior statement remain in place and will be lifted once our team and ecosystem partners confirm it is appropriate to do so. 2. The Mantle ecosystem is resilient. Since April 18, capital has been steadily flowing back into the Mantle ecosystem. Onchain data shows cumulative repayments across core USD assets have reached approximately $204 million within 48 hours. Liquidity conditions continue to normalize, and the strength of the recovery speaks to the depth and resilience of the Mantle community. 3. Mantle is standing together with our ecosystem. Mantle is in active coordination and communication with the @aave team and affected protocols on a coordinated recovery plan, including potential treasury participation. We will continue to share meaningful updates as the situation develops. Through moments like these, Web3's strength shows how we stand together. That's where we are, and where we'll remain. We stand firmly with our builders. Thank you for standing with us. Stay safe.

@smykjain Criminals like @Re7Labs and @eulerfinance should listen to your advice.

LayerZero should step up to cover some of the losses. The party with biggest responsibility here is LayerZero. If they don't own up to it and Aave bears most of the cost then ecosystem should start boycotting LayerZero. Ideally, losses should go to all parties LayerZero, KelpDAO & Aave. Primarily, LayerZero provides option to add more CDN so you don't have to trust LayerZero. Not because the risk that LayerZero can get hack. Even FLUID token has limits with CCIP that no more 2% of FLUID supply should be bridged in 24hr timespan which after this incident we will make even more tight to 0.5%. Industry really need to start putting caps everywhere.

@SolanaFloor @arbitrum Decentralization is a myth

🚨New: Ethereum’s 2nd largest L2 by TVL, @arbitrum, froze 30,766 $ETH ($70M) tied to the KelpDAO exploit and moved the funds to an intermediary frozen wallet. The move sparked backlash, with critics raising concerns about how truly decentralized layer 2s are.

@Eli5defi @LayerZero_Core is another criminal who refuses to take responsibility just like @Re7Labs @eulerfinance criminals who distance themselves as soon as exploit happened. These criminals will keep denying unless they bring within the law.

Interesting post-mortem here, but it leaves me with more questions because it comes across as so defensive. Anyway, let's get to the basic first. Based on LZ, on April 18, DPRK's Lazarus Group (TraderTraitor unit) stole $290M from KelpDAO's rsETH bridge. The attack, step by step: ❶ Attacker found the list of RPC nodes (the "eyes") that LayerZero's verifier trusts for truth ❷ Hacked 2 of them. Rigged the malicious software to lie only to the verifier, and tell the truth to everyone else so monitoring systems saw nothing wrong ❸ DDoS'd the honest RPCs offline. Verifier failed over to the poisoned ones ❹ Verifier got fed a fake transaction as real. Signed off. Bridge released $290M worth of rsETH that wasn't backed by anything ❺ Malware self-destructed. Binary deleted, logs wiped, configs gone LZ stated that Kelp used a single verifier (1-of-1 DVN setup) against LayerZero's repeated warnings. One verifier, one point of failure and confirms the damage is isolated. Zero contagion to any other asset so far. But I still have a lot of questions, cmiiw: - If 1/1 DVN was malpractice, why was it allowed to ship? - The compromised infrastructure belongs to LayerZero Labs, not Kelp. - How did the attacker get the RPC list in the first place? - Swapping the binary on production nodes implies a root-level compromise. On RPC poisoning: either this config leaked (which suggests a prior, unreported LayerZero compromise), or the attacker inferred it via sophisticated traffic analysis. Replacing the running op-geth binary on a production RPC node requires one of the following: root access on the box, a compromised deploy pipeline, or insider access. Which was it? The statement doesn’t say. If it was the deploy pipeline, that’s a supply-chain incident. If it was credential compromise, the scope is broader than what they’re admitting. The statement routes around this question entirely.