perhaps

Karnel - Mask - Linux - Exchange server 2008 - Cyber - Quantom Computing - Red Hat - Hackers\Linux.
✞ⱼₑₛᵤₛ 𝄴ₕᵣᵢₛₜ✞/מָשִׁיחַ✡ /حبيبي

[perhaps @SystemDebt]

☭יוֹסֵבּ בֶּסָריוֹנִיס דזֶה ג'וּרָ'אשׁווִילִי

[Alan Rice @alan__rice]

AI prices are getting ridiculous

[perhaps @SystemDebt]

@Justin_lords @irabukht Its called "all inboxes" section which allows you to see all of the emails you get to all of the accounts at once :).

[ZachXBT @zachxbt]

@USTreasury You should sanction all of the sketchy Iranian OTC brokers in Canada being abused by illicit actors.

Two were used in recent violent home invasion robbery / extortion cases to launder crypto.

-Nia Nations Exchange (NNCE)
-Million Exchange (MillionEx)

[ZachXBT @zachxbt]

@ScalpWithIsrul @DriftProtocol @solana @tether Why would you hold the token of a dead perp DEX that was exploited for $285M and became insolvent?

There’s nothing to investigate you lack common sense

[ZachXBT @zachxbt]

@edgeX_exchange “We investigated ourselves and did not find ourselves guilty even though we control nearly the entire supply”

[perhaps @SystemDebt]

@zachxbt @BaseonethL2 @ersakshamjain @binance @Gate_io Edgy 🔪

[perhaps @SystemDebt]

@GroovyPNW_Fit @Stacco__ @templedao 😂🤣

[ZachXBT @zachxbt]

Update: LAB continues market manipulation on CEXs via MM up to $5.7B mkt cap ($14B FDV) at top 22 ranking.

Disappointing to see exchanges allow it to continue as we all know how it ends when the hidden supply unlocks from OTC, private sale, airdrop, etc finally occur since insiders control nearly the entire float.

Just is a question of whether the vesting terms are changed yet again by the team.

Retail traders get baited in due to top CEX listings, trending lists, & high market caps which create the illusion of safety.

As stated before I do not advise trading these types of tokens.

[perhaps @SystemDebt]

@unusual_whales Interesting to see all these bots spammimg the comment section @unusual_whales

[perhaps @SystemDebt]

@zachxbt @FabianoSolana @Rain__Protocol @snovik & @OrenHershkovitz 🫂🇮🇱

[ZachXBT @zachxbt]

You are a clown.

Patagon is not a victim you purposely buy up garbage protocols for civil lawsuits to profit.

Zama an innocent protocol and all of its users were dragged into your legal case.

You did not alert Zama or give them the chance to contest beforehand.

This is the reality in the US: Arbitraging outdated laws and boomer judges who know little to nothing about tech cases.

Guess this is expected when you are a bad actor who helped lose $93M from actual victims at Stream DeFi….

[Rand @randhindi]

Thanks to @zachxbt, we found the root cause and will be taking the appropriate actions to unblock the situation. Tldr; this has nothing to do with Zama, or privacy.

The issue stems from an address related to the Overnight Finance hack, which deposited over ~$12.5m USDC into our confidential USDC wrapper contract. Back when they did, their address wasn't on any sanctions list and was not flagged by our KYT tools. However, a court order yesterday night placed a restraining order on various wallets linked to the hacker.

Since there wasn't much utility yet for the cUSDC wrapper, there were very little funds in it, and as a result the vast majority (>99%) of funds in the cUSDC contract came from that single hacker's deposit. Because of this, the court order asked to freeze our wrapper contract to freeze the hacker's fund.

So the sanction was not against Zama, or against privacy. It was a classic restraining order as we see often in DeFi, and we should have been notified so we could have taken the appropriate actions on our side.

I want to be very clear about something: our posture has always been compliant confidentiality, and we will not tolerate any illicit behavior in our protocol. It's also really useless for hackers to try to use Zama to hide their trail as we are precisely not a mixer and we do not obfuscate the sender and recipient, only balances and amounts. Eg you can see the hacker's cUSDC transactions here: https://t.co/yFtdaz5ytU

We are in touch with the various people involved to resolve the situation asap. In the meantime, we will pause the cUSDC, cUSDT and cWETH contracts until we have finished our investigation, identified all addresses linked to this case and taken appropriate action.

I will share a more detailed post-mortem and how we plan to deal with such requests in the future.

[perhaps @SystemDebt]

@stacy_muur @Uniswap I truly wonder if this post is a brain rot or a rage bait
Still can't grasp my head around the essence of this post.

[perhaps @SystemDebt]

@stacy_muur @Uniswap Tragic & sad but tbh the saddest part is that you guys even see ads and don't use brave browser or ad blocker extensions in 2026. REALLY FUCKING SAD.

[unusual_whales @unusual_whales]

Trump: "I'm right now at 99% in Israel. I could run for prime minister, so maybe after I do this, I'll go to Israel and run for prime minister."

[perhaps @SystemDebt]

@nikitabier @John_Dickinson3 @nikitabier 🫨

[perhaps @SystemDebt]

@John_Dickinson3 @Michae1Hinrichs @nikitabier 😭😂🤣

[perhaps @SystemDebt]

@MastrXYZ @toly which is exactly why alpenglows skip vote mechanism matters here
correct me if I'm wrong 😅 @toly

[perhaps @SystemDebt]

@MastrXYZ @toly Moreover, simd is still an early draft PR with no description and no reviewers the direction is endorsed the specific 1B number still has to survive simd review
and bigger blocks raise real centralization concerns heavier blocks favor better funded validators

[perhaps @SystemDebt]

@MastrXYZ @toly So basically "faster finality" isn't really what this proposal about.. faster finality is alpenglows job it cuts block finalization from ~12s to ~150ms. SIMD is about throughput (more work per block), not finality
it's an alpenglow benefit, not a 0538 benefit