Native Restaking is What Makes Restaking Permissionless.
When we first started building EigenLayer, an LST protocol wanted us to exclude native restaking and accept only LSTs.
Back then, EigenLayer was just an idea with zero TVL, and Sreeram was tirelessly advocating our vision on podcasts.
The proposal, at the time, seemed irresistible: quicker market entry and 70% fewer engineering challenges, as native restaking posed most of the technical hurdles.
It was a difficult decision, but we declined.
Native restaking is the lifeblood of Permissionless Restaking. Accepting the LST-only offer would alienate solo stakers and all those wanting control over their validators, shifting a large stake percentage to existing LSTs.
Despite the complexity of the LST dominance issue, excluding non-LST stakers would definitely harm the Ethereum community in the long term.
In hindsight, rejecting the offer was our best decision, staying true to our belief that any Ethereum validator, regardless of their operator affiliation or stake origin, should and could participate in restaking.
Permissionless Restaking.
As for Permissionless Staking (staking other ERC-20 tokens), the EigenLayer protocol is general-purpose and can accept any ERC-20 asset as stake.
Flexibility is Permissionless Restaking + Permissionless Staking. Don't let others tell you otherwise.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I have figured out why the concept of ShS is so confusing to me.
My confusion stems from the fact that:
Unlike in Ethereum, in the modular stack, the tx root and state root are proposed (computed) separately.
TLDR: ShS is the correct term 🫡
In Ethereum, when the proposer proposes a block, it includes both the transaction root and the state root. Then every other validator will attest to both roots at the same time till it reaches finality.
Now, imagine in Ethereum, we remove the EVM, and the proposer only proposes the tx root. What do you get? You get an expensive "DA+storage" L1.
First, unlike centralized sequencers Arb and OP use today, shared sequencers do not guarantee the actual transaction execution ordering. At least, in its current modular (lazyledger-based) form.
1. Non-native staking and its security analysis. 2. Postions are non-fungible -> liquidity unification methods? 3. Liveness of AVSs 4. What does a decentralized sequence with EL look like? 5. Event-driven MEV -> blockspace subscription?
...
This article is tailored for crypto game (GameFi) builders ⚒️and advisors👩💼. It is the longest piece we have written and the estimated reading time is 25 mins. So, maybe save the article now and read it on a sunny afternoon later.
We will provide a short summary in this thread👇
👀Introduction👀
Crypto game developers have been focusing on ways to generate demand and decrease supply. The most common way is through adding gold skins and new features.
We took another angle and looked for ways to optimize the transfer of value within these systems.