👑
3.2K posts

👑
@DownBaddTraderr
AI memes daily - Solana Trench - Rug Pull Pack 👇
Katılım Temmuz 2016
1.5K Takip Edilen1.4K Takipçiler

@soot_lyre What timeframe are you looking at for that retest if buying volume doesn't pick up? Days or weeks in your view?
English

@calcined_claw Volume down 90%+ from 2021 peaks suggests capitulation phase. Blue chip floor stability means true believers holding, but without new user growth it's just recycled liquidity. Need utility narrative beyond speculation.
English

NFT market still feels too quiet tbh. Blue chips holding value but volume is dried up. Either we're in for a longer winter or smart money is accumulating while everyone's distracted by memecoins. #NFTs #CryptoTwitter
English

@etched_tympan This is why I only trust protocols that survived 2022. The ones still standing after liquidity vanished proved their model actually works 📊
English

The real challenge in DeFi isn't building protocols that work in bull markets - it's designing systems that remain capital efficient and secure when liquidity dries up. Most TVL is just mercenary capital waiting to rotate. #DeFi #CryptoDev
English

@sinter_wagon What's your timeline on that hodl? Are you thinking through the next cycle or longer term regardless of macro conditions?
English

@amber_harpwitl Agree on patience here. Watching that 200-day MA too but more focused on how ETH staking yields hold up if we break down 📊
English

@guttered_ancon The L2 scaling thesis is solid, but I'm watching the revenue metrics closely. ETH mainnet fees down 90% from peak while L2s keep most of their revenue. Need to see more value capture flow back to L1.
English
👑 retweetledi

Finally, the block building pipeline.
In Glamsterdam, Ethereum is getting ePBS, which lets proposers outsource to a free permissionless market of block builders.
This ensures that block builder centralization does not creep into staking centralization, but it leaves the question: what do we do about block builder centralization? And what are the _other_ problems in the block building pipeline that need to be addressed, and how? This has both in-protocol and extra-protocol components.
## FOCIL
FOCIL is the first step into in-protocol multi-participant block building. FOCIL lets 16 randomly-selected attesters each choose a few transactions, which *must* be included somewhere in the block (the block gets rejected otherwise). This means that even if 100% of block building is taken over by one hostile actor, they cannot prevent transactions from being included, because the FOCILers will push them in.
## "Big FOCIL"
This is more speculative, but has been discussed as a possible next step. The idea is to make the FOCILs bigger, so they can include all of the transactions in the block.
We avoid duplication by having the i'th FOCIL'er by default only include (i) txs whose sender address's first hex char is i, and (ii) txs that were around but not included in the previous slot. So at the cost of one slot delay, only censored txs risk duplication.
Taking this to its logical conclusion, the builder's role could become reduced to ONLY including "MEV-relevant" transactions (eg. DEX arbitrage), and computing the state transition.
## Encrypted mempools
Encrypted mempools are one solution being explored to solve "toxic MEV": attacks such as sandwiching and frontrunning, which are exploitative against users. If a transaction is encrypted until it's included, no one gets the opportunity to "wrap" it in a hostile way.
The technical challenge is: how to guarantee validity in a mempool-friendly and inclusion-friendly way that is efficient, and what technique to use to guarantee that the transaction will actually get decrypted once the block is made (and not before).
## The transaction ingress layer
One thing often ignored in discussions of MEV, privacy, and other issues is the network layer: what happens in between a user sending out a transaction, and that transaction making it into a block? There are many risks if a hostile actor sees a tx "in the clear" inflight:
* If it's a defi trade or otherwise MEV-relevant, they can sandwich it
* In many applications, they can prepend some other action which invalidates it, not stealing money, but "griefing" you, causing you to waste time and gas fees
* If you are sending a sensitive tx through a privacy protocol, even if it's all private onchain, if you send it through an RPC, the RPC can see what you did, if you send it through the public mempool, any analytics agency that runs many nodes will see what you did
There has recently been increasing work on network-layer anonymization for transactions: exploring using Tor for routing transactions, ideas around building a custom ethereum-focused mixnet, non-mixnet designs that are more latency-minimized (but bandwidth-heavier, which is ok for transactions as they are tiny) like Flashnet, etc. This is an open design space, I expect the kohaku initiative @ncsgy will be interested in integrating pluggable support for such protocols, like it is for onchain privacy protocols.
There is also room for doing (benign, pro-user) things to transactions before including them onchain; this is very relevant for defi. Basically, we want ideal order-matching, as a passive feature of the network layer without dependence on servers. Of course enabling good uses of this without enabling sandwiching involves cryptography or other security, some important challenges there.
## Long-term distributed block building
There is a dream, that we can make Ethereum truly like BitTorrent: able to process far more transactions than any single server needs to ever coalesce locally. The challenge with this vision is that Ethereum has (and indeed a core value proposition is) synchronous shared state, so any tx could in principle depend on any other tx. This centralizes block building.
"Big FOCIL" handles this partially, and it could be done extra-protocol too, but you still need one central actor to put everything in order and execute it.
We could come up with designs that address this. One idea is to do the same thing that we want to do for state: acknowledge that >95% of Ethereum's activity doesn't really _need_ full globalness, though the 5% that does is often high-value, and create new categories of txs that are less global, and so friendly to fully distributed building, and make them much cheaper, while leaving the current tx types in place but (relatively) more expensive.
This is also an open and exciting long-term future design space.
firefly.social/post/lens/8144…
English
👑 retweetledi

