David 🔮

@1xharsh 2

You have a water gun to your head. You have to pick one monke. Only one. Which will it be? [ Culture Monke ]

1/ On the 6529 Network Museum The Memes are a form of decentralized funding protocol - of art, of science, of other things that we want to fund. The selection is fully decentralized and the execution, mostly but not fully decentralized. (For now, someone has to press a Trezor button ultimately for the mint to start, though this will change eventually.) 2/ Is this interesting? Is this just specific to The Memes or is the first example of a broader concept? Well, obviously it is the latter. Today, I would like to propose a second demonstration of something that can be fully decentralized, in this case, a museum 3/ The 6529 Network Museum is a museum that is collectively curated and "owned" by the 6529 network, aka the people who have accrued TDH, aka at a first approximation the meme card holders 4/ By "owned", I mean owned the way the Louvre is owned by the French people, not owned the way I own punk6529. In other words, I mean "held in perpetuity by the network" +/-, on behalf of the network, but not for any particular member of the network (myself included) 5/ The network museum will not as a general rule sell pieces, it will not distribute eth to network members or anything of the sort. It will be a smart contract ultimately that is controlled by the network forever. 6/ For now it is 3 of 5 multi-sig SAFE with 5 of us charged with transitioning in it to the TDH controlled smart contract - @6529er @itsjpower @gratusmasculus and @HugoFaz 7/ Now the interesting question - how do you run a decentralized museum - we have a theory on how to start. @6529er and I submitted a Meme Card today with a proposed theme for the first collection of the Museum. Any money he and I receive if the Meme Card is selected will be used to fund a network selection and acquisition of pieces from artists within the proposed theme. 8/ Whether or not our proposed collection is good will be determined by the network by TDH. If our proposed Meme Card and, by extension, collection is selected, the pieces to be collected will also be selected by the network by TDH. Once they are selected, they will be purchased as newly minted CC0 1/1s for the museum and the meme card will show a compilation of them. 9/ I think (and I apologize in advance for this) that this is pretty smart. It took me me quite a bit of time to figure out how to do this, but I like the outcome. a/ Anyone can submit a Meme Card to do this (and I hope people do) b/ the network decides if they like the collection c/ the network decides what 1 of 1s to buy d/ the artists get a 1 of 1 in an extremely permanent collection and distribution to a larger group via the Meme Card compilation e/ the Meme Card minters get a meme card and an edition of interesting work. 10/ Also, the fact that we are only buying, not selling and not fractionalizing, simplifies many otherwise complex issues. I know this is going to confuse people, but it all depends on how you look at it. The purpose of the network is to perform the functions of the state, not of a private individual or company. 11/ Nobody would expect the Smithsonian to be flipping its pieces on eBay or to give a dividend to every American and so the same logic applies here. 12/ There is more detail here: 6529.io/waves/b6128077… 13/ In any case, we will see how it goes - let's see what the network thinks about all this and if it votes for the card - if so, I think we will learn some interesting things

spent the afternoon with smart, capable non-accelerationist people and, I dunno, I feel like I am living on a different planet than them. for all its flaws, thank god twitter exists.

- Drafted a blog post - Used an LLM to meticulously improve the argument over 4 hours. - Wow, feeling great, it’s so convincing! - Fun idea let’s ask it to argue the opposite. - LLM demolishes the entire argument and convinces me that the opposite is in fact true. - lol The LLMs may elicit an opinion when asked but are extremely competent in arguing almost any direction. This is actually super useful as a tool for forming your own opinions, just make sure to ask different directions and be careful with the sycophancy.

@zigmarillion This is amazing. Honored to have it in my collection!

Really glad to be a part with my art of this amazing initiative by Hugo! My piece Second Dawn reflects how the Phoenix Rises again from the ashes just like Formosa Gallery. A celebration of new and grander beginnings This follows the expression of my new "Carte Blanche" phase that uses inverted double exposure night photography with animation and elements of illustration And thank you to all collectors who supported this project and special shout out to you @DKiblerEspresso who now has this piece in your collection

@1xharsh gm

🌸Epoch 7🌸 - Epoch 6 ✅ - Full update + master plan later today - Concept becomes clearer from here on Epoch 7 is a palate cleanser. One day only. A time to understand Proof of Culture better. Engage today to enter a lucky draw for this 1/1. Say it back. gm 🤍

@1xharsh gm

gm 6.0 day 2/3 paying attention? gm🤍

