Porto is great for developers of applications, key management services, or wallets.
We have 3 core principles building Porto: 1. Developer-first: Porto works out of the box with Wagmi & Viem.
2. Performance & cost-effectiveness: We redid years of account abstraction research and have state-of-the-art performance and tx latency.
3. Modularity: Porto works standalone, or headless.
Porto works great with OAuth-based key management services, enabling you to upgrade your EOAs into smart contracts using EIP-7702.
For example, if you're a @privy_io user, using Porto headlessly means that you get all the benefits of its backend, without changing anything in how you manage your users or your frontend.
Think of it like another account abstraction provider, but faster, cheaper, feature-rich, and developer-friendly.
Porto's gas usage vs Solady's ERC4337 implementation, which should be the most gas-efficient one in the market (but let us know if this is not right, and we can re-benchmark)!
Well, we're going to prod in the coming weeks, of course.
But beyond that: 1. We are excited to increase the security of Porto Accounts, so that we can conveniently store billions of dollars in them. We have a bug bounty rolling, and we'll continue investing in our security. Note that we're just doing a developer preview today, so we're still early and we're looking for people to work with us.
2. We are excited to solve interoperability at the wallet/application layer. Our ability to modify the stack as we wish will let us do wonders here in the coming weeks.
All of this is powered by a new account abstraction stack, which we just call...the "account". You can learn more in the repository. Make sure to star it!
We haven't yet the fundamental limits of what we can do.
Ethereum should reach the efficient frontier of what’s possible before arguing about how we would choose between our values once we’ve hit those limits.
Shipping faster will help Ethereum get there.
Instead of "should we do X or Y?", the answer might be "both."
We can move faster by deciding to evolve the protocol with ambition, and not ossify.
We can do better than N-of-N (5 CL + 5 EL!) clients coming to consensus before new upgrades.
We can level up ACD.
We can allocate more resources to Devops & Testing.
We started @Ithacaxyz to accelerate the frontier, & have raised $20M from @paradigm.
We’ve been collaborating with the developer community on some of crypto's hardest problems. Small teams = big impact. The future of crypto will be built together.
Over the past four years, our team shipped some of the industry’s most used open source tools like Reth & Foundry.
We believe in sustainable open source development for the good of crypto.
We think the stack is ready, and it’s now time to accelerate.
After almost two years of development and a successful audit by Sigma Prime, we are finally releasing Reth 1.0, the first “prod-ready” release of our blazing-fast Ethereum execution client. We invite RPC providers and stakers to run Reth.
To speed up execution by getting rid of the overheads of bytecode interpretation, inspired by well-established technologies like the Java or the WASM JIT.
Reth AlphaNet is a testnet rollup built on OP Stack & OP Reth.
Reth AlphaNet is aimed at experimentation of Ethereum research at the bleeding edge, and comes with 3 EIPs not available anywhere else yet. EIP-3074, EIP-71212, EIP-2537.
These EIPs are built with best-practices in mind, are optimized, and tested. We want to do more of this.
AlphaNet is also built for high performance, and we aim to break through the gigagas per second barrier with it.