lihorne
Joined 12 years ago
Karma
170
Submissions
42
Member since
Jan 16
Recent submissions
Comment · 7 months ago
Hey, I'm one of the developers at Tempo. We're working on an extension type for subscriptions to propose being added to the spec as well! We're starting with the simple types, but subscriptions are a natural extension. The subscription intent will work similarly to a one-time charge—the server returns a 402 with intent="subscription", and the client signs a recurring authorization.
Comment · 4 years ago
OP Labs | Remote-first | Full-time
Optimism is an Ethereum scaling solution that enables anyone to execute any vision on an open source protocol that will never be captured by private interests. We’re building this technology as a public good, in order to fundamentally change the relationship between companies and their users.
From code to ethos, we are Ethereum-aligned. By operating as a Public Benefit Corporation, we align private incentives with public good and create a positive-sum economic model that provides a sustainable future for the internet.
Today, the most pressing bottleneck to Ethereum and crypto’s growth is its performance and scalability. We are building the most elegant solution to this problem. We do this out in the open because we believe in open source and its ability to accelerate innovation.
To date, we have raised $178M. Both series A and B were led by Andreessen Horowitz and Paradigm.
We are actively hiring for the roles listed here: All open roles are listed here:
https://boards.greenhouse.io/oplabs
Join us in scaling Ethereum and empowering the creators of public goods! :)
Comment · 4 years ago
OPCraft is an Autonomous World—a fully on-chain virtual space where every single aspect of the World—every river, blade of grass, and patch of snow sitting atop the mountain ranges—exists on-chain, and every single action in the World happens as an Ethereum transaction.
Just like other crafting-based voxel Worlds, you can explore procedurally generated landscapes, mine ores, place materials, and craft new items. Players can create majestic architectures, erect monuments, and terraform the land; either alone or collaboratively.
OPCraft runs on an op-chain; meaning the blockchain is mainly being used towards updating the World as players modify it. Just like a normal rollup, developers can deploy smart contracts on this chain and anyone can run a node in order to access it.
OPCraft’s network runs on Optimism’s OP Stack architecture, with simple adjustments made for higher throughput and shorter block times.
Full writeup here: https://dev.optimism.io/opcraft-autonomous-world/
Comment · 4 years ago
You're right that we could have been better communicators about this. We prioritized our concerns with applications that could break during the upgrade, and we biased our public communications towards developers as a result.
For example, you're right that a notification on our homepage, in addition to our docs, would have been a good reminder to users. We'll work on getting a blog post and better documentation up that explains exactly how to access data from before 11/11. We really appreciate the candid feedback here.
We're a very fast growing startup tackling a herculean task, so we're bound to make mistakes and this is one of them — I hope you can understand. We want to be much better communicators going forward.
Comment · 4 years ago
This is a fantastic question for pretty much every scaling solution out there — as the initial engineering work on rollups finish, many of the fundamental scaling problems re-emerge on L2. Right now, our system's hardware requirements are very similar to L1 mainnet, but the state is growing.
There are two solutions in the future: statelessness, and block-producer/verifier asymmetry. Statelessness (and related concepts like state expiry) has been under active research in Ethereum for years, and we've recently started our own contributions with a new stateless Ethereum client [1]
The other part of the solution is to leverage asymmetries between the hardware requirements of block producers and verifiers. TLDR: this lets you have high HW requirements for sequencers, but still secure the network with laptops. Vitalik recently wrote about this; you can read that here [2]
[1] https://twitter.com/ben_chain/status/1488275978983915523?s=2... [2] https://vitalik.ca/general/2021/12/06/endgame.html
Comment · 4 years ago
The Nov 11 upgrade radically changed how Optimism's backend worked. Transactions after 11/11 are executed in a VM that's much closer to the EVM than before. It's still possible to run nodes that access these pre-11/11 transactions, but because of the way Etherscan and geth are designed, it's unfortunately not as simple as just serving the same data again.
Etherscan CSV exports are the best solution we had that didn't require significant modifications to Etherscan's backend. You should be able to use the CSV feature to export all of your relevant pre-11/11 transaction data (transactions and ERC20/ERC721 transfers).
While we did our best to communicate this months in advance on our twitter, blog, discord, and documentation, it's hard to reach everyone and we totally agree that this is not ideal. At the time, we had to prioritize progress, but we've since made a firm commitment to not to update the chain in this way going forward. So, this shouldn't be something people will need to worry about in the future.
Comment · 4 years ago
Fixed, sorry
Comment · 4 years ago
Hey! Optimism's head of engineering here!
We're super greatful to saurik for writing up such a great analysis of what he found. If you want to hear some of our key takeaways as the maintainers of the network, you can check out our disclosure post here [1].
If you're wondering WTF Optimism is... we are building an optimistic rollup on top of ethereum. The basic idea is to de-couple blockchain computation from data availability and allow a new operator to exist called a sequencer which can accept transaction requests and submit the calldata to Ethereum Mainnet, but do the computation on Optimism Mainnet. There is an idea of a fault proof which means you can verify that the computation done on Optimism Mainnet followed the exact rules of the EVM, and you can prove this on Ethereum Mainnet. Our fault proof codebase, cannon, was built by another jailbreak legend (geohot) precisely with the goal of running Ethereum's battle-tested code and minimize the chances of bugs like this. It's some really cool stuff. If you're into compilers, VMs, and blockchains alike, check it out! [2]
The protocol is still in active development, it is not done yet, and that's exactly why we set up this bug bounty program. We think bug bounties matter, a lot, and we're proud to now become the record holders of the largest bug bounty payout in history, however we hope to very quickly be beaten by someone else. Developers like saurik, who we've gotten to know recently, are super important for this ecosystem to thrive. Building this stuff is hard, and we want the best hackers in the world to get rich breaking these protocols because if we succeed in this industry, this technology will be the backbone of the world's financial infrastructure — it needs to be secure. Everything we write is also MIT licensed and developed completely in the open.
Very happy to answer any questions, I'll check this thread for the rest of the day — AMA :)
Also, we are hiring! [3]
[1] https://optimismpbc.medium.com/disclosure-fixing-a-critical-... [2] https://github.com/ethereum-optimism/cannon/ [3] https://boards.greenhouse.io/optimism
Comment · 6 years ago
The budget concept is a security measure between the app and the wallet, so that the app code only has control over a fixed amount of funds in the wallet.
Within the app context, an unlimited number of channels (up to the budget capacity) can be opened. The video at the top of the blog post is an example of a single user downloading from multiple other leechers & seeders while simultaneously uploading to other leechers.