Hank Hodl

Holding since before it was cool. Not financial advice, just stubbornness. 💎

[Hank Hodl @hodlin_hank]

isn't the majority of websites in the world uses php? damn how fked are we?

[Enqrypt @enqrypt_app]

A familiar website can still ask you to sign something dangerous.

The latest PHP security alert is a reminder to review every wallet request.

Here’s where ENQRYPT Guard can help—and why server-side patching still matters. ↓ https://t.co/1M9lSevYqZ

[Enqrypt @enqrypt_app]

A familiar website can still ask you to sign something dangerous.

The latest PHP security alert is a reminder to review every wallet request.

Here’s where ENQRYPT Guard can help—and why server-side patching still matters. ↓ https://t.co/1M9lSevYqZ

[Enqrypt @enqrypt_app]

Meet ENQRYPT Guard.

Understand what your wallet is being asked to approve. Review transactions, signature requests and risky permissions before you sign.

Now available on the Chrome Web Store.z

https://t.co/4odC6eo3ad

[Enqrypt @enqrypt_app]

Before you sign, understand what you’re approving.

Meet ENQRYPT—a workspace for wallet exposure, transaction risk, approval management and encryption.

Hidden information. Visible control.

[Hank Hodl @hodlin_hank]

@enqrypt_app keeping a watch on this

[Enqrypt @enqrypt_app]

Your wallet holds more than assets. It carries permissions, signatures, and a public history.

Meet ENQRYPT. Understand what’s exposed. Review what you sign. Take control.

Hidden information. Visible control.

Read the introduction below. ↓ https://t.co/ruTg08aMty

[SEQLUDE @Seqlude_AI]

$SEQLUDE UPDATE

DEX Screener has been paid for. ✅

We're improving $SEQLUDE's visibility and making it easier for the community to discover and verify our official links.

One step at a time. We're just getting started.

🌐 https://t.co/3Jv8mxeUxk
💬 https://t.co/JJM8Dt1kci

[SEQLUDE @Seqlude_AI]

Direct Utilitarian Tasks:
If you prefer an experience devoid of the specific infrastructure, data collection policies, or ecosystem constraints inherent to OpenAI's platforms.

[SEQLUDE @Seqlude_AI]

$SEQLUDE is live now on #RobinhoodChain

0x0e8d9a881a413a0959f5110d5a65c72420035b7b

secure your private session now!

https://t.co/9pxPLzmLFX

[Hank Hodl @hodlin_hank]

Thisss

[vitalik.eth @VitalikButerin]

Ultimately, precompiles and EVM are both the wrong place to put most cryptography support into Ethereum. The reason is that precompiles and EVM both operate on data that has to be included into the ethereum chain somehow, which realistically means included in a block as calldata. That space is limited - even with PeerDAS and blocks-in-blobs, there's a practical cap of ~8 MB/s before it starts getting uncomfortable.

Remember: it's not a blockchain. It's a cryptographic world computer. Any data/computation that does not need to be in the "main thread" of data/execution should not be put into the main thread.

Instead, the correct solution is... EIP-8288 maximalism.

If you have any heavy computation that's self-contained, compute it and STARK it client-side (this is quickly getting faster and faster, even on phones), and push the STARK through the EIP-8288 recursive aggregation mechanism. The chain sees the fact that the computation was done and what the result is; it never needs to see the actual data and computation.

This way everyone can use whatever cryptography they want, the Ethereum chain can be lean, and we never need to add more precompiles again.