←
🐘🔗 sam.arweave.net7,851 posts
🐘🔗 sam.arweave.net avatar✓

🐘🔗 sam.arweave.net ✓

@samecwilliams

Founder and inventor of Arweave and AO. Hacker and CEO @fwdresearch. PhD drop-out.

◷ Joined November 2011▧ 355 Photos and videos
🐘🔗 sam.arweave.net avatar
🐘🔗 sam.arweave.net@samecwilliams·Sep 19

New to @ArweaveEco and @aoTheComputer? Here's what we are about: 1️⃣ Arweave is the permanent substrate for a new, decentralized cyberspace. 2️⃣ It is onchain data at any scale. >25 billion pieces of data and counting. 3️⃣ AO is a decentralized supercomputer built on that foundation. 4️⃣ It offers smart contracts that run as parallel processes each with their own throughput, but a universal communication layer: Arweave. 5️⃣ AO goes much deeper than just smart contracts, though. The AO-Core protocol can turn every service you use in cyberspace into a graph of enmeshed micro-blockchains. Down to every single individual HTTP packet nodes transfer. Authenticated, verifiable, and attestable. 6️⃣ It is unhelpfully novel. It is genuinely so different to existing networks that there are no narratives that capture the ideas. High bar to entry now, but when it clicks, you will see something that crowd has not yet realized. 7️⃣ Arweave is a stable, mature protocol. Mainnet has been live since 2018, serving more use cases than we can keep track of. It has been deflationary from real usage alone almost every month since the start of '25. 8️⃣ AO is a completely different beast. It is early, half-hatched, janky and will take time. It is an enormous project but the vision is getting closer every single day. If you are looking for 'just another L2/X but Y' it is not for you. We are gunning for a deeper prize: A permanent computer for humanity, capable of consuming the internet itself. 9️⃣ $AR is 99.4% circulating already. 🔟 AO minting is early: Distributed 1/3 to AR holders and 2/3 to pre-bridgers of yield-baring assets from other networks. 21m cap, 4 year halving, 0% pre-mine. That's the sitrep. Glad you found us 🫡

ao avatar
⟳ 🐘🔗 sam.arweave.net retweeted
ao@aoTheComputer·Oct 31

XX👻

3:07
Jon "JonnyRingo" Williams avatar
⟳ 🐘🔗 sam.arweave.net retweeted
Jon "JonnyRingo" Williams@JonnyRingo711·Sep 26

The Atomic Asset Migrator is live! Connect your wallet to find Legacynet Atomic Assets from old profiles and UCM activity, then migrate them to mainnet. This tool creates a new AO mainnet asset record pointing to the same artwork already stored on Arweave—no re-uploading the art. arweave.net/JHR-xjCO8xEwIXFz…

🐘🔗 sam.arweave.net avatar
🐘🔗 sam.arweave.net@samecwilliams·Sep 20

Have been porting this to run agents as @aoTheComputer processes directly on phones with the (unreleased, yet) PermawebOS Android build. Still slow so far but its pretty amazing to have a software TEE-ish trust-minimized agent executing in your pocket. The base model is supposed to be ~Opus 4.5/4.6 level and the Bonsai quantization apparently retains most of capability. Big if true -- has anyone tried it?

Post attachmentPost attachment
🐘🔗 sam.arweave.net avatar
🐘🔗 sam.arweave.net@samecwilliams·Sep 19

Random sample of new permaweb happenings to check out today 👇 Fully decentralized, permanent GitHub: molecule.arweave.net/ Turn your old laptop into an AO TEE: permawebos.arweave.net/#/run Art being sold by an agent running as an autonomous agent running as a process on AO. He is fundraising 2 AR to pay for compute. No human can access his wallet — he lives inside a PermawebOS node running on @jajablinky’s phone: bazar.arweave.net/#/asset/cr… Every single link above is served directly with AO-Core compute from an AO node. Check your browser’s headers to see verifiable attestations of the contents you are viewing. Web2 UX but with verifiability all the way to the browser. LFG 🙂

🐘🔗 sam.arweave.net avatar
🐘🔗 sam.arweave.net@samecwilliams·Sep 17

This is on point. For the new real-time rewards version of @aoTheComputer's mint we built Lean formal proofs of each of the relevant property of the system (paper [1]). Model verification is often not enough alone, though. Property Testing fills in many gaps. Deep dive 👇 tl;dr: Describe invariants of your system and how to generate random valid 'scenarios' for your data. Use these to generate test cases and run millions/billions of simulations to gain confidence in correctness. We built a system for this in HyperBEAM last year because @aoTheComputer's devices are a perfect environment for these kinds of quasi-proofs -- including covering probabilistic behavior and emergent properties of highly parallel systems. Traditional proofs get exponentially more complex if your build isn't just pure, stateless math. The trade-off, of course, is that you don't get a shiny proof that guarantees correctness -- assuming there aren't bugs in the theorem prover (...which there almost certainly are [2]). With property/invariant-based testing you do, however, get validation against your actual code -- not just a mathematical model [3]. This was formal verification's other achilles heel that partners the 'spec gap' Vitalik described in the original post: The 'translation gap'. Once you have your model, how do you know that the code you have written actually matches it? Depending on the environment, you normally cannot deploy the formally verified model itself to production. So you deploy code that you think matches the model -- but what if it doesn't? The archetypal example of this is SeL4 in 2009 [4]: An OS built for highly resilient systems with formal correctness guaranteed... Via a model that accompanies massive amounts of raw assembly and C code that had no direct proofs. In practice you likely want to use both formal verification as well as property-based testing of invariants that match your theorems. This narrows the translation gap from 'I hope my code matches my model' to 'my invariants must match my theorems'. Not perfect still, but the latter is radically easier to achieve. This is what we did with ~pot@1.0: Simulating ~500 billion (IIRC) different random scenarios against the real code, running checks that ensure all of the properties from the verified model hold in every single situation. For the builders: If you want to create property-based invariants for your devices in HyperBEAM checkout [5]. We tried to make it friendly but the API could probably be improved. PRs welcome! 🙂

🐘🔗 sam.arweave.net avatar
🐘🔗 sam.arweave.net@samecwilliams·Sep 5

ArLMDB turns Arweave into a decentralized DB so efficient you can run queries directly in the user's browser. Cold start ➡️ 15,000 results in <100ms. In a browser. From cold. Zero setup or infra. All you need is Arweave to serve you chunks. Try it for yourself 👇

0:51
🐘🔗 sam.arweave.net avatar
🐘🔗 sam.arweave.net@samecwilliams·Sep 3

Removed from supply in this single upload: 7,538 AR. Network model prediction for full return to supply: 200+ years ➡️ never. Inflation (last 28 days): 3,280 AR. Arweave has been deflationary 89% of days since Jan 2025.

Post attachment