Crypto’s Killer Use Case
- Tik Tok is to Media as Crypto is to Money
- In-wallet FYP + prediction markets
- The "flippening" of Web2 to Web3
- Instagram on crypto rails?
- Realistically "onboarding the next B"
Berachain: Memetic Playground or DeFi Utopia?
Will Berachain get rekt by impermanent loss?
Is the community worth anything?
Is the tech actually anything novel?…
As a former Bera naysayer, I wanted to share some thoughts on what changed my mind:
1/ An Honest Overview of Onchain FHE:
While I believe FHE will change the fabric of all compute, I wanted to shed some light on the challenges of building a *complete FHE system.
1/ The videos are up from “Beyond the Block" MEV research day with
@titanbuilderxyz
. The line-up of speakers were incredible, introducing many new ideas and concepts. Here is a recap thread
1/ 🪄SC Wallets: Redefining Web3 UX 🪄
This is the (in)complete guide to:
- What is an EOA, SC Wallet & ERC-4337
- Why EOAs threaten the future of blockchain
- What is Account Abstraction?
- Tying it together: SC Wallet, ERC-4337 & AA
- AA on Layer 2s
Reminder that Tron has over $57B worth of stablecoins, predominately held by people in emerging markets
The chain sucks: high txn fees, centralized af (27 validators), terrible UX, limited DeFi etc.
How is there not a single L1 or L2 mission-driven to compete for this market??
5/ The use of ZKPs leans into an interesting topic around where to build an FHE application: Either an FHE powered L1, FHE Rollup or use an FHE coprocessor.
@Maddiaa0
and
@Janmajaya_mall
's private auction and SherLOCKED by
@NitanshuL
are recent implementations of a coprocessor
10/ “L1 Preconfirmations” by
@MuratLite
explores a new fulfillment consortium model to achieve preconfs without validator participation. MEV-commit is a network to play “fast games” and do real-time bidding and commitments for preconfs
10/ If you’d like to further explore the nuances of onchain FHE, feel free to check out an article co-written by
@hu_zhiwei
and I covering more topics such as Programmable Bootstrapping, FHE DA Layer etc.
We welcome all feedback & collaboration :)
@awasunyin
Now tech is mature enuff, I’m certain we’ll see a rise in VC backed, verticalized payment solutions
Publisher-exchanges in Web2 and Web3 will lead the demand for robust payment rails, it’s up to us to build them
2/ “From Solver Markets to Builder Subsidy War” by
@sui414
&
@0xangelfish
explores the emergence of specialized markets for integrated liquidity and routing, and the subsequent centralization concerns. Next, Danning breaks down the 2023 builder subsidy war
7/ “Onchain Solving” by
@ThogardPvP
explores smart contract-based solving. There are many benefits including reorg protection, no builder reliance, atomic composability, no reliance on simulations etc. Very underrated topic imo
3/ A few improvements can be made:
(1) Enable an n/2 threshold which would make it more difficult to collude
(2) Run the threshold decryption protocol inside of an HSM
(3) Use a TEE-based threshold decryption network
Or use MPC instead to secure the private key and decrypt
6/ Another option is FHE rollups by Fhenix. Although FHE encrypted data is complex, recently the team at Fhenix demonstrated how to achieve fraud proofs using the Arbitrum Nitro stack paired with FHE logic compilation to WebAssembly
FHE rollups or coprocessors >> FHE L1s
5/ “Towards Competitive Preconfirmation Markets” by
@ksrini_
provides an overview of preconf designs. He also covers the last look problem, cross-rollup MEV and "intra-app interop," where apps can give non-contentious preconfs based on app-specific logic
2/ Challenge
#1
: Secure Threshold Decryption
Every confidential, shared state system is predicated upon an enc/dec key. As such, we are bound to trust a threshold committee.
So what happens if the threshold nodes collude?
They could silently decrypt any data & user inputs‼️
9/ “Based EigenLayer” by
@0xkydo
provides a simple framework for based preconfirmations. We need restaking in order to slash malicious proposers, preconfers and/or builders. Probably the best intro to preconfs I've seen
11/ “How Super Builders Unlock Shared Sequencer Superpowers” by
@Jskybowen
provides an overview of shared sequencing architecture, and the importance of “super builders” i.e the entity that is economically incentivized to support atomic interop
4/ Challenge
#2
: How do we use FHE Trustlessly?
While FHE enables the processing of encrypted data, it cannot verify correctness of either user inputs or computation.
Hence, we need ZKPs in order to use FHE in a trustless environment. So how do ZKPs + FHE fit together:
Current observations of 4844 show blob propagation latency introduces reorg risk to builders w no incentive. Esp during MEV spikes, builders will likely opt to censor blob txns. Looking forward to seeing how preconfs can offer rollups more reliable inclusion
📢We uncover the role of preconfirmations in EIP-4844 in our latest research, “Censorship, Latency, and Preconfirmations in the Blob Market" surfacing the implications of the blob market shift. 🧵 [1/6]
8/ “The Rise of the Sophisticated Proposer” by
@DrewVdW
@ViktorBunin
@flevestanagan
@plc_hld
@ernopp
delves into the mind of a node operator. They share thoughts on everything from timing games, risk profiling, restaking, vertical integration, DVT etc.
6/ “Execution Tickets” by
@mikeneuder
defines the shortcomings of PBS including warping validator economics, timing games, censorship etc. Execution tickets can fix validator economics, remove rugpooling etc. Phenomenal overview of the design by Mike
7/ Challenge
#3
: FHE Hardware
Existing hardware is not suitable for FHE at scale.
The limitation stems from the massive interaction with the memory and the overhead incurred from the complex polynomial computations and time consuming ciphertext maintenance operations
@MikeIppolito_
I'd argue the only person w enough practical perspective to share in depth here is
@MuratLite
.
@primev_xyz
also happens to be the *only preconf network on testnet
3/ “State of Privacy in the Txn Supply Chain” by
@GuyZys
@ravitals
@maccanomics
@0xbyyou
discusses private mempools, private auctions, collaborative block building, etc. The panel also addresses the shortcomings of FHE and possible mitigators
8/ Possible future directions to improve hardware:
- Processing-in-memory to overcome "memory wall"
- Hybrid software/hardware co-design approach
- Networking FHE Accelerators: The shift from scale-up to scale-out
And much more...
4/ “Structural Analysis of MEV Boost Auctions” by
@MaxResnick1
formally examines the MEV Boost auction. Takeaway: When some bidders are strong relative to others, first-price sealed-bid auctions may generate higher revenue
@FrankieIsLost
fr. builders can j censor blobs during MEV spikes + validator timing games can "force" builders to censor bc of additional reorg risk. Fire article on the topic:
5/ SC wallets were created to undertake many of the issues associated with EOAs. The inherent programmability of smart contracts makes it possible for wallets to have far more advanced features and overall UX compared to their EOA counterpart. SCW transaction lifecycle:
@plc_hld
Completely agree. Countless use cases: blob settlement, bridging preconfs, searcher preconfs etc.
Think it’s the next logical evolution to combat the natural limitations of the ETH txn supply chain
3/ If you’ve transacted on Ethereum before, odds are you’ve used popular wallets such as MetaMask, Rainbow, imToken, etc. These EOA wallets have onboarded tens of millions of users over the years, forming the Ethereum ecosystem as we know it today. EOA transaction lifecycle:
6/ Drafted in September 2021, ERC-4337 is the latest effort towards improving SCWs. ERC-4337 makes creating and using SCWs considerably easier by streamlining and consolidating the on and off-chain infra used during the process. ERC-4337 transaction lifecycle:
@0xMert_
Any form of high freq, real-time payments
Ex. Real-time interest payments on escrowed funds that update every second, payments via interactive ad network frames, new data orchestration layer that can reward contributions at a more granular level etc.
NEW POD: Restaking & Shared Security Lessons Learned
@MikeIppolito_
,
@MylesOneil
, and
@VelvetMilkman
unpack:
- Intersection of restaking and shared security
- Lessons learned from Cosmos and Polkadot
- LSTs vs. LRTs
- Emergence of Solana L2s
@MaanavKhaitan
preconfs can provide guarantees around inclusion, not finality. Preconf networks can deal w reorgs in a number of ways- re-submit txn, preconf insurance etc. CC
@MuratLite
@lmrankhan
Completely agree!
Crypto payment rails enable bi-directional payment flows that can tightly couple money and attention. The net new publisher-exchange experiences we create will be the “killer app” imo
4/ It’s important to highlight a key design choice of EOAs regarding how the account (the object holding your digital assets) and the signer (the object which grants control over your assets) are basically one and the same. This hard-coded logic in the EVM results in:
13/ To summarize, I hope it’s clear that EOAs are harmful to the growth of the broader crypto ecosystem. Fortunately, SCWs provide an alternative account structure that allows for the exceptional scaling of self-custody conducive to the average Web2 user.
11/ How do SCWs, ERC-4337 & AA relate?
SCWs separate the acc and signer. (Unlike EOAs)
ERC-4337 advances SCWs by making it significantly easier to create and operate an SCW.
AA turns all accounts into nearly indistinguishable SCWs- Becoming a first class citizen!
10/ The shift to AA eliminates EOAs and makes SCWs first class citizens. Unlike today, where dApps need to implement support for ERC-1271 to allow SCWs to transact with a given dApp. Thus, SCWs are an after thought in dApp design decisions, a major challenge for SCW providers.
@binji_x
4844 is def a massive reduction in DA cost. However for timely inclusion, rollups will need to pay a priority fee via preconfs, esp during MEV spikes imo
9/ Moving onto Account Abstraction. AA is an effort to embed SCWs into the core blockchain protocol. This merges features of both EOAs and SCWs into a single account type (SCWs) that can initiate transactions and pay gas fees along with the advanced functionalities of SCWs.
@kyle_corsola
@colludingnode
@cryptodavidw
Tbh I don't understand the discussion here
- Onchain FHE *needs ZK to work. So the framing of FHE or ZK is wrong
- While FHE is the endgame of privacy imo, it will take time. Threshold assumption, data blow-up etc.
- Using ZK, MPC and/or TEEs is necessary for now
7/ Why are SCWs a 100x improvement?
SCWs offer infinitely more powerful features than EOAs, conducive to Web2 users. To name a few:
- Social Recovery
- Multicall
- Fraud Monitering
- Tiered Permissions
- Mobile Biometric Authentication
- Session Keys
and many more on the way!
8/ To recap, so far we've covered: What is an EOA + SCW, the limitations of EOAs, why SCWs present a new era of usability and security and how ERC-4337 advances SCWs. Lastly, I wanted to summarize the fundamental differences between EOAs and SCWs on Ethereum:
12/ AA on Layer2s:
L2s have the opportunity to launch with native AA and forego EOAs altogether. Thus, L2s are a premier testing ground for wallet developers to continue expanding the functionality that can be provided by SCWs. zkSync and Starknet are implementing native AA.
2/ There are two kinds of Ethereum accounts, EOAs and SC wallets. EOAs are controlled by users with their private key where a signature from the private key is needed to transact. SCWs are controlled by smart contracts where successful execution of the code is needed to transact.