I like how the best way to protest this is by doing what everyone should have been doing to begin with: running a great open source model on rented hardware
this is a beautiful attack, the way that multisig signers were compromised with innocuous signatures in advance, without really compromising private keys
from the pre-funding to a virgin address, to the bundler, to the exit strategy to decentralized assets
to the protocols exposed but functioning perfectly under the stress test - props to Jupiter! - and the optional insurance protocols functioning decently, all while people point fingers at Circle for their bridge working perfectly, it's not even clear what people want them to do specifically! All of these aspects of web3 are working great, and it's easy for a cynic that only sees these headlines to miss that
we live in a wholly unoptimized world because the available resources have been so high, while the benefits of optimizing have been so low. that has flipped now and there are tons of low hanging fruit to optimize.
I agree that benchmarks would be great, but thats only relevant to this one topic, not the overall agentic coded pull request concept itself
It's relevant in that it's an example that people are doing the easy part - the coding - and skipping the hard part - the benchmarking and proving it works and provides value.
A PR without evidence it works and expectations for the benefits using the new feature would bring is kind of worthless.
Who says it works if the “author” isn’t thoroughly testing and reviewing it?
People who do this want the fun part of pretending they’re implementing a feature without actually putting in the hard work it takes to make something for real.
They want the repo maintainers to do all the hard, boring parts while they have fun. As if maintainers of open source projects don’t have enough thankless work on their plates. Good luck with that!
reply