Declan Fox

3K posts

Declan Fox banner
Declan Fox

Declan Fox

@DeclanFox14

Building @LineaBuild believe in somETHing

Katılım Haziran 2018
1.2K Takip Edilen21.6K Takipçiler
Declan Fox
Declan Fox@DeclanFox14·
@patron4eg Correct assumption on the liquidity buffer. Security is a number one priority for Yield Boost hence the cautious rollout. We are also monitoring the staking queue closely. Sharplink deposits are in weETH so entirely separate to the native ETH balances on LM.
English
1
4
18
1.7K
PaTRoN
PaTRoN@patron4eg·
Even now, the Linea canonical bridge holds around $120M in ETH, despite the extremely weak crypto market and the currently low activity across the Linea network. You can verify this directly in the contract: 0xd19d4b5d358258f05d7b411e21a1460d11b0876f In my view, the first NativeBoost rewards may appear already in early April. This is because new terms of service come into effect on March 28, where: • all risks related to using NativeBoost are fully transferred to the user • users waive participation in class action lawsuits Legal changes like this are typically introduced right before launching yield-generating financial mechanisms. Now let's estimate what kind of capital flow this could bring to the Linea ecosystem. My assumption is the following: • around 70–80% of the ETH in the canonical bridge will be sent to staking • the remaining funds will act as a liquidity buffer for fast withdrawalsLet's take a conservative scenario. Total ETH in the bridge $120,000,000 Share allocated to staking 70% 120,000,000 × 0.7 = $88,000,000 Current Lido yield is roughly in the range of 2.4% - 3.1% annually Let's take the average value: 2.75% Annual yield 88,000,000 × 0.0275 = $2,420,000 Monthly yield 2,420,000 / 12 ≈ $202,000 So roughly $200k per month could flow into the Linea DeFi ecosystem. For comparison: • current incentives in the network are close to zero • Etherex currently generates around $100k in monthly feesEven if the entire NativeBoost yield were directed only to Aave and Euler, it could significantly increase: - TVL - user activity - trading volumes on Etherex P.S. And all of these calculations assume ETH at $2000. If the ETH price increases, the reward flow will scale accordingly. The remaining key question is:how much of these rewards will be captured by Sharplink, and whether retail users will receive any meaningful share. #LINEA $LINEA #ETHEREX #REX $REX $REX33 #Sharplink @LineaBuild @Sharplink @etherexfi @joechalom
PaTRoN tweet media
English
3
2
23
5.7K
Declan Fox retweetledi
MetaMask 🦊
MetaMask 🦊@MetaMask·
The $LINEA claim window for MetaMask Rewards has come to a close. 🔥 The remaining 380M tokens that were not claimed will be burned. 🔥 Thank you for participating!
English
104
70
643
110.4K
Declan Fox retweetledi
Brian Armstrong
Brian Armstrong@brian_armstrong·
Stablecoin rules in the UK are being finalized, and are at risk of preventing the UK from being globally competitive in the digital economy. For example, the Bank of England is proposing a cap on stablecoin holdings for individuals and businesses. The UK has a long history of being a financial hub. Embracing and encouraging innovation, especially when other countries are moving fast here, is important for maintaining that. The current direction of the rules does the opposite, and will act as an innovation blocker. If you're from the UK you can sign the petition by @StandWCrypto_UK to set out a pro-innovation strategy for blockchain and stablecoins. Link below.
Brian Armstrong tweet media
English
334
617
3K
170.6K
Declan Fox retweetledi
Enterprise Ethereum Alliance | eea.eth
We're thrilled to introduce the EEA Privacy Working Group! This group brings together industry leaders to provide clear guidance on privacy technologies for enterprises deploying on Ethereum and L2s. Initial contributors: > @AppBlockchain > @Consensys @LineaBuild > @COTInetwork > @EYnews (Nightfall) > @0xPolygon > @zksync > @Kaleido_io > @ethereumfndn Covering ZK Proofs, TEEs, MPC, Garbled Circuits, these are real solutions for finance, healthcare and supply chains.
Enterprise Ethereum Alliance | eea.eth tweet media
English
49
62
255
80.8K
Declan Fox retweetledi
joshrudolf.eth
joshrudolf.eth@rudolf6_·
Announcing the Platform team a new team at the EF with one goal: deliver the strongest possible Ethereum platform, where L1 and L2s are best positioned to support users, apps, and all groups building on Ethereum see more in link below & stay tuned for updates 🫡
English
57
55
471
40.5K
Tomasz K. Stańczak
Tomasz K. Stańczak@tkstanczak·
I am stepping down from my co-ED role at the EF at the end of February 2026. Bastian Aue is taking over the co-ED role alongside Hsiao-Wei. The future is bright for builders, for Ethereum, for the EF, and for me. I wrote a longer blog post (link below). I will answer all of your questions here, at ETHDenver, and during podcasts and AMAs that will be there over the next few days. blog.ethereum.org/2026/02/13/tom…
English
298
104
1.3K
501.2K
Declan Fox retweetledi
Linea.eth
Linea.eth@LineaBuild·
At Linea, we don't just use gnark, we build it. Vortex polynomial commitments now benchmarked at: - 3.7× faster than Plonky3 FRI (CPU) - 9.6× GPU boost on commit - 35.8× GPU boost on open Thanks to @AntChainOpenLab for the hardware acceleration work and to our cryptography team @gnark_team.
AntChain OpenLabs@AntChainOpenLab

