kongz

alive

[kongz @0x41A2]

@miguelweb3 Bro you didnt even replied to my dm 😭

[papertrade.xyz @papertrade_xyz]

we are aware of some issues depositing on solana/phantom

our official stance is thats what you get for using solana

[vitalik.eth @VitalikButerin]

I don't recommend anyone scramble to move their funds to new wallets today. But we should take the risks to cryptography from AI-accelerated math seriously, and minimize our exposure to not just quantum-vulnerable cryptography, but also potentially AI-vulnerable cryptography.

The core new area of risk from this viewpoint is, unfortunately, ML-DSA / FHE / lattices.

(and it's also another reason, along with quantum, why ECDSA might fall even faster than expected, hence the "fresh address" recommendation)

So far most people have been in the mode of thinking "elliptic curves broken, hashes safe, lattices safe". But there is a good chance that the concrete security of lattices will take serious hits from the next two years of AI math.

The basic threat model is: factoring is something that naively takes 2^(n/2) time, but over decades smart people have found and optimized number field sieves, and degraded that to 2^O(n^(1/3)), which is why RSA keys and signatures need to be ~400 bytes (and not 64 bytes). What if there are skeletons in the closet like that, both for elliptic curves and lattices, that we are simply not smart enough to discover - but bots soon will be?

This is a major part of the reason why for the past year ethereum's lean roadmap has been going in the "hash-only" direction: no lattices, no ML-DSA, no Falcon, no lattice-based commitments inside ZK proofs, etc. Signatures in lean ethereum are all hash-based, either WOTS or SPHINCS-.

For signatures and proofs, we already know how to go hash-only. The bigger challenge is for *public-key encryption* - and this goes far beyond blockchains. Secure communication, anonymizing protocols, lots of things need public-key encryption.

And unfortunately there are long-standing mathematical theorems showing why public-key encryption cannot be done with hashes alone. You have to have some kind of trapdoor object that has at least one form of usable "structure" - either group theory (incl. isogenies) or lattices or code-based or potentially in the future even more newfangled and spooky things (local mixing?). But for anything that has structure, you should assume that AI will make at least some progress in breaking that structure. Here, one reasonable inference is that if you want to make something plausibly long-term secure, multiply the key sizes by 10.

To me that's a very plausible world and something not at all extreme to predict. If AI will bring us 50 years of math in 2 years, then that 50 years of math may very plausibly include a "naive factoring -> GNFS" level of improvement to our ability to break lattices. In that world, lattices will still exist, but they will have to be significantly bigger to guarantee the same level of safety.

And at those new larger sizes, hash-based constructions will beat lattice-based constructions on concrete efficiency in every use case where hash-based constructions are possible at all.

Theoretically, of course it's possible that hashes are broken too (eg. P = NP would imply that). But I think P = NP is very unlikely. And intuitively, it's much more likely that a mathematical object has exactly no exploitable structure (like hashes are intended to), than that a mathematical object has exactly ~3 forms of exploitable structure (for elliptic curves: associativity, Schoof, pairings) and not some secret fourth form of structure we have not yet discovered that greatly degrades its security (for elliptic curves, ECDLP and pairing security). Similar for LWE, SVP, RLWE and the zoo of lattice problems.

For this reason, we do not yet see any reason to worry and start padding the byte size of hashes (if we start to worry more, we would pad the round count first before doing anything to the byte size).

Concrete TLDR, my own personal views:

* Hash-based > lattice-based, in those situations where hash-based is possible at all
* For anything lattice-based, be much more paranoid on param sizes. Remember that blockchains are only a small portion of the cryptography story; this point goes far beyond blockchains and applies to eg. access to websites, secure messaging, Tor / VPNs ...
* For privacy protocols, strongly favor NOT putting encrypted notes onchain. Instead, send them offchain through some third-party mechanism.
* If it's not difficult for you, keeping your funds in addresses which have not yet been used to make a transaction is a good idea. If it's easy for you, do it. **But be careful about migrations; I personally have lost more money in botched migrations than I have lost in all hacks combined**.
* For multisig wallets, doing confirmations offchain is better than onchain, because this way the signatures of signer wallets do not get exposed to the public, so if ECDSA falls to AI much faster than expected, at least the multisig "gracefully degrades" to a 1-of-1 where the 1 is whoever was gathering the signatures - a much better place to be than "anyone can take the money"
https://t.co/oVjwZog2lL

[kongz @0x41A2]

@0xPolygon oh fuck off

[kongz @0x41A2]

sad but expected

[Abstract @AbstractChain]

https://t.co/0F6yDmUPe5

[kongz @0x41A2]

Signed, sealed, delivered

@fungolabs

[FungoLabs @FungoLabs]

How we use Zama ?

→ Every NFT mints sealed and is encrypted onchain using Zama’s FHE.

→ The contract computes on data it can never read.

→ Its look and essence are determined by FHE randomness. Nobody gets to choose. Not even us.

🟨 Built with FHE on @zama.

[kongz @0x41A2]

@FungoLabs @zama Let’s go!

[Micah @rapidssh]

TL;DR

- RFQ is broken by design: you get a price snapshot that goes stale before you sign.
- SDQ (State-Driven Quoting) flips it: subscribe once, and you get a fresh, ready-to-sign quote whenever a block changes your trade, and nothing when it doesn't.
- It unlocks instant prices, no "confirm again" loops, no polling, and orders, bots and agents that act on the live executable price.
- It's built on Route v2.1, live on https://t.co/v4NT5PX8U8: rewritten in Rust and the fastest on average in our tests against 0x, Velora and KyberSwap, with more output than all three.
- SDQ is live on our partner API for close partners now. DM @rapidssh for early access.

[tanuki42 @tanuki42_]

PSA: On the eve of @token2049 week, please be CAREFUL when talking to people you don't know.

🇰🇵 North Korea has used proxies to socially engineer people in real life at conferences (see $285M Drift hack in April). Others do the same.

Be extremely careful what you disclose.

[kongz @0x41A2]

@Skarly What’s the mint price?

[kongz @0x41A2]

@litocoen @EthenaPay Going to token2049 but it’s still not available in my region!

[kongz @0x41A2]

@ruiontwi @DeltyThe73rd I’m rooting for you 🍀

[kongz @0x41A2]

@JIMMYEDGAR I didnt get anything after sending eth?

[kongz @0x41A2]

@JIMMYEDGAR @X @XMoney 0x41a232db03ce4514bdd5ce3412bd7fc1ec31f8da

[kongz @0x41A2]

@JIMMYEDGAR How is my wallet unconfirmed? 😭

[kongz @0x41A2]

@JIMMYEDGAR https://t.co/Cz6VIWm5KD

Done matey

[kongz @0x41A2]

Go and try Plasma One now!

https://t.co/MnyBRg3qOp

[Plasma @Plasma]

Plasma One is now open to everyone.

[kongz @0x41A2]

Are you ready to make the $JUMP?

Join me on the Jumper waitlist

https://t.co/nEqRiX1hGj

[Jumper @jumperapp]

The ticker is $JUMP
The super-app for onchain finance.