So, I've been quietly working on a new project over the last year... and it's time to share a bit about it π
It's time to bring Ethereum back to it's roots, time to bring back the magic that made it so special.
Let me tell you a bit about why I'm so excited about @fuel_network
Ethereum today looks a lot different than when I started.
ETHBerlin 2018 was my first entry into the community. And back then, the community was pretty weird.
A group crazy enough to think they could take on the world's governments, banks, and big corporations.
I fell in love.
This crazyness was what built Ethereum.
People dreamed big, dared to think different.
Not just different from the traditional, non-crypto world, but also from the mainstream crypto community who doubted that Ethereum could live up to it's grand promises.
While most chains were single-purpose, Ethereum put a turing-complete computer on chain!
When nearly every chain was using PoW, Ethereum set out to build the a robust PoS system.
While every chain was trying to have a "fixed supply", Ethereum shifted tokenonomics with EIP-1559.
Today, Ethereum looks very different.
Ethereum secures over $1.5 trillion of assets. Mainstream institutions like Blackrock and PayPal are issuing assets on-chain.
And Ethereum's core development has become slow and conservative, as the L1 approaches it's "final state".
To be clear, this is an incredible success for Ethereum.
Ethereum has delivered on it's vision to be the "foundational layer for financial and non-financial protocols".
Yet this is a classic case of the "innovators dilemma": focus on pleasing existing users & customers kills the innovation cycle, making it vulnerable to disruption.
Like many technologies before it, Ethereum is becoming a victim of it's own success.
Ethereum's modular, rollup-centric roadmap enables permissionless innovation to continue, allowing new L2s to experiment with the the execution layer.
Yet most L2s aim to be as similar to ETH L1 as possible (they're basically all EVMs).
This is where Fuel comes in.
But in many ways, Fuel's doing the exact opposite of most L2 teams.
- Instead of reusing the EVM, Fuel's building a fresh new parallelized VM
- Instead of using accounts, Fuel has UTXOs
- While everyone's doubling-down on ZK, Fuel's pushing "hybrid proving" with fast finality
Some people think these ideas are crazy.
Some people think these designs will slow adoption.
They might be right, but at least Fuel's trying something different.
Doing things the Fuel way.
And as a builder, that's the kind of project I want to be working on.
The most exciting part about working at Fuel has been the freedom to truly reimagine what an Ethereum rollup should look like.
Want to add op-codes to the VM?
Want to change the language syntax?
Want rewrite wallet libraries?
First, a little context:
This week we launched CryptoFlows.info, a site that tracks how value flows between different blockchains and which bridges facilitate this.
We take a wide definition of a "bridge", including fully-custodial assets like WBTC and Binance-Pegged ETH.
When investigating bridged assets on Solana, I was surprised to see that the largest bridge wasn't in fact Wormhole, it was "Sollet".
For example, there's 483,499 soETH on Solana, compared to 26,334 Wormhole ETH.
If this is interesting, make sure you check the full blog post (l2fees.info/blog/rollup-caβ¦). I think this is the first blog post with a built-in dapp!
But for the quick version, keep reading here ‡οΈ
On any blockchain, transaction fees need to pay for 3 resources:
- Execution: the network needs to run your tx
- Storage/state: the network needs to track any updates (token balances, etc)
- Data availability: the network needs to ensure that every node knows about your tx
OpenOrgs launched early this year as a dashboard for showing the largest DAOs by treasury size. But with this update, it can grow into a more all-encompassing hub for all DAOs.
Check out some of the new stuff: ‡οΈ
After OpenOrgs launched last time, many people pointed out that many of these treasuries were mostly their own governance token locked in a vesting contract.
OpenOrgs now splits the "Total Treasury" (which includes vesting tokens) from the Liquid Treasury.
If you expand a row, you can see more details about the treasury, such as the amount of vesting tokens held by a treasury.
It's day 5: the final day of ERC-777 week! π°π
This week we've discussed the pros & cons of the ERC-777 token standard. Today I'll cover things that developers should know about to build with ERC-777, and what the next steps are for this standard.
The most popular of these is permit(), which was originally created for Dai, and popularized in Uniswap V2.
Permit allows a the user to sign a message before their transaction, giving another contract permission to "pull" tokens. This signature gets included in the main tx.
This is a big improvement over the standard ERC-20 behavior.
First of all, users don't need to send an extra approve() transaction, saving them time and money.
Also, users typically don't give infinite approval, which avoids the recent security issues.
With the upcoming launch of optimistic rollups & some recent hacks, it's time to put some focus back on my favorite token standard!
Every day this week, I'll post a thread about ERC-777 and answer any questions about it
Today: an intro to ERC777 ‡οΈ
I like to think of ERC777 as ERC20 2.0
ERC-777 is a standard for fungible tokens, and it's fully backwards-compatible with ERC-20. It works with any existing wallet, but also adds new features.
For more details, check out this thread I made last year: