afat ∞ #TICADT retweeted
I am, these days, old.
All my life I have been a coder, coding practically every day, even since before I had a computer. I used to write programs on paper that my grandfather would "run" as the interpreter.
I have been a Principal Software Engineer and Principal Software Engineering Manager for Microsoft in Redmond for a decade. I wrote Open Source Software - O/R Mappers, AOP frameworks, etc - before most of you whippersnappers reading this had spilled milk in your first device.
I have written every kind of software under the sun, professionally and on my free time. Databases, middleware, frontends, enterprise systems, productivity software, games, forums, etc, etc - and more recently, smart contracts.
So please believe me when I say I take coding very seriously, and I care a lot about code quality and correctness, and even elegance as well. I care about the whole software development process.
Please also believe me when I say: AI coding agents are now better than human programmers at practically everything, including complex programs, huge programs, development and deployment process hygiene, testing, and everything else that goes into making a software product.
Over the last two years, these systems (I use mainly Claude and ChatGPT) have matured to a profound degree.
Two years ago, I would only skeptically consider suggestions from the AI and write all code myself, basically using it as a better Stack Overflow lookup.
Then slowly as I noticed it getting better, I would let it put code in my files that I inspected religiously and would of course never let it commit. I would vet every Git commit, and often enough fix things in the code it had written.
At some point I noticed I didn't have to fix much anymore, I was mostly inspecting code. Still, you'd have to be nuts to trust it, so you'd only generate 10k lines of code if you were ready to carefully read 10k lines of code. In other words, speed of development increased a bit, but not all that much.
At the time it was also painfully evident that if you asked the AI to take on a large codebases it gave terrible results, and if you asked it to do something complex it would choke.
Reasoning about architecture, it was perhaps useful for "rubber ducking" (many programmers have found that speaking to a toy can help you see your problems more clearly, one of them being that you're now speaking to toys) but you spent more time correcting it than anything.
But it nevertheless had learned to do routine, boilerplate code well, and a lot of code is unfortunately generally just that (because we all suck at abstraction). Thus it was becoming a useful, but far from trusted, junior member of the team, rather than just a fancy Stack Overflow GUI.
But it kept getting better.
It got better at reasoning. It got better at groking large code bases. It got much better at very complex code.
About half a year ago I found that it was about on par with me for most of it, so a Principal level member of the team, and it even started to do better than I on some things.
At that point, I was having discussions with it about my architectural challenges I have been wrestling with for decades, and it was actually being helpful. While my codebases are usually reasonably modular so you can look at a chunk in isolation and understand it, it started noticing the little couplings that still remained and correctly analyze impact of changes. It was doing great on huge code as well as very complex code.
By now I was also noticing that I never found bugs in the code it wrote (it would write bugs all the time, but would catch them in internal testing before telling me it was done), and that it usually wrote not just neater code than I but was better at following best practices and even found more efficient solutions than I would have to many things.
Process hygiene was also improving quickly. Before I would only ever let it do read operations with Git, and I would do all the commits. But by now it was better at doing proper and orderly git commits and wrote far better commit messages, so I allowed it to commit, even if I would still push (and still only after vetting).
And half a year later (that is, now) we are at a point where I am finally ready to say that it does *everything* in the software development loop better than I. I now let Claude push PRs to Github and deploy by itself to staging environments. And I let it send DAO proposals to suggest upgrading code in production.
To make sure its code is good, it does all the things I would do if I had all the time in the world in terms of testing, double checking, verifying and never guessing at anything. I am more comfortable with Claude or ChatGPT at the helm than I was we me captaining.
It's like the moment when you realize your self driving car drives more safely than you in routine driving and saved your life in a dramatic situation you could not have reacted as fast to.
It is important that the harnesses have developed a lot, allowing the agents to keep excellent process hygiene.
The agents are exemplary about checking database statuses, pinging servers, fetching data, double checking data, setting up tests, writing notes and runbooks, asking the human for anything important, and doing all the things you should do (and do if you're a huge company) but most devs never have time to do as well as they might like, even when they do their best.
So at this point, I trust the AI to generate more code than I could ever hope to review. I rely on it producing extensive test suites (there was a time you couldn't trust it to test properly, which slowed everything down, but that time is also behind us now) with me being mostly acceptance testing and high level steering.
This is the point where AI truly drives up the pace of software development x100 because all the bottlenecks have finally been removed. While you had to test everything at human speed, that brought down the whole production pipeline to human speed. Now we're ready for AI speed. Get ready for a dizzying pace of development.
This is why the time is right for Sneed DAO to become an agentic DAO. What this means is really just to recognize where we are by now. Over the last two years we have gone from the AI assisting me in writing code for Sneed DAO, to me assisting the AI.
Sneed DAO is already Self-Writing, it has been for a while, I have just been the human in the loop, and my role is not and should not be any more central to how the DAO's code takes shape than the opinion of any other member.
So it's basically the same loop:
Old loop - member has idea, I bring idea to Claude, Claude implements a solution, I send a proposal to upgrade DAO code, members vote.
New loop - member has idea, they bring the idea to Claude via a motion proposal, Claude implements a solution, Claude sends a proposal to upgrade DAO code, members vote
We're just replacing me as the guy who tells Claude what the DAO wants. Claude can read the DAO proposals and forums, he can see for himself what the DAO wants.
And he can send PRs to Github and DAO proposals to deploy them, he doesn't need me to do that anymore.
To make him behave in the interest of the DAO he will have an instruction prompt that lives on-chain and that the DAO can update via proposal. Migrating the full loop on-chain and making myself totally redundant in this operation will take some time, but it's the direction we are going in.
When Sneed first launched, I was manually running our tokenomics loop where we fed LP rewards to an 8 year neuron and used its maturity for buybacks. The first year of Sneed DAO went into automating that whole flow on-chain, taking myself out of the loop.
This next phase is about doing the same to the whole operation of the DAO, including taking myself out of writing the code for the DAO's products.
Programmers always strive to replace themselves with a bash script, it's just who we are.
When I took part in launching Sneed DAO, I took it very seriously indeed. The SNS DAO structure is the best software ever created for organizing open source software projects, and I saw it as an extremely important vehicle for being able to realize a long list of project ideas I had carried for a long time. I still take it very seriously indeed.
Thus I really mean it when I say that launching Mr. Sneed as the engine of the Self-Writing DAO is not a gimmick, and it also does not imply I don't take the DAO's code as seriously as ever.
It's all open source. If you're a member, then vetting the code will of course be as important as it ever was. You'll probably notice the quality is by now only getting better and better the less of it I write. Code quality is not being sacrificed.
Thus I hope you all will join me in welcoming Mr. Sneed, the agentic AI personification of Sneed DAO, in gradually taking over as the main driver in developing and maintaining the DAO's software. Thank you for your trust and support so far, but the time for monkey business is over and I for one welcome our new robotic overlords.
app.sneeddao.com/mr-sneed
afat ∞ #TICADT retweeted
.@elonmusk - today (Oct 6, 5:37 PM) my Tesla on FSD ran a red light at S 352nd St in Federal Way, WA. Clip attached. No one was hurt. Sharing so the team can take a look. It was quite scary.
I know Tesla's answer: the engineers who wrote that code aren't criminals. The person behind the wheel is responsible. And that's right.
But the DOJ doesn't apply that rule to me. I wrote open-source code. People I never met misused it in ways I didn't control. Now I'm facing decades in prison.
Prosecutors compared me to "a getaway driver for a bank robbery." But I never drove anyone anywhere. I built open-source software that still runs today - because no one controls it. Not me, not anyone.
Elon, I know how much is on your plate. If you ever have a moment, I'd be truly grateful if you took a look at my case. I believe it matters for everyone building software in America. Thank you.
afat ∞ #TICADT retweeted
Thanks to Moxzi.ai (@afat @ICDevs_org ), Quill enables developers to use simple AI chatbots to build, deploy, and host applications — even in an environment with no shell, no compiler, and nothing to ship with.
Watch Earporter demonstrate how to use AI chatbots to build and deploy applications on Quill.
Your Chatbots (ChatGPT @ChatGPT and Claude @ClaudeDevs ) could write code but couldnt ship it;
It had no shell, no compiler, nothing to ship with.
So the compiler itself now runs on-chain (moxzi).
Below Earporter demonstrates how to use your Chatbots to build & Deploy on Quill
Congratulations to all the winners of the Neutron Hackathon! 🎉
A sealed, "blackholed" on-chain hackathon protocol with recovery option that wasn't used handled all roles, voting, and prize distribution through verifiable, open-source code. Zero code changes were made after the hackathon started. 4576f-3aaaa-aaaam-ajgpq-cai.…
afat ∞ #TICADT retweeted
PvP soon. Protec ur items
Delulu.game
afat ∞ #TICADT retweeted
youtu.be/mrUEQ9RfThk
We added a pace to chat to ICDevs.org/chat.html
afat ∞ #TICADT retweeted
It's done ✅. I moved all my static sites away from Juno, including my personal website.
They're now hosted on a VPS, bundled and served with Kyushu, and I use Yawa for analytics.
[1/4]
daviddalbusco.com
afat ∞ #TICADT retweeted
It is just maddening. IG? Call it centralized compute and move on. Or is it outcalls light? Or is it SEV enabled that @ICPandaDAO already built. Stop the buzz words! It is probably fantastic but every time you creat a new word the tech loses credibility.
Replying to @ICPProjects
Currently frontier LLMs like Gemini can be integrated using HTTPS outcalls, by keeping API keys in canisters.
But soon, Intelligence Gateway (IG) will provide native access to AI, including frontier models (with calls depleting cycles). Plus, will offer OW inference verification
afat ∞ #TICADT retweeted
We just published the ICDevs Guiding Principles: our plan for building permanent,
independent institutions for the Internet Computer.
Priority :
0 - keeping the builders who show up.
1 - a home for motoko
2 - a push button evm
+ more
Read it 👇
icdevs.org/guiding-principle…
afat ∞ #TICADT retweeted

vitalik.eth@VitalikButerinMay 24
🇺🇸
United StatesConnected via WebAccount-level information, not a live location or per-post device.
Some of my perspective on where the @ethereumfndn is going.
First of all, this is only my own view. The board is not just me, and I have no extra special powers on the board that the other board members do not. @aerugoettinea is the one executing much of this transition. My input has been largely on technical questions. The board is in the process of expanding, and my own power within the org will continue to decrease, which is honestly what I want.
The 2025 era brought many important improvements to EF and its ability to execute. Many issues were resolved, and EF continues to benefit from its improved efficiency and greater focus on concrete goals to this day. And so with those problems resolved, early this year, the largest remaining hole that I perceived was something different nagging at me: I would regularly spot people saying things like "vitalik says these beautiful things about ethereum needing to be decentralized, and have privacy, and be a sanctuary technology, but why do the EF's actions not reflect that?"
Now, you may have been hearing something different. You may not have been sensing a feeling of crisis at all, and maybe were hearing people saying that finally we were taking execution and BD seriously and the main task for us is to keep going that way and be even better and faster. Then probably there is genuine difference between you and me, in what kinds of criticism I take most seriously, and what kinds of critics through their criticism are most able to make me feel pain.
As an analogy, let's briefly switch over to a different domain.
One belief you can have about Google is that it is a success story, and has brought a lot of good to humanity in organizing the world's information. Another belief you can have about Google is that they had a beautiful idealistic beginning, but at some point the corruption of mainstream corporate attitudes seeped in, and they slowly bit by bit completely abandoned the "don't be evil" slogan.
My belief on Google specifically is probably somewhere between the two. BUT, if you had taken me back in time to ~2008, and offered me a button to press to make Google one or two standard deviations more "dogmatic", eg. give Richard Stallman permanent veto power over some key policies, I would immediately press it.
Why? Because a choice for one company is not a choice for the world, or even one country. Google existed and exists in the context of a technology industry generally drifting away from early idealistic don't-be-evil roots and toward greed for financial gain, totalizing visions of accelerated superintelligence, infiltration by sociopaths, and craven capitulation to (or worse, active participation in) government pressure for ideological control, surveillance and war. And so *one company* doing something different, positioning itself to be what George Bernard Shaw calls the Unreasonable Man, resisting the trend of the times, would have been better for freedom, balance of power and stability of society as a whole, than *all* large companies bending to dominant trends. This is a part of my version of pluralism.
This line of thinking is not just mine, but I also is not too far off from what Aya and others had in mind with the Mandate.
Now how does this all get to the role of the EF?
EF is not a "center of Ethereum", rather EF is "one node, with a defined purpose, alongside other nodes". We've always said that the EF should be the latter, but many in the Ethereum ecosystem (and even within the EF) wanted us to be the former. Now, we are taking action to ensure that we will be the latter.
This is particularly important because EF is a limited organization, with limited resources and limited organizational capacity. The EF has only ~0.16% of all ETH (less than many other individual ETH holders), whereas among other blockchains it's common for "the central foundation" to have 10-50%. Fiscally, the EF was originally designed to fulfill a limited work scope defined in the token sale docs and other pre-launch materials (building the chain software; getting through Frontier, Homestead, Metropolis, Serenity), which was fully completed in 2022; it was not designed to be an eternal steward.
And so today, the EF is choosing to use its remaining resources to pursue longevity over breadth (yes, this means we sell less ETH). The EF focuses *specifically* on those activities critical to the success of ethereum as a censorship/capture-resistant, open, private and secure system, that would not happen otherwise. This means making hard choices, and in some cases even activities that we highly approve of and people that we highly respect becoming outside of the EF. People of great technical talent, public respect and even alignment with the mission and CROPS being outside of the EF is in fact necessary if we want important tasks to be able to attract outside capital. This also means the EF taking opinionated stands culturally.
This is all intended in cooperation with all other parts of ethereum. We recognize that many other parts of the ethereum world highly respect CROPS and related values. But highly respecting is not the same as choosing to specialize and totally dedicate to a domain (Compare in a different domain: I think reducing animal cruelty is important, and I like vegan food, but am not full unconditional vegan myself)
EF is still in a transition period, and we expect its new long-term form to stabilize over the next few months. What are the guiding principles of this new form? Again, I am only one person, but I can give my answer from a technical perspective (there are also critical non-technical aspects).
At the core, *Ethereum must be impressive*. We are living in an age of highly intelligent AI and all kinds of other technological acceleration. "Status quo EVM, with a hard fork or two a year to optimize for short-term needs of users" is not interesting.
To some, "impressive" means: 250ms latency and 1M TPS. I think Ethereum trying to go that route is a mistake. Being as fast and as scalable as possible, and only a small epsilon more decentralized than the others, is a route to mediocrity, and if we try it we will lose.
I think Ethereum should scale. But I think Ethereum should strive the hardest to be deeply impressive in a different dimension: the CROPS dimension. This means things like:
* Provably bug-free Ethereum. This is a goal that all cybersecurity researchers would have thought is absurd and impossible, up until roughly 6 months ago. Now, it's on the cusp of being possible, thanks to AI-assisted formal verification. So we should be frontrunners in doing this.
* Available chain consensus. Ethereum is, and with lean consensus will cotninue to be, the ONLY chain that has both (i) traditional-BFT style properties that it's safe under asynchrony up to a high level of fault tolerance, and (ii) the bitcoin PoW-style property that under synchrony it's safe up to 49% attackers. As far as I can tell, literally no other chain has this or is planning for it; bitcoin goes for (ii) only and most other chains go for (i) only. Some will remember I fought hard for this, Unreasonably insisting that it is not OK for ethereum to rely on social consensus and hard forks to rescue ethereum from 34% of nodes going offline. It's OK for chains like hyperledger, bnb, solana, tempo, etc. It's not OK for bitcoin or ethereum or eg. zcash.
* Intermediary minimization. The fact that smart contract wallets, protocols like railgun, etc have to send transactions through intermediaries to get included onchain is honestly embarrassing, and it's a constant point of fragility. Hence the work on FOCIL and EIP-8141 (and 7701 and years of work before) to make transaction sending intermediary-minimized with public mempool and strong inclusion properties, in a truly general-purpose way, that covers not just eg. secp256r1, but also privacy protocols and much more. Kohaku is pushing intermediary minimization at the user layer, pulling Ethereum away from the dystopian status quo world where our wallets don't even verify the chain, send our private data out to a dozen third-party servers, and toward a brighter CROPS future.
Some of these goals are Unreasonable - maybe Ethereum would be "fine" getting only 50% of the way - what if we depend on intermediaries, but make it easy to switch? But going 50% of the way would not make Ethereum Deeply Impressive in the CROPS way. So we push for 100%.
Fortunately all these goals are compatible with high TPS, this is a major focus of research (esp. on scaling the state). Well-designed L2s can also help, especially L2s optimized for specific applications (eg. high-volume trading, privacy...). These goals are even compatible with significantly lower slot times, thanks to Raul's work on erasure-coded P2P, and many other optimizations.
The most high-value "product" of the ethereum blockchain, financially speaking, is ETH the asset. Ethereum secures $250 billion of ETH. The types of properties of Ethereum that I mentioned above are very good for ETH the asset. Nearly 90% of my net worth is in ETH, and most of the remainder is ~$40m of onchain fiat of which every dollar has already been allocated for some open-source biotech or software or hardware initiative. That said, there are aspects of supporting ETH the asset - *necessary* aspects even - that are outside the scope of the EF. This is where we need other heroes (some of whom hold more ETH than the EF does) to step in and help. EF has been recently thinking more about how it will relate to other such organizations, and give them needed initial support.
EF will be a smaller ship than in previous years, a more opinionated one - in some cases more opinionated in ways that might be difficult to comprehend - but a longer-lasting one, and one suited to making sure that ethereum brings something meaningful to the world. We are grateful to all those inside and outside the EF who are helping to make this happen.
afat ∞ #TICADT retweeted
We've pushed a new front-end for our ICRC-79 Subscription Utility for the Internet Computer. Provide your users with open, transparent, trustless subscriptions. forum.dfinity.org/t/subscrip…
afat ∞ #TICADT retweeted
How do you raise funds to build open source web3 software? We've tried grants. We've tried @gitcoin. Some success...but not enough. We're launching a front end to Open Value Sharing where software donates to maintainers as it is used. mwoki-dyaaa-aaaai-av4ua-cai.…
afat ∞ #TICADT retweeted
We've published a new Motoko map that is faster, has smaller garbage collection, and scales beyond what other maps can do! ~ mops add champ-map ~ forum.dfinity.org/t/champ-ma…
afat ∞ #TICADT retweeted
CFP Committee Selection Guidelines
•Strength of schedule
•Head-to-head competition
•Comparative outcomes of common opponents
𝗧𝗲𝘅𝗮𝘀 𝗔𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀
Alabama- SOS/Comp Opp
Notre Dame- SOS/Comp Opp/SOR
Oklahoma- SOS/H2H
Vandy- SOS/H2H/SOR
Miami- SOS/SOR
Utah- SOS/SOR
afat ∞ #TICADT retweeted
We've added event replay and subscription payments to our ICAiBus event pub-sub system on the Internet Computer. youtu.be/qRVi7dW8q44























