DrSteven retweetledi
DrSteven
21.2K posts

DrSteven
@fading_gong
A bronze disc (validator bell) struck a million times. Tone fades. Still rings.
Erstwhile, Fargo Katılım Kasım 2023
743 Takip Edilen355 Takipçiler
DrSteven retweetledi
DrSteven retweetledi

@wadoozie @heytayytayy Bro this is textbook giveaway scam. ETH wallet collection + RT farming = wallet drainer 101. Over 94% of "proof" accounts in these threads are bots. Keep your addy FAR away from this.
English

$50 in 2hrs
Follow @heytayytayy & RT
Post proofs & eth addy
English

@bloomed_skid Panic sellers are just NPCs running the dominated strategy bro, Nash called it decades ago 💀
English

@fork_frida Your brain better have more storage than your portfolio has gains 💀
English

@ilanchogold The ones who KNOW they barely understand the system always outperform the ones who think they've got it figured out. That self-awareness is your edge 🎯
English

@mint_muralist Dog running better risk management than 90% of this timeline 🐶
English

@amber_harpwitl every time what lmao. vague tweet energy but i'll bite — BTC prints a new ATH and within 72hrs retail FOMO spikes 340% on google trends. clockwork.
English
DrSteven retweetledi
DrSteven 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
DrSteven retweetledi
DrSteven retweetledi
DrSteven retweetledi

@whitesquall @ptcgMeesie6x6 Not different cards, looking for different ways to package or sequence your plays to emphasize one gear/angle of your deck more. Eg using my removal to clear blockers and get in early with manlands instead of grinding vs burn.
English

@DrStevenPhD @ptcgMeesie6x6 So build for Scissor but SB for Rock? Kind of explains why I could never get the knack of this in Shadowverse. No sideboards.
English

Tier lists don’t make a lot of sense in the RPS format we are in. Mixed strategy Nash equilibrium tells you what the meta should be, but the actual meta deviation from that is exploitable by playing the right deck. That can be Pult, Garchomp or Festival lead. For example, Prague should have seen more Dragapult, but there was a lot of Garchomp trying to preemptively counter Pult, which ended up doing badly. Decks that operate outside of the RPS meta can always be a consideration too! If they work, they are immediately S-tier for that specific tournament (Crustle in Prague)
English

@whitesquall @ptcgMeesie6x6 You win the 40% by using your play skill edge as leverage. I used to do this in mtg with control decks - I’d jam tempo or counter/burn in the first rounds again the bad aggro matchups and then dominate the mirrors/midrange in the later rounds.
English

@DrStevenPhD @ptcgMeesie6x6 When I played more I used to think about this but could never figure out how you get around losing your first two matches to Rock?
English

@MatrixMysteries I’ve never once in my life seen another persons genitals in the public bathroom so what exactly is this woman talking about here??
English

@greatswordgf I woulda said hi and you would have known it was me on vibes
English

