Gnark-crypto's Vortex commitment is 3.7× faster than Plonky3's FRI PCS. Our Hardware team further improved the performance of Vortex commitment by 9.6× using GPU. Additionally, Vortex's Open was accelerated by 35.8×. @alexand_belling @zkgbo @YaoGalteland @LineaBuild

English
59
51
243
25.1K
Declan Fox retweetledi
Guillaume Dechaux
Guillaume Dechaux@GuiDechaux·
Currently at @DAF_Global, as we further solidify our strategic partnerships and open the gates for new institutions ready to fully commit to the Ethereum & Linea ecosystem. The upside couldn't be more clear on the compounding adoption of institutional-grade trustware
Guillaume Dechaux tweet media
English
8
3
34
1.7K
joshrudolf.eth
joshrudolf.eth@rudolf6_·
1/ never been a better time to build with 🤝🤝🤝 Arbitrum: x.com/sgoldfed/statu… Base: x.com/jessepollak/st… Starknet: x.com/EliBenSasson/s… Linea: x.com/declanfox14/st… Optimism: x.com/karl_dot_tech/…
karl.floersch.eth (✨🔴_🔴✨)@karl_dot_tech

CHALLENGE ACCEPTED. Not a challenge related to drama farmers saying "L2s bad, Ethereum dumb." But instead the challenge of creating a modular L2 Stack that supports and enables customization and the full spectrum of decentralization. And you know -- we're already closer to that reality than you might think. We already have chains built using the OP Stack at Stage 0, Stage 1, and Stage 2. We already have a custom builder API which enables different sequencing rules. You can use ZK proofs you can use fault proofs. It's honestly overwhelming and yet it's just the beginning. But I don't want bull posting to get in the way of the reality. We still have a long way to go to realize the Ethereum vision: * Default withdrawal window from Ethereum is a week! This is insane and a priority. We gotta get that down to an hour or try 10 minutes?! * Stage 2 isn't production ready. We've got a lot of proofs but nothing nearly secure enough to power a major bridge. Aside: I've been advocating for a native eth precompile for rollups for literally almost a decade. Ever since Vitalik posted this: github.com/ethereum/EIPs/… . I guess L1 takes a while to ship features too 😄 just playin ❤️ excited to support it * We still don't have block explorers and developer tooling to enable cross chain applications which makes ecosystem lock-in much more powerful. It's critical that we continue to push the frontier of what is possible and also call out those who don't. There are a few "just a separate L1 with a bridge"s out there. But that's why we just gotta keep our heads down and ship real software. It's a new era. We're bringing Ethereum to the masses with a stack that fits what they need. And we're cooking on gas rn. Alright I gotta get back to the TUI

