appleajdi (@appleajdi) profile picture
Joined May 2026
Photo by appleajdi (@appleajdi)Photo by appleajdi (@appleajdi)Photo by appleajdi (@appleajdi)Photo by appleajdi (@appleajdi)Photo by appleajdi (@appleajdi)Photo by appleajdi (@appleajdi)Photo by appleajdi (@appleajdi)Photo by appleajdi (@appleajdi)Photo by appleajdi (@appleajdi)Photo by appleajdi (@appleajdi)
Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull. So let me explain some of these buzzwords in more detail. At the core, 8288 is about hyper-scaling data and execution for any computation that needs to get performed on a piece of data once, the chain learns the answer, and then we never need to see that data again. This sounds very specific, but it includes most "heavy" things happening on Ethereum: * Signatures * STARKs * Merkle branches * FHE computation * ... Really the first two are the most important. Once we go quantum-safe, signatures get bigger (65 bytes ECDSA -> 1-6 kB WOTS/SPHINCS depending on params) and ZKPs get much bigger (200-1000 bytes with groth16, PLONK, etc -> 128 kB with STARKs). This is unsustainable to put on chain, and 8288 fixes this. 8288 works by aggregating STARKs in the mempool. First, you as a user generate the STARK or SPHINCS signature or PCS opening (more on that last one later), and publish it. Then, each node listens. Each tick, each node takes all of the new objects that it has seen, and generates a STARK containing a list of "claims": "pubkey P has signed message M" "program X run on data D has output Y" "p(X) = Y for some polynomial P whose hash is H" and a proof that it has seen a signature, STARK or PCS opening verifying those claims. So the only information getting re-broadcasted is: (i) hashes of inputs and outputs (~64-96 bytes per claim) (ii) a single STARK proof per tick These aggregate proofs themselves get re-aggregated, and eventually you get to a single "master proof" in the block, that verifies that all of those statements are true. And so the only other data that has to actually go on chain is the statements (the (P, M), (X, D, Y), (X, Y, H) tuples I described above), not the actual signatures or proofs. This gets put into a specialized frame type. Now, let's get into the leanSPHINCS vs leanSTARK vs leanPCS part. The core distinction is: *what is the underlying object that the user is creating?* In leanSPHINCS, it's a signature, and specifically this particular type of purely-hash-based signature: ethresear.ch/t/sphincs-minus… If we add leanSPHINCS, then users will be able to make quantum-safe accounts, and pay only a little bit of gas (4096 for the 64 bytes) for each signature. So we get scalable quantum-safety for regular accounts, multisigs, etc. But it's only one specific signature scheme, you can't do anything else. In leanSTARK, it's a STARK. This means it's fully general: the user runs whatever computation they want, and publish a STARK of it. So you can use it for: * Any signature scheme (including eg. lattice-based ones if you like those) * A multisig that hides its internal logic * Privacy protocols * Private account abstraction: authorization logic that depends on some value hidden elsewhere in the state, so you can have one key that controls all your accounts without publicly linking them to each other Basically, it's a free for all, in the same way the EVM is a free for all. But leanSTARK has a practical downside. The protocol would have to specify the language in which users write their programs (we call this the "ISA"). So we would have to agree on that language. This is a really big deal - it's the first big case of "Ethereum moving beyond the EVM" - and so it's likely to take time to agree on the details of it, especially since the ISA would be hard to upgrade. There are benefits to taking longer on this, figuring out the ideal ISA, and then even giving access to it inside regular contracts. LeanPCS is the third option. PCS stands for "polynomial commitment scheme": a proof that P(x) = y. The most important thing to know about PCSes is that they are by far the most important "hard" component of a STARK (see here: vitalik.eth.limo/general/202… ). If you have a "magic PCS oracle" (which from the EVM's point of view, 8288 is), you can verify a STARK in ~20-40k gas. The most important gain with PCS is that there is far less that we need to choose. Specifying a PCS only requires specifying a field, and there is a natural option: the 128 bit binary field (technically, we can go more general than that, and say the 2^k-bit binary recursive tower field, going up to 256) LeanPCS is less efficient than leanSTARK onchain, because you would have to put multiple claims to prove one thing. But it's arguably more efficient offchain, because you have much more flexibility to choose proof systems. But most importantly, leanPCS gives you the same generality as leanSTARK, in a way that could potentially be implemented very quickly. And once we figure out the ISA, we can add leanSTARK later. So there is a route to getting "the cryptographic proof singularity" much faster than any of us expected, and that route runs through 8288 with leanPCS. firefly.social/post/x/212092…
278
190
76
1,461
256,337
NEW: @okx CEO @star_okx CALLS OUT @cz_binance "IS THERE ANYONE WHO LIES TO THE PUBLIC MORE SHAMELESSLY THAN THIS—AFTER REPEATEDLY CAUSING MARKET CRASHES EVERY OCTOBER, THEN CLAIMING TO BE RESPONSIBLE FOR PROTECTING THEIR CUSTOMERS...?"
80
142
15
1,189
79,699
appleajdi retweeted
“We’ve never seen price do this before” Genuinely shut the fuck up.
118
125
10
2,466
169,118
this also going to zero lmao
NEW: CMC CRYPTO FEAR & GREED INDEX DROPS TO 15, "EXTREME FEAR" - ITS LOWEST LEVEL SINCE JUNE
7
appleajdi retweeted
CZ be like "ASSETS RESTORED 😂🤣😂🔥🤙🙏😂🤣🔥🤙😂🤣😂 4 🤣🔥😂🤙"
57
116
5
2,222
102,116
btc was bullish during the hack because CZ had to deal with the hack and had no time to max sell btc lmao.
If I had a BTC for every time CT was bullish after a hack this cycle, I'd have two BTC. Which isn't a lot, but it's weird that it happened twice
12
appleajdi retweeted
If you liked $ZEC at $1,200, you'll love it at $850!
26
3
5
202
99,515
Flights grounded, radar down, emails offline, this is the part of the movie where the government finds out a bad actor discovered vulnerabilities in critical infrastructure and is trying to mobilize various resiliency groups in preparation before informing the general population. If you are a woman reading this you need to have sex with me as soon as possible.
9
34
4
673
12,976
appleajdi retweeted
Good decisions compound in trading. Prudent balance sheet and portfolio management = excess capital to capitalize on special situations. Positive trading rPnL = more capital to speculatively hedge and protect downside // crystallize gains. Strict position sizing and risk/leverage controls ensure you can never blow up, always giving you a seat at the table. GOOD TRADES COMPOUND
31
57
4
969
41,144
appleajdi retweeted
Next-generation $NVDA chip
637
3,079
631
27,999
1,091,826
appleajdi retweeted
My GOAT would never bonk a Chinese spy.
267
775
175
11,979
3,657,639
Expanding on why I believe "ETH as store of value (SoV)" makes much more sense to focus on than "ETH as fee-burning token". Three primary reasons: 1. ETH as fee-burning token never was as strong as it seemed 2. Optimizing for ETH as fee-burning token would demand Ethereum and ETH function in ways that are very hard to make compatible with decentralization and capture resistance. 3. Meanwhile, optimizing for ETH as SoV is aligned with Ethereum focusing on its unique strengths (decentralization and CROPS) EIP-1559 (including its burn) is fine and good, we should keep them. But we should not feel sad if fee burn is < 10% of breakeven indefinitely; the value of ETH comes from elsewhere. The core idea: the big thing that people appreciate about Ethereum is decentralization and CROPS. The main pragmatic benefit that these things translate into is stability. SoV is the category where that is not an unneeded extra we merely put effort into for ideological reasons, but rather a pragmatic strength from the perspective of people putting in their assets. And in the era of AI disruption, stability will be highly valued.
1,026
1,169
779
6,941
2,140,431
appleajdi retweeted
I think all of this stuff is actually very simple tbh. You act as a billboard for these coins by retweeting, interacting or hosting spaces etc with the celebrity. Then the coins rug and the celeb or Sahil or whoever makes money. Their plan is obvious: make the coin go up by getting attention to it via you (as you have written and acknowledged, attention is very valuable). Your followers will gamble on stuff that you have mentioned in a hope you’ll mention it again, or that they’ll hit an Iggy-style multiple. And that injection of $ makes it possible for celeb to make 100k or whatever and leave. And, you have been a proponent of select celebrity coins, which endorses a “meta” even without direct endorsement of some coins — since there is no explainable framework where Iggy’s coin is good but Soulja Boy’s is bad. The only difference is how long they are waiting to sell. The answer for you is simple: completely stop interacting with these people in public until you have evidence of good faith — which is likely them taking significant financial risk (eg buying a lot of something) rather than taking zero financial risk (eg only selling something). If you have a large account and a bunch of followers that ape a lot of stuff, unfortunately extractive actors will try to groom you or use you for their own personal gain. It sucks actually, and it’s almost impossible to entirely defend against without becoming a jaded recluse. But celebrities are at least very easy to avoid. If they want to “get into crypto” then they should put $ where their mouth is and buy coins like the rest of us do. That’s what being in crypto is. If they don’t want to do that, ask yourself, why would these celebrities want to suddenly be your friend?
165
63
20
3,237
224,578
appleajdi retweeted
Last time the market didn't properly sell off after a huge event like this was the FTX collapse When I saw the lack of follow through then I got giga bullish And we subsequently went from 16k to 100k Hard to be bearish here after having been given the same setup yet again
463
691
141
9,078
767,639
Replying to @binance
Can i click the link on it? How to trust even he don't trust haha
2
2
60
16,498
appleajdi retweeted
Elon, have a lot of respect for you, but bad time to troll. Please stop. Our SPCX shares (from our $500m investment in your Twitter takeover) are worth more than a billion. Would appreciate if you show a little support. Thanks!
4,843
3,357
2,820
41,006
10,326,468
appleajdi retweeted
The most secure way to store your money in 2026
13
20
1
292
17,142
appleajdi retweeted
Today's my first day at Binance as a DevOps engineer. Everyone has been super welcoming. Bloomberg reached out for an interview and gave me a link for the interview. Couldn't unmute and with their help installed a software to help. Grateful for the warm welcome! Wish me luck!
99
196
27
5,104
207,697
appleajdi retweeted
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified. The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far. Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete. As an immediate precaution, Binance has: - temporarily suspended deposits and withdrawals while security checks are completed; - revoked the affected address authorisation; - engaged law enforcement and blockchain intelligence partners to trace and recover funds. Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice. Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions. binance.com/en/support/annou…
3,394
6,155
3,771
29,543
7,383,251