ao

The hyper parallel computer is here.

[ao @aoTheComputer]

LapEE turns abundant consumer hardware into verifiable AO infrastructure.

One of its first jobs: decentralized bundling.

Now permaweb-deploy supports AO bundlers, allowing deployments to route through the emerging network of community-operated bundling nodes.

Another piece of the Permaweb stack decentralized.

Learn More:
https://t.co/ygiVcvwWff

[ao @aoTheComputer]

Did you have a name on ArNS, ANS, or ArProfile?

Your names are now manageable on the new Permaweb Names dashboard!
https://t.co/rAtDoHw0F1

[ao @aoTheComputer]

The first phase of Permaweb Names is live: if you ever owned or rented ArNS, ANS, and ArProfile names you have now received control of an AO message which will allow you to change the data that name points to.

There will be no lease or future registration fees for these names in the future -- they are permanent.

14,624 names from legacy services have now been made resolvable on https://t.co/f2buk8NsKN and other HyperBEAM-powered gateways. Transfers, registrations, and a market will go live in the coming days.

Dashboard: https://t.co/spTOYmHQOx

https://t.co/zaBGWwmt6p

[ao @aoTheComputer]

The first phase of Permaweb Names is live: if you ever owned or rented ArNS, ANS, and ArProfile names you have now received control of an AO message which will allow you to change the data that name points to.

There will be no lease or future registration fees for these names in the future -- they are permanent.

14,624 names from legacy services have now been made resolvable on https://t.co/f2buk8NsKN and other HyperBEAM-powered gateways. Transfers, registrations, and a market will go live in the coming days.

Dashboard: https://t.co/spTOYmHQOx

https://t.co/zaBGWwmt6p

[ao @aoTheComputer]

https://t.co/jHAEvxhNcN

[ao @aoTheComputer]

@opusluxofficial 🤜🤛 BUIDL

[ao @aoTheComputer]

Fire up a LapEE node and put your spare electronics back to work!

That old machine just became part of the decentralized compute swarm on the new internet- The Permaweb Stack.

[ao @aoTheComputer]

Introducing LapEE - the first laptop-native PermawebOS image: boot from USB, run a bundler, and move Arweave uploads toward a decentralized model.

The alpha goes live today.
https://t.co/PJyF18qp1a

[🐘🔗 sam.arweave.dev @samecwilliams]

Running permawebOS

[ao @aoTheComputer]

Introducing LapEE - the first laptop-native PermawebOS image: boot from USB, run a bundler, and move Arweave uploads toward a decentralized model.

The alpha goes live today.
https://t.co/PJyF18qp1a

[xy.ar 🐘 @xylophonezy]

boot from USB -> run a laptop with HyperBEAM as the OS

This $100 laptop is a decentralized bundler, tamper-resistant and provable end-to end

Setup guides (beware, alpha release): https://t.co/CctvXUj9mv

[🐘🔗 sam.arweave.dev @samecwilliams]

Very excited about this launch. Introducing:

➡️ PermawebOS nodes: A bootable, multi-architecture HyperBEAM instance.
➡️ LapEEs: Pretty Good Security via swarms of widely available commodity hardware.
➡️ Decentralized bundlers: A first alpha deployment for LapEEs.

Demanding the most recent high-end server chips or ~$100k as an entry ticket to contribute hardware just isn't a path to decentralized networks.

To actually decentralize the web we are going to need to enable wide participation. The PermawebOS is how we think we get there. Big day 🙂.

To be clear: This is a huge ship and it is definitively, categorically an alpha. We have been running and using LapEEs ourselves at @fwdresearch for weeks, but you shouldn't jump on this today unless you are ready for: A. Nothing to work as you expect. B. The very real possibility that you brick your machine.

Stability and ease-of-use will improve over time, so unless you love self-guided firmware flashing adventures it is best to hang tight for now.

Further down the track, it also looks like Android deployments of the PermawebOS may be possible, too, using kernel software isolation and some of their security hardware. Running a bundler on your phone that you genuinely do not know how to tamper with even if you wanted to is pretty remarkably.

Brick by brick.

[ao @aoTheComputer]

Introducing LapEE - the first laptop-native PermawebOS image: boot from USB, run a bundler, and move Arweave uploads toward a decentralized model.

The alpha goes live today.
https://t.co/PJyF18qp1a

[ao @aoTheComputer]

https://t.co/Vd7mFcjWZj

[ao @aoTheComputer]

https://t.co/Vd7mFcjWZj

[ao @aoTheComputer]

@aoComputerClub 👀

[ao @aoTheComputer]

Forge your custom device and offer your own specialized services through your node!

[🐘🔗 sam.arweave.dev @samecwilliams]

AO devices are like *nix tools: Simple, infinitely remixable, and open for all to build.

This is why you can build things like trust-minimized oracles in a single HTTP URL (yes, really [1]).

But building devices used to suck.

Yesterday, the device forge flipped that. Details👇

[🐘🔗 sam.arweave.dev @samecwilliams]

More tools to build the permaweb faster:

[ao @aoTheComputer]

@ZwigoZwitscher 1. There will be a dashboard at some point for this
2. "Where name claims overlap the following precedence will be used: ANS (an 'Arweave Name Service' from
@DecentLandLabs
🫡), Arweave Account ('ArProfile v3'), ArProfile v2, ArProfile v1."

[ao @aoTheComputer]

Arweave Name System recently announced they are sunsetting, so we are introducing Permaweb Names: a unified, truly decentralized name system. Native on AO, built for the whole Permaweb.

New tokens will be issued to each Arweave name holder on June 1st and automatically setup such that existing names will remain resolvable, ensuring continuity.

Two quick details 👇

1. Permaweb Name sales will be made in AO tokens, with *all* fees going to a protocol balance that will slowly be released to subsidize free, verifiable gateway access for everyone -- with no hidden points of centralization. This was the original vision we pitched for the Arweave Name Service and we are excited to see it run now that verifiable gateways are live.

2. In addition to supporting Arweave Name System name holders affected by the sunset of the service, it is time that the many naming experiments from the permaweb's early years are unified under one autonomous protocol. Where name claims overlap the following precedence will be used: ANS (an 'Arweave Name Service' from @DecentLandLabs 🫡), Arweave Account ('ArProfile v3'), ArProfile v2, ArProfile v1.

Stay tuned for more announcements as the switch-over arrives, but for now: All permaweb names are safu.

[ao @aoTheComputer]

HyperBEAM just underwent a major change, shifting from a monolithic repo to the permaweb's kernel, with hot-loadable devices.

Device Forge makes it easy to ship devices that slot into this minimal core as we build the operating system of the permaweb.

https://t.co/U3yW9tn17D

[ao @aoTheComputer]

https://t.co/QinutxUFeg