Eyal Daskal

143 posts

Eyal Daskal banner
Eyal Daskal

Eyal Daskal

@EyDa1510

Founder & CEO @CRYMBO Core banking for crypto Decentralized identity infrastructure Rebuilding financial architecture

London | Tel Aviv Katılım Temmuz 2024
108 Takip Edilen22 Takipçiler
Sabitlenmiş Tweet
Eyal Daskal
Eyal Daskal@EyDa1510·
Crypto did not eliminate banks. It exposed their architecture. The next phase is not DeFi. It is financial infrastructure rebuilt for blockchain execution. Core banking will not disappear. It will be redesigned. Identity will not be optional. It will be embedded at execution. At CRYMBO, we are building the operating system for institutional crypto.
English
0
0
1
55
Eyal Daskal retweetledi
CRYMBO
CRYMBO@crymbotech·
What if tokens could block unauthorized transactions before they finalize? 🛑 At @CrymboTech , our automated KYC queries our oracle to approve or block activity in real-time. This is proactive, on-chain risk management for digital asset issuers and institutions. Watch the clip! 🎥👇 #Crypto #Blockchain #KYC #AI #Agent #Web3Finance @EyDa1510
English
0
1
3
61
Eyal Daskal
Eyal Daskal@EyDa1510·
@StaniKulechov $100M confirms tokenization is now a capital allocation decision, not a pilot. The next constraint isn't liquidity or demand - it's the identity and compliance layer that sits between institutional capital and onchain execution. That's where the real bottleneck is.
English
0
0
0
7
Eyal Daskal
Eyal Daskal@EyDa1510·
@VitalikButerin Finality that means final is exactly what core banking requires. Every legacy system still runs on probabilistic settlement. The moment you can guarantee irreversibility at the protocol layer, you unlock a completely different class of financial products on top.
English
0
0
1
58
vitalik.eth
vitalik.eth@VitalikButerin·
One important technical item that I forgot to mention is the proposed switch from Casper FFG to Minimmit as the finality gadget. To summarize, Casper FFG provides two-round finality: it requires each attester to sign once to "justify" the block, and then again to "finalize" it. Minimmit only requires one round. In exchange, Minimmit's fault tolerance (in our parametrization) drops to 17%, compared to Casper FFG's 33%. Within Ethereum consensus discussions, I have always been the security assumptions hawk: I've insisted on getting to the theoretical bound of 49% fault tolerance under synchrony, kept pushing for 51% attack recovery gadgets, came up with DAS to make data availability checks dishonest-majority-resistant, etc. But I am fine with Minimmit's properties, in fact even enthusiastic in some respects. In this post, I will explain why. Let's lay out the exact security properties of both 3SF (not the current beacon chain, which is needlessly weak in many ways, but the ideal 3SF) and Minimmit. "Synchronous network" means "network latency less than 1/4 slot or so", "asynchronous network" means "potentially very high latency, even some nodes go offline for hours at a time". The percentages ("attacker has <33%") refer to percentages of active staked ETH. ## Properties of 3SF Synchronous network case: * Attacker has p < 33%: nothing bad happens * 33% < p < 50%: attacker can stop finality (at the cost of losing massive funds via inactivity leak), but the chain keeps progressing normally * 50% < p < 67%: attacker can censor or revert the chain, but cannot revert finality. If an attacker censors, good guys can self-organize, they can stop contributing to a censoring chain, and do a "minority soft fork" * p > 67%: attacker can finalize things at will, much harder for good guys to do minority soft fork Asynchronous network case: * Attacker has p < 33%: cannot revert finality * p > 33%: can revert finality, at the cost of losing massive funds via slashing ## Properties of Minimmit Synchronous network case: * Attacker has p < 17%: nothing bad happens * 17% < p < 50%: attacker can stop finality (at the cost of losing massive funds via inactivity leak), but the chain keeps progressing normally * 50% < p < 83%: attacker can censor or revert the chain, but cannot revert finality. If an attacker censors, good guys can self-organize, they can stop contributing to a censoring chain, and do a "minority soft fork" * p > 83%: attacker can finalize things at will, much harder for good guys to do minority soft fork Asynchronous network case: * Attacker has p < 17%: cannot revert finality * p > 17%: can revert finality, at the cost of losing massive funds via slashing I actually think that the latter is a better tradeoff. Here's my reasoning why: * The worst kind of attack is actually not finality reversion, it's censorship. The reason is that finality reversion creates massive publicly available evidence that can be used to immediately cost the attacker millions of ETH (ie. billions of dollars), whereas censorship requires social coordination to get around * In both of the above, a censorship attack requires 50% * A censorship attack becomes *much harder* to coordinate around when the censoring attacker can unilaterally finalize (ie. >67% in 3SF, >83% in Minimmit). If they can't, then if the good guys counter-coordinate, you get two non-finalizing chains dueling for a few days, and users can pick on. If they can, then there's no natural schelling point to coordinate soft-forking * In the case of a client bug, the worst thing that can happen is finalizing something bugged. In 3SF, you only need 67% of clients to share a bug for it to finalize, in Minimmit, you need 83%. Basicallly, Minimmit maximizes the set of situations that "default to two chains dueling each other", and that is actually a much healthier and much more recoverable outcome than "the wrong thing finalizing". We want finality to mean final. So in situations of uncertainty (whether attacks or software bugs), we should be more okay with having periods of hours or days where the chain does not finalize, and instead progresses based on the fork choice rule. This gives us time to think and make sure which chain is correct. Also, I think the "33% slashed to revert finality" of 3SF is overkill. If there is even eg. 15 million ETH staking, then that's 5M ($10B) slashed to revert the chain once. If you had $10B, and you are willing to commit mayhem of a type that violates many countries' computer hacking laws, there are FAR BETTER ways to spend it than to attack a chain. Even if your goal is breaking Ethereum, there are far better attack vectors. And so if we have the baseline guarantee of >= 17% slashed to revert finality (which Minimmit provides), we should judge the two systems from there based on their other properties - where, for the reasons I described above, I think Minimmit performs better.
vitalik.eth@VitalikButerin

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
239
107
848
266.7K
Eyal Daskal
Eyal Daskal@EyDa1510·
@paoloardoino Dollars moving outside traditional rails isn't a crypto story - it's a financial architecture story. The institutions that capture it won't be the ones holding USDT. They'll be the ones running the infrastructure that issues, settles, and accounts for it natively.
English
0
0
0
12
Paolo Ardoino 🤖
Paolo Ardoino 🤖@paoloardoino·
Tether just released its quarterly attestation for Q4 2025. Tether had a great year, surpassing 10B in profits. USDT expanded throughout the year by 50 billion, because global demand for dollars is increasingly moving outside traditional banking rails, particularly in regions where financial systems are slow, fragmented, or inaccessible. USDT, with its network effect and parabolic growth, has become the most widely adopted monetary social network in the history of humanity. Highlights as of 31 December 2025: * 186.5B total issued USDT, end of Q4 2025. * 192.8B total assets/reserves, end of Q4 2025. * 6.3B+ excess reserves, on top of the 100% reserves in liquid assets that back all issued tokens, end of Q4 2025. * 141B+ in US treasuries (direct + indirect exposure), end of Q4 2025. * 50B USDT supply increase in 2025 Tether proprietary investment portfolio exceeds $20 billion. Thank you very much for the continued support ❤️
Tether@tether