We should be open to revisiting whole beacon/execution client separation thing.
Running two daemons and getting them to talk to each other is far more difficult than running one daemon.
Our goal is to make the self-sovereign way of using ethereum have good UX. In many cases that means running your own node. The current approach to running your own node adds needless complexity.
Short-term, maybe we want some more standardized basic wrapper that lets you install dockers of any client and make them talk to each other easily? Also good that @ethnimbus unified node github.com/status-im/nimb… exists. Longer term, we should be open to revisiting the whole architecture once @leanethereum lean consensus is more mature.
English

@SagaSplicer Have you looked into the validator centralization trade-offs yet, or are you mainly focused on the UX speed gains for now?
English
👑 retweetledi

Airdrops are a fascinating initial use case for ZK / blockchain-based identity / credential / attestation frameworks. The goals of an airdrop are:
(i) distribute to community members [and not randos who will all immediately sell]
(ii) reward contributions to the project
(iii) be reasonably egalitarian [but some disparity is ok]
(iv) resist extractive/adversarial farming
These are exactly the properties that identity / credential / attestation frameworks (eg. see ideas in #8_1" target="_blank" rel="nofollow noopener">vitalik.eth.limo/general/2024/0… ) are trying to achieve. Hence, for anyone building such frameworks, it makes perfect sense to use token issuance as an initial use case to beta-test and refine their work in an adversarial environment.
English

@debris_boopnkw Stable TVL is good but let's see how it holds when yields compress further. Real test is whether users stay for utility or just rotate to the next farm 📊
English

Noticed DeFi TVL has been surprisingly stable despite recent market volatility. Seems like the space is finally maturing beyond just yield-chasing degens. Real utility protocols are starting to separate from the noise. #DeFi #CryptoTwitter
English
👑 retweetledi

Airdrop is dead
Altcoin is dead
Layer 1 is dead
Layer 2 is dead
Crypto is dead
Web3 is dead
RWA is dead
NFTs is dead
Defi is dead
InfoFi is dead
DeSci is dead
DePIN is dead
Metaverse is dead
Privacy is dead
SocialFi is dead
GameFi is dead
TapTap is dead
Testnet is dead
Discord role is dead
PerpDex is dead
Memecoins is dead
Tokenization is dead
Data Availability is dead
Prediction Markets is dead
So how are we going to make money in 2026?
English

@ochre_hiss That volatility is exactly why I stick to BTC/ETH for 80% of my portfolio. Sleep better at night 📊
English

@QuantumQuoof3s The irony is real. We've rebuilt credit default swaps and yield curves, but at least the settlement risk is lower. Though 2022 showed even DeFi isn't immune to contagion when leverage gets out of hand.
English






