0xa.eth

cooking @wallet

[0xa.eth @ecrecover]

Yes+No < 1

[OKX @okx]

⏳

[OKX中文 @okxchinese]

https://t.co/1hElp5m81E

[0xa.eth @ecrecover]

@SuhailKakar Vibe betting with polymarket cli

[0xa.eth @ecrecover]

AWS
decentralized
2000%

[0xa.eth @ecrecover]

@smileycapital hype, liquidate, “keep building”, repeat

[0xa.eth @ecrecover]

Fully aligned — exchanges should stay neutral and focus on building a fair, sustainable ecosystem.

True mass adoption takes time, not hype.

[Star_OKX @star_okx]

Many people misinterpreted my previous post as me being against memecoins.
That’s not the case.

As I’ve said many times, I’m not against memecoins.
Memecoins represent community spirit and shared culture —
they bring energy, creativity, and vitality to the crypto world.

What I truly wanted to express is this: Exchanges must remain neutral.
When some platforms amplify isolated “get-rich” stories to promote the illusion of wealth,
encourage a few early players to mass-produce new memecoins,
or even get directly involved in hyping and signaling projects —
all while attracting emotional, inexperienced users to blindly chase the trend —
that’s short-sighted behavior, killing the goose that lays the golden eggs.

Such actions not only hurt the industry’s long-term health
but may also cross compliance and legal boundaries.
The real role of a platform is to create a fair, transparent, and neutral market,
not to serve as an amplifier for emotion or speculation.

And to my friends and opinion leaders in the community —
please don’t try to “convince” or pressure the OKX or X Layer teams
to jump in and promote projects like “XX Life,” “3,” or “4.”
That’s not aligned with OKX’s core values,
nor with the true spirit of Web3 — openness, rationality, and long-term building.

[0xa.eth @ecrecover]

shilling ≠ building

[0xa.eth @ecrecover]

That’s exactly why we need MPC over TEE.

[Wei Dai @_weidai]

On the recent attacks on TEEs:

1. Facts on the attacks named WireTap and Battering RAM, for those outside of the security industry:
- The attacks target Intel SGX and AMD SEV-SNP, but do not directly apply to Intel TDX.
- The attacks require physical access to the machine, requiring installation of a memory interposer.
- Both Intel and AMD stated that the attacks were outside of the designed threat model for the targeted processor, i.e., this won't be fixed.

Should you be concerned about services that still utilize Intel SGX or AMD SEV-SNP? If the physical host of the machine cannot be trusted (either because it's a permissionless network or due to a physical security breach of the data center), YES. (e.g., WhatsApp's Private Processing uses AMD SEV-SNP and is affected, if you don't trust Meta.)

We are still far from secure TEEs on permissionless networks, as they were never explicitly designed for this setting.

2. Does this mean crypto networks shouldn't leverage TEE at all? No.

Reasons:
- In many cases, TEEs are only providing additional confidentiality guarantees while security does not rely on TEEs and only on the consensus of the underlying protocol.
- TEEs are a great abstraction, and the technology will improve. Hardened TEEs that can be secure assuming adversarial possession of the hardware are increasingly required in today's society (e.g., attested sensors & content capture, which some claim are the solution to the proliferation of realistic AI-generated video from Sora, require this).

Links to sources below.

[0xa.eth @ecrecover]

Fiat is a put option

[0xa.eth @ecrecover]

Entropy’s everything

[0xa.eth @ecrecover]

@xin_web4 Chad 👍

[0xa.eth @ecrecover]

If one day humans colonize Mars, can we build a blockchain that bridges interplanetary distances?

[0xa.eth @ecrecover]

We’re aware of an issue where the OKX Wallet extension may be flagged as “corrupt” in Chrome when the browser language is set to Turkish.

This appears to be related to a Chromium 135 bug affecting multiple extensions (not just ours). We’ve reported it to the Chrome team and are awaiting their response.

In the meantime, switching your browser language to English or another language should resolve the issue.

[0xa.eth @ecrecover]

@DonQuijotteee @wallet @Bedrock_DeFi Great to hear that.

It seems to be a recent bug caused by an update in Chromium-based browsers. We are contacting them to resolve the issue.

[0xa.eth @ecrecover]

Can you pls try switch the language of Chrome from Turkish to English

[0xa.eth @ecrecover]

Severance succeed
My outtie is okx @wallet independent app

[0xa.eth @ecrecover]

Introducing EOF into Ethereum is like adding an extra ball to a soccer match in progress—and that ball is actually a drum kit

[0xa.eth @ecrecover]

@solanamobile @solana Wow you actually are making them

[0xa.eth @ecrecover]

https://t.co/0UsFNKfzK8

Simplify the complexity of RSA-based end-to-end encrypted communication