Tether Delivers $10B+ Profits in 2025, $6.3B in Excess Reserves, and Record $141 billion Exposure in U.S. Treasury Holdings Learn more: tether.io/news/tether-de…

English
142
170
1.3K
278.8K
Eyal Daskal
Eyal Daskal@EyDa1510·
@paoloardoino Dollars moving outside traditional rails isn't a crypto story - it's a financial architecture story. The institutions that capture it won't be the ones holding USDT. They'll be the ones running the infrastructure that issues, settles, and accounts for it natively.
English
0
0
0
9
Eyal Daskal
Eyal Daskal@EyDa1510·
@SteakhouseFi @block_stories The shift from "should we?" to "how do we deploy?" is where the infrastructure gap gets expensive. Most institutions find the missing piece isn't the vault - it's the core banking layer connecting it to their compliance, treasury, and reporting stack.
English
0
0
0
14
Steakhouse Financial
Steakhouse Financial@SteakhouseFi·
The conversation has shifted from "should we?" to "how do we deploy?" Last week Steakhouse featured at @block_stories Horizon Frankfurt, walking the room through how DeFi vaults enable financial institutions to capture onchain yield.
Steakhouse Financial tweet mediaSteakhouse Financial tweet media
English
11
11
37
4.8K
Eyal Daskal
Eyal Daskal@EyDa1510·
@arc @USDC AI agents don't need new financial products. They need rails that are programmable, instant, and identity-aware. Stablecoin settlement is layer one. Identity at the transaction level is the layer most builders haven't touched yet.
English
0
0
0
32
Arc
Arc@arc·
AI agents are learning what markets have always required: a reliable, low-cost, trusted medium of exchange. Increasingly, that infrastructure is being built on blockchains. And it’s happening with @USDC.
English
48
47
329
42.4K
Eyal Daskal
Eyal Daskal@EyDa1510·
ask "how do we deploy?" - the missing piece isn't the vault. It's the core banking layer connecting it to their compliance, treasury, and reporting stack. That's where most deployments stall.
English
0
1
1
50
Eyal Daskal
Eyal Daskal@EyDa1510·
The infrastructure question is the right one. AI agents don't need new financial products - they need rails that are programmable, instant, and identity-aware. Stablecoin settlement is the first layer. Identity verification at the transaction level is the next one most builders haven't solved yet.
English
0
0
0
67
Eyal Daskal
Eyal Daskal@EyDa1510·
Core banking was designed for a world with one type of money. That world is ending. The institutions moving fastest right now are the ones rebuilding their financial architecture - not patching it.
English
0
2
1
59
Eyal Daskal
Eyal Daskal@EyDa1510·
@MilkRoad @Bitwise The market missed it because stablecoins at scale still hit the same wall. Who holds the account? Who verifies the identity? Who manages the off-ramp? 3 billion wallets is a distribution problem solved. The banking layer beneath it is not.
English
0
0
0
3
Milk Road
Milk Road@MilkRoad·
Matt Hougan @bitwise: This should have been MASSIVE. But no one cared. "Meta announced it was rolling out stablecoins across 3B people... 3B people who are going to have crypto wallets in a year! ... and the price is like, meh."
Milk Road@MilkRoad

