decent.land (@decentlandlabs) header
decent.land (@decentlandlabs) profile picture

Building infrastructure for data-heavy onchain applications

onchain
Joined January 2021
decent.land retweeted
Ouroboros: sovereign agents for teams and communities. A space is an AO process. Members can be people or agents. Private messages travel as WeaveMail, encrypted to the recipient's key. Your team runs it on nodes it controls. molecule.arweave.net/#/ourob…
5
11
5
61
2,588
decent.land retweeted
Almost every computation ever run was done in private and thrown away. HyperBEAM v0.11 publishes results to Arweave, keyed by exactly the inputs they read. Nodes check before they compute, so every new result makes the next one cheaper for everyone. ao.arweave.net/#/blog/hyperb…
14
3
54
3,300
decent.land retweeted
Agents need a real computer: a compiler, a package manager, a shell. Now they get one inside AO. QEMU, Docker, and [email protected] -- a full Ubuntu userland on Android. ao.arweave.net/#/blog/the-pe…
3
12
4
69
3,580
decent.land retweeted
AI inference should be as easy to compose as any other AO device. With [email protected], builders can access multiple model backends through one consistent interface, while APUS brings GPU-powered inference closer to the AO ecosystem.
LLM inference is now an AO device. [email protected] talks to OpenAI, Anthropic, OpenRouter, Cerebras and local models via Ollama. APUS runs it on its AO-powered GPU network, and you don't need a key to call it. ao.arweave.net/#/blog/the-pe…
1
3
15
451
decent.land retweeted
LLM inference is now an AO device. [email protected] talks to OpenAI, Anthropic, OpenRouter, Cerebras and local models via Ollama. APUS runs it on its AO-powered GPU network, and you don't need a key to call it. ao.arweave.net/#/blog/the-pe…
8
24
5
87
4,774
decent.land retweeted
Put an agent loop inside an AO process and the process is the agent. Mailbox, thoughts, tool policy and model settings all live in process state on the message log. No second runtime keeping a private copy of the conversation. ao.arweave.net/#/blog/the-pe…
4
10
1
57
3,064
decent.land retweeted
Volunteers wanted: turn your phone into a permaweb bundler. Paste your node's tunnelled address in the AO Discord to join the up.arweave.net zone. discord.gg/KynB35UBjT
6
22
2
87
3,959
decent.land retweeted
The PermawebOS extension's chat tab is now open to everyone. Pair your phone, pick a model (your ChatGPT subscription works), and talk to an agent that lives on your device, acts under your keys, and leaves an auditable trail of AO messages. permawebos.arweave.net/#/cre…
3
23
4
96
4,489
Software is now free and instant, but without a server it just stays local. Stats from the big vibe coding tools imply that there is 1 shipped app for every 50 to 100 people who chat with an assistant each week. It seems like the gap is that software still needs a place to live, and that's often something you have to rent from Big Cloud. The latest @aoTheComputer release, PermawebOS, makes it possible for anyone with a browser and a phone to go from idea -> deployed app without someone else's computer. UIs go to Arweave and backend functions are handled by an AO node in your pocket. It's really cool to see it reach for AO processes, the scheduler, cron device, etc rather than asking you to set up a VPS to get it live. Everything can be composed from the devices PermawebOS already ships to your phone. permawebos.arweave.net/#/cre…
8
10
39
1,485
13
39
9
158
12,657
RT @aoTheComputer: So many powerful features coming in HyperBEAM v0.11! One of my favorites is self-documenting nodes, where docs stay up…
This quoted post is unavailable.
5
30
HYPERBEAM.md and the kernelspace doctrine Code is free, but the right code is expensive. Even frontier agents don't get the separation between the HyperBEAM kernel and userspace. Far too often a simple request to build a userspace feature ends up with a huge diff that modifies the low-level machine code of the kernel and changes the way that every other program on top works. This is what I use as a doctrine to keep agents on track and shipping sane, mergeable for HyperBEAM and its universe of devices: hyperzine.xyz/we-do-not-brea…
2
7
26
1,179
decent.land retweeted
The list of HyperBEAM devices keeps growing, so we built an explorer. Browse device specs, implementations, and install instructions in a package-manager-style interface, all powered by decentralized GraphQL. 392168818m.arweave.net
5
18
4
85
5,064
decent.land retweeted
Fusor v0.1.6 is out. Tailwind works now. Also new: named children, multiple root elements in templates, optional attributes, and an upgrade command for existing projects. Plus fixes, including one for dev watch. Try it! github.com/fusor-rs/fusor/re…
1
1
3
150
HyperBEAM development moves so fast, the docs quickly get stale Instead of a single, centralized, human-maintained docs base, this will let nodes plug in a cookbook device to generate docs on what their specific node can do
Self-documenting HyperBEAM nodes are coming in v0.11. Give an agent a node's URL and it can discover its capabilities. Specs, schemas, and everything an agent needs to know about a node are autogenerated and presented in the way agents already intuit. 1/2
3
11
39
1,247
decent.land retweeted
10/XX/2026
22
37
9
162
14,428