English
5
7
56
8.1K
Declan Fox
Declan Fox@DeclanFox14·
@gotRekt1337 Yes, that's correct. This is how you get rid of Security Councils, as the SC no longer manages EVM / verifier upgrades.
English
2
0
8
1.1K
GotRekt 小瘋子 (o゜▽゜)o☆
@DeclanFox14 Doesn't that mean though that you'd be integrated into layer 1 basically and could only hard fork in ethereum hard forked? so basically linea wouldn't be an L2 and rather part of the L1 protocol. @DeclanFox14 plz answer
English
1
0
3
1.4K
Declan Fox
Declan Fox@DeclanFox14·
Linea is primed to be the first battle tested Native Rollup technology stack, and we directly support this EIP and direction. We made a unique decision early on to follow the mainline EVM specification exactly with no forks, hence it’s the only L2 stack that an L1 EL client can sync to out of the box! This was extremely challenging with ZK proofs but we stuck to it and now this aligns with the convergence of L1 and L2 and applies nicely to V’s restated vision. First step, Stage 1 zkEVM, which will be rolling out very soon along with other unique Linea features, such as Yield Boost. Let’s keep building!
vitalik.eth@VitalikButerin

There have recently been some discussions on the ongoing role of L2s in the Ethereum ecosystem, especially in the face of two facts: * L2s' progress to stage 2 (and, secondarily, on interop) has been far slower and more difficult than originally expected * L1 itself is scaling, fees are very low, and gaslimits are projected to increase greatly in 2026 Both of these facts, for their own separate reasons, mean that the original vision of L2s and their role in Ethereum no longer makes sense, and we need a new path. First, let us recap the original vision. Ethereum needs to scale. The definition of "Ethereum scaling" is the existence of large quantities of block space that is backed by the full faith and credit of Ethereum - that is, block space where, if you do things (including with ETH) inside that block space, your activities are guaranteed to be valid, uncensored, unreverted, untouched, as long as Ethereum itself functions. If you create a 10000 TPS EVM where its connection to L1 is mediated by a multisig bridge, then you are not scaling Ethereum. This vision no longer makes sense. L1 does not need L2s to be "branded shards", because L1 is itself scaling. And L2s are not able or willing to satisfy the properties that a true "branded shard" would require. I've even seen at least one explicitly saying that they may never want to go beyond stage 1, not just for technical reasons around ZK-EVM safety, but also because their customers' regulatory needs require them to have ultimate control. This may be doing the right thing for your customers. But it should be obvious that if you are doing this, then you are not "scaling Ethereum" in the sense meant by the rollup-centric roadmap. But that's fine! it's fine because Ethereum itself is now scaling directly on L1, with large planned increases to its gas limit this year and the years ahead. We should stop thinking about L2s as literally being "branded shards" of Ethereum, with the social status and responsibilities that this entails. Instead, we can think of L2s as being a full spectrum, which includes both chains backed by the full faith and credit of Ethereum with various unique properties (eg. not just EVM), as well as a whole array of options at different levels of connection to Ethereum, that each person (or bot) is free to care about or not care about depending on their needs. What would I do today if I were an L2? * Identify a value add other than "scaling". Examples: (i) non-EVM specialized features/VMs around privacy, (ii) efficiency specialized around a particular application, (iii) truly extreme levels of scaling that even a greatly expanded L1 will not do, (iv) a totally different design for non-financial applications, eg. social, identity, AI, (v) ultra-low-latency and other sequencing properties, (vi) maybe built-in oracles or decentralized dispute resolution or other "non-computationally-verifiable" features * Be stage 1 at the minimum (otherwise you really are just a separate L1 with a bridge, and you should just call yourself that) if you're doing things with ETH or other ethereum-issued assets * Support maximum interoperability with Ethereum, though this will differ for each one (eg. what if you're not EVM, or even not financial?) From Ethereum's side, over the past few months I've become more convinced of the value of the native rollup precompile, particuarly once we have enshrined ZK-EVM proofs that we need anyway to scale L1. This is a precompile that verifies a ZK-EVM proof, and it's "part of Ethereum", so (i) it auto-upgrades along with Ethereum, and (ii) if the precompile has a bug, Ethereum will hard-fork to fix the bug. The native rollup precompile would make full, security-council-free, EVM verification accessible. We should spend much more time working out how to design it in such a way that if your L2 is "EVM plus other stuff", then the native rollup precompile would verify the EVM, and you only have to bring your own prover for the "other stuff" (eg. Stylus). This might involve a canonical way of exposing a lookup table between contract call inputs and outputs, and letting you provide your own values to the lookup table (that you would prove separately). This would make it easy to have safe, strong, trustless interoperability with Ethereum. It also enables synchronous composability (see: ethresear.ch/t/combining-pr… and ethresear.ch/t/synchronous-… ). And from there, it's each L2's choice exactly what they want to build. Don't just "extend L1", figure out something new to add. This of course means that some will add things that are trust-dependent, or backdoored, or otherwise insecure; this is unavoidable in a permissionless ecosystem where developers have freedom. Our job should make to make it clear to users what guarantees they have, and to build up the strongest Ethereum that we can.

English
127
63
388
53.7K
Declan Fox
Declan Fox@DeclanFox14·
@0xcyp @TimBeiko Removing the need for security councils would be nice from on OpSec pov
English
1
0
4
297
cyp.eth
cyp.eth@0xcyp·
@TimBeiko native rollups need preconfs to be useful preconfs introduce yet another level of centralization and trust thank you for coming to my ted talk
English
2
0
2
529
timbeiko.eth
timbeiko.eth@TimBeiko·
Native rollups are underrated as providing a very clear mental model to users and builders about what part of L2s are actually "secured by Ethereum": the precompile is, and L2s take on the risk (and reward!) for however they want to derive its input and handle its outputs 😄
vitalik.eth@VitalikButerin

There have recently been some discussions on the ongoing role of L2s in the Ethereum ecosystem, especially in the face of two facts: * L2s' progress to stage 2 (and, secondarily, on interop) has been far slower and more difficult than originally expected * L1 itself is scaling, fees are very low, and gaslimits are projected to increase greatly in 2026 Both of these facts, for their own separate reasons, mean that the original vision of L2s and their role in Ethereum no longer makes sense, and we need a new path. First, let us recap the original vision. Ethereum needs to scale. The definition of "Ethereum scaling" is the existence of large quantities of block space that is backed by the full faith and credit of Ethereum - that is, block space where, if you do things (including with ETH) inside that block space, your activities are guaranteed to be valid, uncensored, unreverted, untouched, as long as Ethereum itself functions. If you create a 10000 TPS EVM where its connection to L1 is mediated by a multisig bridge, then you are not scaling Ethereum. This vision no longer makes sense. L1 does not need L2s to be "branded shards", because L1 is itself scaling. And L2s are not able or willing to satisfy the properties that a true "branded shard" would require. I've even seen at least one explicitly saying that they may never want to go beyond stage 1, not just for technical reasons around ZK-EVM safety, but also because their customers' regulatory needs require them to have ultimate control. This may be doing the right thing for your customers. But it should be obvious that if you are doing this, then you are not "scaling Ethereum" in the sense meant by the rollup-centric roadmap. But that's fine! it's fine because Ethereum itself is now scaling directly on L1, with large planned increases to its gas limit this year and the years ahead. We should stop thinking about L2s as literally being "branded shards" of Ethereum, with the social status and responsibilities that this entails. Instead, we can think of L2s as being a full spectrum, which includes both chains backed by the full faith and credit of Ethereum with various unique properties (eg. not just EVM), as well as a whole array of options at different levels of connection to Ethereum, that each person (or bot) is free to care about or not care about depending on their needs. What would I do today if I were an L2? * Identify a value add other than "scaling". Examples: (i) non-EVM specialized features/VMs around privacy, (ii) efficiency specialized around a particular application, (iii) truly extreme levels of scaling that even a greatly expanded L1 will not do, (iv) a totally different design for non-financial applications, eg. social, identity, AI, (v) ultra-low-latency and other sequencing properties, (vi) maybe built-in oracles or decentralized dispute resolution or other "non-computationally-verifiable" features * Be stage 1 at the minimum (otherwise you really are just a separate L1 with a bridge, and you should just call yourself that) if you're doing things with ETH or other ethereum-issued assets * Support maximum interoperability with Ethereum, though this will differ for each one (eg. what if you're not EVM, or even not financial?) From Ethereum's side, over the past few months I've become more convinced of the value of the native rollup precompile, particuarly once we have enshrined ZK-EVM proofs that we need anyway to scale L1. This is a precompile that verifies a ZK-EVM proof, and it's "part of Ethereum", so (i) it auto-upgrades along with Ethereum, and (ii) if the precompile has a bug, Ethereum will hard-fork to fix the bug. The native rollup precompile would make full, security-council-free, EVM verification accessible. We should spend much more time working out how to design it in such a way that if your L2 is "EVM plus other stuff", then the native rollup precompile would verify the EVM, and you only have to bring your own prover for the "other stuff" (eg. Stylus). This might involve a canonical way of exposing a lookup table between contract call inputs and outputs, and letting you provide your own values to the lookup table (that you would prove separately). This would make it easy to have safe, strong, trustless interoperability with Ethereum. It also enables synchronous composability (see: ethresear.ch/t/combining-pr… and ethresear.ch/t/synchronous-… ). And from there, it's each L2's choice exactly what they want to build. Don't just "extend L1", figure out something new to add. This of course means that some will add things that are trust-dependent, or backdoored, or otherwise insecure; this is unavoidable in a permissionless ecosystem where developers have freedom. Our job should make to make it clear to users what guarantees they have, and to build up the strongest Ethereum that we can.

English
14
8
93
9.5K
Odysseus | phylax.systems
Odysseus | phylax.systems@odysseas_eth·
Linea now enables dApps to prevent hacks before they happen. First chain to ever do it. When @DeclanFox14 and I started chatting last summer, I realized how security-focused @LineaBuild is. Phylax is honored to partner with them on their strategic bet in next-generation security. Notably, they are the only network to add security features as a first-class citizen of the chain. This is one of those moments that will change DeFi forever. They realized security has to evolve before mass adoption. They've been having big partners like @SharpLink request security features like this, and recently, Sharplink deployed $170M, underlining their conviction in Linea. Here are a few thoughts on why we built the Credible Layer the way we did: 1. Blockchains are superior financial infra because they settle instantly and permissionlessly. But code isn't law. 2. To keep blockchains safe, we need to give builders a way to prevent outcomes that may be technically accurate, but practically disastrous. 3. The best way to do this is to allow dApps to define what that state unwanted state (hack) is and have the network itself enforce these rules against every transaction. This gives us two things: a) it's trust minimized, and b) it's impossible circumvent. 4. Security doesn't need to be either centralized or hard to do. Both of these suboptimal outcomes are due to the lack of imagination of the current incumbents. From the start, we wanted to build a system that is powerful, transparent, and most importantly: easy to use. We want to commoditize security. Already, we've seen amazing adoption of the Credible Layer in the Linea ecosystem: many of their top dApps are already enforcing assertions, and many more are going live soon. Their feedback has highlighted how differently the Credible Layer approaches security. They have echoed that audits aren't a catch-all solution, and that monitoring doesn't really alleviate anyone's real fears. Being a DeFi developer is actually a very stressful job. Constantly worrying about their contracts and whether they missed something. Not being able to sleep. We frequently forget it's been a rough ride for a lot of the people who have built this industry. And on the capital supply side of the market, the risk-averse participants won't start risking 100% of their capital for a 4%-8% return. The days when DeFi subsidized its way into PMF are long gone. Adoption requires a better risk profile. It requires something from our solution. They need a deterministic guarantee that is underwritten by the uptime of the chain. Determinism is important. You need outcomes that can be expected and attributed to human people, particularly when regulation and compliance are involved. That's what Linea is giving them with the Credible Layer. Essentially, it's a circuit breaker, a mechanism that was introduced to capital markets more than 30 years ago, after the events of the Black Market. Recently, the current administration has been starting to suggest similar systems to be adopted in crypto as well, as they are concerned with the volume of hacks and their use to fund terrorist organizations or state actors. Tradfi enabled circuit breakers for a very similar reason that we are introducing them to blockchains: they needed a mature way to protect capital. In their case, it was against violent market events or manipulation, while in our case is against vulnerabilities or bugs. In TradFi, settlement happens within a few days. Errors are easy (although expensive) to fix. Just roll back the trade, do a couple of meetings, and update the database. Done. Crypto, on the other hand, has instant settlement. It's internet capital markets. The same thing that excites institutions, instant settlement, is also what frightens them. In both cases, though, these systems contributed credibility. Circuit breakers enabled TradFi to become the world-shaping industry it is today. Essentially, circuit breakers, as a mechanism, reduce the likelihood of long tail events. For crypto, that's hacks. But you can't just focus on security. Blockchains have features that must be protected. Because blockchains are decentralized, instant, and permissionless, this means there is no recourse when there is a problem. We were intentional when we built the Credible Layer so that it mitigates the cons without degrading the important features. We'd seen too many other security solutions offerings (most monitoring and ML security tooling released to date) negate these important features by adding a centralized, trusted party to the dApps infra. Nearly to the point that one wonders why such apps are even classified as *decentralized* finance apps to begin with. Most importantly, the Clarity Act has been very clear on this point. For any blockchain to get the benefits of being defined as decentralized, it can't rely on centralized entities. Including centralized security. The solution up to now has been try to find issues (bugs) before they become hacks, and if there is a hack, rollback the chain if you can. But rolling back the chain compromises both decentralization and permissionlessness. We all agree that it should never happen, but we have no recourse when hundreds of millions are on the line. Now we do. And it's being mandated by the government. Here's how I see the future of onchain security looking: dApps write their contracts, define their invariants, and write assertions that are then checked by the network against every transaction. Any transaction that would violate the dApps rules is simply dropped. Bullish Linea.
Linea.eth@LineaBuild

We've integrated the Credible Layer from @phylaxsystems into our sequencer to stop exploits before they execute. This shifts the risk curve, enabling institutions like @SharpLink to deploy more capital into DeFi.

English
45
28
139
21.9K
Declan Fox
Declan Fox@DeclanFox14·
Making decentralized technologies more secure is a top priority for the @LineaBuild team this year. It is painfully obvious we will never expand our industry if businesses and consumers keep getting hacked and exploited. Remember, it was only a few months ago that Balancer was hacked for $120M+ That’s why we decided to partner with @odysseas_eth and the impressive @phylaxsystems team to add the Credible Layer to the Linea Stack (leveraging the @HyperledgerBesu plugin system). Linea Mainnet is the first chain to activate this in production and we’ve already seen a number of DeFi apps write assertions, showing strong signal on the demand from builders. Excited to push the frontier forward on web3 security and see the cumulative amount of user funds we will see protected from hacks using this tech. Stay safe!
Linea.eth@LineaBuild

We've integrated the Credible Layer from @phylaxsystems into our sequencer to stop exploits before they execute. This shifts the risk curve, enabling institutions like @SharpLink to deploy more capital into DeFi.

English
48
16
154
14K
OFFSTAGE
OFFSTAGE@offstage_x·
test
English
293
19
415
32.7K
Declan Fox retweetledi
cyp.eth
cyp.eth@0xcyp·
still fairly good liquid APY on LINEA and you get to earn the yield governance token of the gasless chain and you farm points from native apps i might even kiss you goodnight on your forehead as well karma counts.
Status Network@StatusL2

Reminder that if you have LINEA tokens sitting idle, you could be earning 40%+ APY by pre-depositing them to Status Network. This makes the LINEA pre-deposit vault the first of its kind on Linea, supporting pre-mainnet capital commitment and kickstarting Status Network’s economy and yield governance. status.app/blog/put-your-…

English
22
5
52
6.2K
Declan Fox retweetledi
Enterprise Onchain
Enterprise Onchain@enteronchain·
Casual news..... In 1973, 239 banks created SWIFT. In 2025, SWIFT hired an Ethereum focused company to rebuild it. @Consensys is building the prototype for SWIFT's new blockchain-based ledger. 30+ banks including JPMorgan, HSBC, and Deutsche Bank are collaborating. The first use case: 24/7 real-time cross-border payments. What took blockchain 15 years to prove, traditional finance now considers essential infrastructure.
Enterprise Onchain tweet media
English
28
25
198
20K
Declan Fox retweetledi
Linea.eth
Linea.eth@LineaBuild·
With @SharpLink’s $170M ETH deployment "we're showing how institutions can deploy ETH productively while meeting the security and compliance standards they require." - @DeclanFox14 A meaningful step forward in partnership with @Anchorage, @ether_fi, and @EigenCloud.
Linea.eth tweet media
Sharplink@Sharplink

NEW: We just deployed $170M ETH with first-of-it’s-kind enhanced yield on @LineaBuild. This combines native Ethereum yield, restaking rewards from @eigencloud and direct incentives from @LineaBuild and @ether_fi, all within an institutional-grade qualified custodian thanks to @Anchorage. This is the most productive way to hold ETH with institutional-grade infrastructure. That’s the SharpLink edge.

English
79
137
636
108.1K