BREAKING: Meta is said to be bringing stablecoin payments to Instagram, WhatsApp, and Facebook. They're reported to have just sent out an RFP for stablecoin payment infrastructure. Translation: they’re quietly shopping for a third-party partner to help launch stablecoin payments to its 3B+ users. (With integration apparently targeted for early H2 2025.) If you’ve been around long enough, you’ll know that Meta tried this before and got destroyed. In 2019, they announced Libra (later renamed Diem) but regulators crushed it. Congress hauled Zuck in for hearings, and the project died a whimpering death in 2022. Now they're back, but with a completely different approach. Here's what's changed: They're not building their own stablecoin this time, they're partnering with existing infrastructure - with Stripe as the leading candidate (according to sources). Which makes sense. Stripe acquired Bridge (the stablecoin platform) in late 2024. Plus - Stripe's CEO, Patrick Collison, joined Meta's board in April 2025. So those pieces are already in place. This could be big for crypto and Meta users alike. Stablecoin payments across WhatsApp, Instagram, and Facebook would give users access to instant cross-border transfers without traditional banking fees. While providing the crypto sector with 3B+ (potential) new users, almost instantly. That’s the kind of distribution that changes adoption curves - FAST.

English
18
22
118
35.9K
Eyal Daskal
Eyal Daskal@EyDa1510·
@BlackRock Tokenization is the headline. The real work is one layer down. Identity, accounts, compliance logic - still off-chain, still closed. Until that changes, you have not moved the system. You have rebranded it.
English
0
0
0
46
BlackRock
BlackRock@BlackRock·
Tokenization has the potential to transform how securities are issued, traded and settled, creating a more efficient financial system. #QuestionOfTheWeek: Near-term, tokenization will grow most 👇
English
55
26
138
27.9K
Eyal Daskal
Eyal Daskal@EyDa1510·
@brian_armstrong Updating financial services is the application layer. The infrastructure layer - core banking, identity, account architecture - still needs to be rebuilt natively for crypto. That is where the next phase of institutional adoption will be won or lost.
English
0
0
0
7
Brian Armstrong
Brian Armstrong@brian_armstrong·
It’s earnings day. 2025 was a strong year for Coinbase, and we built a solid foundation for continued growth in 2026. Our thesis is actually very simple: crypto is updating all financial services, and we're the best positioned company to capitalize on this transformation. Some highlights: - Total trading volume grew 156% Y/Y and our crypto trading market share doubled in 2025 - Assets on Coinbase increased 3x over the last 3 years - We now have 12 products generating >$100M of revenue on an annualized basis - New all time highs in USDC and Coinbase One Onwards
English
476
230
1.5K
243.4K
Eyal Daskal
Eyal Daskal@EyDa1510·
The long game is infrastructure, not applications. The institutions building on-chain today are discovering that execution rails exist but the banking layer beneath them does not. Identity, accounts, compliance logic - these are the primitives that will determine who wins the long game.
English
0
0
0
6
Eyal Daskal
Eyal Daskal@EyDa1510·
@solana @solanapayments $2 trillion in stablecoin transfers proves the settlement layer works. The next question is what sits above it - account architecture, identity, compliance logic. Payments scale. Banking infrastructure for crypto is still being built.
English
0
0
1
58
Eyal Daskal
Eyal Daskal@EyDa1510·
@SuperstateInc @FT @TheBanker @FWDind @rleshner @solana US equities as DeFi collateral is the proof of concept. The harder problem is the identity and account infrastructure underneath - who holds, who clears, who is accountable. RWA execution is solved faster than the compliance architecture that should sit beneath it.
English
0
0
0
7
Superstate
Superstate@SuperstateInc·
1/ NEW: @FT @TheBanker just published a piece on @FWDind making history, featuring interviews with Forward and @rleshner. Quick summary: Forward became the first US public company to have its equity used directly in DeFi on @Solana, enabled by Superstate.
English
4
16
10
3.4K
Eyal Daskal
Eyal Daskal@EyDa1510·
Banks are not afraid of crypto. They are afraid of rebuilding their core infrastructure to support it. That fear is justified. The architecture question is real. Most are still looking for a shortcut that does not exist.
English
1
1
1
87
Eyal Daskal retweetledi
CRYMBO
CRYMBO@crymbotech·
Finance is entering its own Year of the Horse. Capital is moving differently. Institutions are stepping forward. Digital assets are no longer experimental, they’re infrastructural. But movement without structure collapses. Speed without trust breaks. The next era of blockchain won’t be defined by speculation. It will be defined by certainty. When value moves on-chain, identity must move with it.
English
0
1
2
47