@1xharsh gm

The Duck Waits, Not Knowing #37 from The Rose Garden Owned by @DKiblerEspresso Gm🤍

Alright folks one last update and a few announcements. From here on out I'll be sending out updates case-by-case. The support continues to be fabulous 🙏 - The first callout by @musicalnetta is coming very soon. Again, follow her to participate - I've created groups for the folks who have pledged financial support to offer our assistance. We need better scaffolding to help collectors along and this is our attempt to do it. - In the next few days I'll be launching the instagram account - @cryptorookie has built a fabulous website almost ready to go. I expect that to launch soon as well Lots more to do.... and here are yet more people who have stepped up: Artist Support: - @NuwanShilpa x.com/NuwanShilpa/st… - @Hadi_art6 x.com/Hadi_art6/stat… - @reylarsdam x.com/reylarsdam/sta… In-kind Support: - @TransientLabs will highlight some of the artists on their site and offer curatorial notes - @whitewallsapp have offered to create a channel specifically dedicated to this curation - @ALLSHIPS will do a feature once a month on the artists The past few days have seen an energy unlike I've seen here since 2021. Only this time it feels organic and real and sustainable. Thank you all for the support! We're pushing this forward and not stopping♥️✊

i am glad this chart is public now because it is bananas. it is ridiculous. it should not exist. it should be taken less as evidence about anthropic's execution or potential and more as evidence about how weird the world we've found ourselves in is.

I'm going to spend $100k this year buying cryptoart from artists trying to get established. It'll come out to around 1E per week. It's not nearly enough but hopefully it helps. @musicalnetta, who is way better at this than I am, will be helping me. Here's how it works:

A lot of people quote tweeted this as 1 year anniversary of vibe coding. Some retrospective - I've had a Twitter account for 17 years now (omg) and I still can't predict my tweet engagement basically at all. This was a shower of thoughts throwaway tweet that I just fired off without thinking but somehow it minted a fitting name at the right moment for something that a lot of people were feeling at the same time, so here we are: vibe coding is now mentioned on my Wikipedia as a major memetic "contribution" and even its article is longer. lol The one thing I'd add is that at the time, LLM capability was low enough that you'd mostly use vibe coding for fun throwaway projects, demos and explorations. It was good fun and it almost worked. Today (1 year later), programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny. The goal is to claim the leverage from the use of agents but without any compromise on the quality of the software. Many people have tried to come up with a better name for this to differentiate it from vibe coding, personally my current favorite "agentic engineering": - "agentic" because the new default is that you are not writing the code directly 99% of the time, you are orchestrating agents who do and acting as oversight. - "engineering" to emphasize that there is an art & science and expertise to it. It's something you can learn and become better at, with its own depth of a different kind. In 2026, we're likely to see continued improvements on both the model layer and the new agent layer. I feel excited about the product of the two and another year of progress.

I'm proud to present the final trailer for An Accursed Share! This is my love letter to our crazy space and the culture we're building, and I'm so grateful to everyone who has supported my work over the years!

Migrating from a platform that went dark? Don’t let your works vanish with it. superrare.com/create → import

Unfortunately, due to its closure, you should withdraw your Masks and Players off of Nifty as soon as possible. There are a few hundred remaining and I would encourage everyone to keep them close for the future. There are a tremendous amount of caring and brilliant people in motion as we speak - in and out, high and low - who are all, off the timeline, answering the bigger questions in the air right now. On our end, we have had a plan in place since we first began The Monument Game as it relates to continuity and media migration that extends through Masquerade. As these conversations unfold, it’s become clear that’s not universal and there are a number of ways our path and learnings will touch the broader preservation efforts. My confident hope is that the work being done and all involved at Nifty and around them can continue to band together to do just that. Anyone that has inquiries on asset withdrawal, please reach out to support@niftygateway.com

NODE exists to serve artists defining digital culture, but major exhibitions only tell part of the story. OCCUPY is our open channel for new and emerging work. A way for artists to get on our radar and access professional-grade infrastructure. If selected, your work runs on our screens at our global headquarters in Palo Alto and you join a network of artists around the world. Learn more: nodefoundation.com/occupy

A few random notes from claude coding quite a bit last few weeks. Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent. IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits. Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased. Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion. Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage. Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building. Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it. Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements. Questions. A few of the questions on my mind: - What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*. - Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro). - What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music? - How much of society is bottlenecked by digital knowledge work? TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.