# Device Proshop: every HyperBEAM device, explained, plus what is being built and what is wanted > Source of truth for this file: https://deviceproshop.xyz/blocks.json (snapshot of HyperBEAM edge: 2026-09-21; file generated 2026-10-29). > Machine access: https://deviceproshop.xyz/llms.txt (index), https://deviceproshop.xyz/blocks.json (catalog), MCP endpoint at https://deviceproshop.xyz/mcp (tools: search_devices, get_device, list_builds, list_in_the_works, plan_node, request_device, how_to_build_a_device), skill at https://deviceproshop.xyz/agent/SKILL.md. ## What AO and HyperBEAM are, in one paragraph AO is a decentralized computer built on Arweave's permanent storage. HyperBEAM is the node software. It is built from small modules called devices. Each device does one job (order messages, run code, charge for work, keep secrets). A node is a chain of devices that a message flows through in order. Anyone can publish a new device with the Forge toolchain and other node operators can install it by name. Real device names look like `~process@1.0`; every device below also has a plain-terms nickname. ## Families - Run: Devices that do the actual work. - Pay: Devices that handle money and fairness. - Protect: Devices that keep things safe and locked. - Store: Devices that remember and save things. - Connect: Devices that talk to the outside world. - Find: Devices that search and look things up. - Tools: Devices that help builders build. ## The everyday loop Cron wakes the process. The process hands the job to Lua. Lua's answer goes out with Push. ## Devices (from HyperBEAM edge and published Forge packages; one is marked as coming back soon) ### ~process@1.0 (Process; in plain terms, The Memory Keeper) - id: process - family: Store. Devices that remember and save things. - status: built into HyperBEAM - job: Remembers everything that has ever happened to it. - explainer: A process is like a notebook that never loses a page. Every message sent to it gets written down in order, and it can always replay the notebook from the start to figure out what it knows right now. That's how a game, a token, or a chat room on AO keeps its state. It doesn't do the thinking itself. It hands the work to Lua or WASM and the ordering to Scheduler. - for example: A bank statement. Every transaction is listed in order, and you can always add them up to get today's balance. - works with: scheduler, lua, wasm64, stack, push, cron, patch - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/process/dev_process.erl ### ~scheduler@1.0 (Scheduler; in plain terms, The Line Keeper) - id: scheduler - family: Run. Devices that do the actual work. - status: built into HyperBEAM - job: Puts every message in line so nobody cuts. - explainer: When lots of people send messages to the same process at the same time, somebody has to decide who goes first. Scheduler gives every message a number (0, 1, 2, 3) and signs it so everyone agrees on the order. Without this, two nodes could replay the same notebook and get different answers. - for example: The ticket machine at the DMV. Everyone gets a number, and numbers are served in order. - works with: process, push - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/process/dev_scheduler.erl ### ~lua@5.3a (Lua; in plain terms, The Quick Worker) - id: lua - family: Run. Devices that do the actual work. - status: built into HyperBEAM - job: Runs small scripts fast. - explainer: Lua is a tiny, friendly programming language. This device reads a Lua script and runs it against a message. Many new HyperBEAM processes use this Worker because it's quick to write and easy to read. It can also call other devices while it works. - for example: A pocket calculator that can follow a short set of instructions. - works with: process, stack - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/vm/dev_lua.erl ### ~wasm-64@1.0 (WASM; in plain terms, The Heavy Worker) - id: wasm64 - family: Run. Devices that do the actual work. - status: built into HyperBEAM - job: Runs big programs written in almost any language. - explainer: WebAssembly (WASM) is a way to pack up a program written in Rust, C, Go, or lots of other languages so it runs the same everywhere. This Worker runs those packed programs. It's what you use when the job is too big for a Lua script. - for example: A shipping container. Pack the program once, and it runs the same on any dock. - works with: process, stack, wasi, json-iface - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/vm/dev_wasm.erl ### ~stack@1.0 (Stack; in plain terms, The Assembly Line) - id: stack - family: Run. Devices that do the actual work. - status: built into HyperBEAM - job: Chains devices together so each one does its step. - explainer: Stack takes a list of devices and runs them one after another, passing the result down the line. That's how a process can say 'first check for duplicates, then run my Lua, then tidy up the output' without anyone writing glue code. It's the device that makes the device idea work. - for example: An assembly line: prime, paint, then polish, in that order every time. - works with: process, lua, wasm64, dedup, multipass, patch - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/util/dev_stack.erl ### ~push@1.0 (Push; in plain terms, The Mail Carrier) - id: push - family: Connect. Devices that talk to the outside world. - status: built into HyperBEAM - job: Delivers a process's replies to whoever they're for. - explainer: When a process finishes a job, it often has messages for other processes ('tell the token to move 5 coins'). Push picks those up and delivers them, then delivers any replies to those, and keeps going until the mailbag is empty. - for example: A courier who delivers a reply, then delivers the reply to that, until nothing is left in the bag. - works with: process, scheduler - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/process/dev_push.erl ### ~cron@1.0 (Cron; in plain terms, The Alarm Clock) - id: cron - family: Run. Devices that do the actual work. - status: built into HyperBEAM - job: Wakes a process up on a schedule. - explainer: Normally a process only does something when someone sends it a message. Cron sends it a message on a timer, every minute, every hour, whenever you say, so it can check prices, clean up, or pay out on its own. - for example: A thermostat that checks the temperature every ten minutes, whether or not anyone is home. - works with: process, scheduler - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/node/dev_cron.erl ### ~relay@1.0 (Relay; in plain terms, The Messenger) - id: relay - family: Connect. Devices that talk to the outside world. - status: built into HyperBEAM - job: Runs to the normal internet and back. - explainer: AO lives in its own world, but sometimes you need a weather report or a price from a regular website. Relay makes the web request for you and brings back the answer. It can wait for the reply ('call') or just drop the message and leave ('cast'). - for example: The colleague who walks over to the other office, asks the question, and comes back with the answer. - works with: router, arweave - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/util/dev_relay.erl ### ~meta@1.0 (Meta; in plain terms, The Receptionist) - id: meta - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Greets every visitor and tells them what this node can do. - explainer: Every request to a node walks in through Meta first. It knows the node's settings (which devices are installed, who owns it, what it charges) and it can run checks before and after a request (that's where Rate limit and P4 plug in). Ask it '/~meta@1.0/info' and it tells you about the node. - for example: The front desk. Every visitor checks in there first and is told what the building offers. - works with: p4, rate-limit, blacklist, auth-hook - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/node/dev_meta.erl ### ~p4@1.0 (P4 payments; in plain terms, The Ticket Booth) - id: p4 - family: Pay. Devices that handle money and fairness. - status: built into HyperBEAM - job: Pay first, then you get in. - explainer: P4 is how a node charges for its work. It asks a pricing device 'how much should this cost?' and a ledger device 'does this person have enough?' and then lets the request through or turns it away. Swap the pricing or ledger device and you've got a whole new business model without touching anything else. - for example: The turnstile at a stadium. Valid ticket, you're in. No ticket, you're not. - works with: metering, simple-pay, faff, recharging-ledger, pricing-router - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/payment/dev_p4.erl ### ~metering@1.0 (Metering; in plain terms, The Electricity Meter) - id: metering - family: Pay. Devices that handle money and fairness. - status: built into HyperBEAM - job: Counts exactly how much of the node you used. - explainer: Instead of a flat price, Metering watches a request while it runs and counts things: bytes in, bytes out, how hard the computer worked. Then it multiplies by the operator's rates. Plug it into P4 and people pay for exactly what they used. - for example: The electricity meter on the side of a house. You pay for what you actually used. - works with: p4 - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/payment/dev_metering.erl ### ~simple-pay@1.0 (Simple pay; in plain terms, The Price Tag) - id: simple-pay - family: Pay. Devices that handle money and fairness. - status: built into HyperBEAM - job: A set price per message or per route. - explainer: The simplest way to charge: the operator sets a price per message, or a fixed price for certain routes, and the node keeps track of what each user has paid. Good for getting started. - for example: A price tag. One number, no surprises. - works with: p4 - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/payment/dev_simple_pay.erl ### ~faff@1.0 (Faff allowlist; in plain terms, The Guest List) - id: faff - family: Pay. Devices that handle money and fairness. - status: built into HyperBEAM - job: Only friends and family get in, and it's free. - explainer: Faff is a pricing device that doesn't charge anything. It just checks whether you're on the operator's list. If you are, come on in. If not, no. Handy when you run a node for yourself and don't want strangers using it. - for example: A guest list at the door. Your name's on it or it isn't, and nobody pays. - works with: p4 - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/payment/dev_faff.erl ### ~rate-limit@1.0 (Rate limit; in plain terms, The Bouncer) - id: rate-limit - family: Protect. Devices that keep things safe and locked. - status: built into HyperBEAM - job: "You've had enough. Come back later." - explainer: Every visitor gets a bucket of allowed requests that refills over time. Ask too fast and Rate limit says 429 ('slow down') until your bucket refills. Keep hammering and your bucket goes negative, so you wait even longer. It stops one person from hogging the whole node. - for example: A coffee shop that serves one order per person at a time. Ask again in a minute. - works with: meta - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/node/dev_rate_limit.erl ### ~blacklist@1.0 (Blacklist; in plain terms, The Gatekeeper) - id: blacklist - family: Protect. Devices that keep things safe and locked. - status: built into HyperBEAM - job: Keeps a list of stuff that's not allowed on this node. - explainer: The operator points Blacklist at one or more lists of banned IDs. Any request touching something on the list gets blocked. Every node picks its own lists. There's no central boss, so each operator decides what they will and won't serve. - for example: A no-fly list. Each airport keeps its own, and nobody makes them share. - works with: meta, cron - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/node/dev_blacklist.erl ### ~secret@1.0 (Secret; in plain terms, The Locker) - id: secret - family: Protect. Devices that keep things safe and locked. - status: built into HyperBEAM - job: Keeps your key safe so you don't have to carry it. - explainer: Signing messages needs a private key, and keeping that key in a browser is risky. Secret stores the key on a node you trust and only uses it when you prove it's you. How you prove it is pluggable: a cookie, a password, or any other device. - for example: A safe deposit box. The bank holds it, and only your key opens it. - works with: cookie, http-auth, auth-hook - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/auth/dev_secret.erl ### ~cookie@1.0 (Cookie; in plain terms, The Wristband) - id: cookie - family: Protect. Devices that keep things safe and locked. - status: built into HyperBEAM - job: Gives your browser a wristband so the node remembers you. - explainer: Websites use cookies to remember who you are. This device reads and writes them for a node, and can turn a cookie into a secret that signs your messages. That's how a web page can talk to AO without you managing a wallet. - for example: A hotel key card. Show it and the door opens; no need to prove who you are each time. - works with: secret, auth-hook - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/auth/dev_cookie.erl ### ~http-auth@1.0 (HTTP auth; in plain terms, The Password Check) - id: http-auth - family: Protect. Devices that keep things safe and locked. - status: built into HyperBEAM - job: Username and password, the classic way. - explainer: The same login box you've seen a thousand times, turned into a device. Your username and password become a secret that can sign messages, so old-school web tools can use AO too. - for example: A username and password. The same login box you've used a thousand times. - works with: secret, auth-hook - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/auth/dev_http_auth.erl ### ~auth-hook@1.0 (Auth hook; in plain terms, The Autograph Machine) - id: auth-hook - family: Protect. Devices that keep things safe and locked. - status: built into HyperBEAM - job: Signs your messages for you as they come in. - explainer: Plug this into Meta and every request that arrives gets signed with a wallet the node holds for you, after you prove who you are with Cookie or HTTP auth. It's the device that lets normal web apps use AO without a crypto wallet popup. - for example: A notary's stamp. Once you've shown ID, every page gets stamped for you. - works with: meta, cookie, http-auth, secret - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/auth/dev_auth_hook.erl ### ~snp@1.0 (SNP (TEE); in plain terms, The Vault) - id: snp - family: Protect. Devices that keep things safe and locked. - status: coming back; being rebuilt - job: A sealed room even the node's owner can't see into. - explainer: Some computer chips can run code in a locked box and give you a receipt proving what ran inside. This device uses that so a node can prove 'I ran this exactly, and nobody, not even me, peeked.' It was in earlier versions and is being rebuilt right now, so treat it as coming soon. - for example: A sealed room with a window. You can verify what happened inside, but nobody could reach in. - works with: meta - source: https://github.com/permaweb/HyperBEAM/blob/edge/docs/resources/source-code/dev_snp.md ### ~cache@1.0 (Cache; in plain terms, The Shelf) - id: cache - family: Store. Devices that remember and save things. - status: built into HyperBEAM - job: Hands you anything the node has saved, by its ID. - explainer: Every message a node has seen gets saved with a fingerprint (its ID). Ask Cache for an ID and it hands the message back in whatever format you want. Trusted writers can also put new things on the shelf. - for example: The hold shelf at a library. Give the ID, get the item. - works with: query, match, bundler - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/node/dev_cache.erl ### ~bundler@1.0 (Bundler; in plain terms, The Packer) - id: bundler - family: Store. Devices that remember and save things. - status: built into HyperBEAM - job: Packs lots of little things into one box before shipping to Arweave. - explainer: Saving each tiny message to Arweave one at a time would be slow and expensive. Bundler collects them, stuffs thousands into a single box, signs it, and ships it. It also puts a copy in the node's cache right away so you can read it before the box even leaves. - for example: Shipping one pallet instead of five hundred separate envelopes. - works with: cache, arweave, p4 - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/arweave/dev_bundler.erl ### ~arweave@2.9 (Arweave; in plain terms, The Archive Door) - id: arweave - family: Connect. Devices that talk to the outside world. - status: built into HyperBEAM - job: Reads devices and transactions from Arweave, the forever storage. - explainer: Arweave is where AO keeps things permanently. This device is the door to it: ask for a device, a transaction, or the current height and it goes and gets it from a real Arweave node. Other devices like Copycat use this door. - for example: The door to the archive room, where every record ever filed still sits. - works with: copycat, bundler, relay - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/arweave/dev_arweave.erl ### ~copycat@1.0 (Copycat; in plain terms, The Photocopier) - id: copycat - family: Find. Devices that search and look things up. - status: built into HyperBEAM - job: Copies messages from other places into this node's shelf. - explainer: If you want to search Arweave data fast, you need a local copy. Copycat pulls messages from an Arweave node or a GraphQL endpoint, checks them, and files them in this node's cache so Query can find them. - for example: Photocopying the files you need from head office so you can read them at your desk. - works with: arweave, cache, query, match - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/query/dev_copycat.erl ### ~query@1.0 (Query; in plain terms, The Search Engine) - id: query - family: Find. Devices that search and look things up. - status: built into HyperBEAM - job: Finds messages on the shelf that match what you ask for. - explainer: Say 'find me every message where the type is Transfer and the owner is Sam' and Query goes through the shelf and returns them as a count, a list of IDs, or the messages themselves. It's the device behind explorers and dashboards. - for example: Search on a laptop. Find everything that matches, instantly. - works with: cache, match, copycat - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/query/dev_query.erl ### ~match@1.0 (Match; in plain terms, The Card Catalog) - id: match - family: Find. Devices that search and look things up. - status: built into HyperBEAM - job: Keeps an index so searches are fast. - explainer: Searching every message one by one is slow. Match writes down 'this key has this value in this message' as things arrive, so Query can jump straight to the right place. Operators pick which keys get indexed. - for example: The index at the back of a book. It tells you which page to open without reading the whole thing. - works with: query, cache, copycat - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/query/dev_match.erl ### ~router@1.0 (Router; in plain terms, The Traffic Cop) - id: router - family: Connect. Devices that talk to the outside world. - status: built into HyperBEAM - job: Decides which node a message should go to. - explainer: A node often needs to send messages to other nodes. Router has a list of rules: 'anything for this process goes to those three nodes; pick the nearest one.' It spreads the load and keeps going if one node is down. - for example: An air traffic controller. Every message is sent to the best available runway. - works with: relay, location - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/node/dev_router.erl ### ~location@1.0 (Location; in plain terms, The Address Book) - id: location - family: Connect. Devices that talk to the outside world. - status: built into HyperBEAM - job: Tells you where to find a node on the internet. - explainer: Nodes are known by their wallet address, but you need a real URL to reach them. Location lets a node sign a note saying 'find me at this address for a while,' and lets other nodes look those notes up. - for example: A contacts list. A name on one side, a real address on the other. - works with: router, name - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/node/dev_location.erl ### ~name@1.0 (Name; in plain terms, The Nametag) - id: name - family: Find. Devices that search and look things up. - status: built into HyperBEAM - job: Turns a friendly name into the long ID it stands for. - explainer: IDs on AO are 43 random-looking characters. Nobody wants to type that. Name checks a list of resolvers (local names, the naming system, whatever's plugged in) and turns 'my-game' into the real ID. - for example: Typing a company's name into a browser instead of its IP address. - works with: local-name, location - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/name/dev_name.erl ### ~local-name@1.0 (Local name; in plain terms, The Sticky Note) - id: local-name - family: Find. Devices that search and look things up. - status: built into HyperBEAM - job: Names that only this node remembers. - explainer: Sometimes a name only needs to work on one node, like 'my-test-process'. Local name saves those locally and keeps them across restarts. - for example: A nickname only your household uses. - works with: name, node-process - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/name/dev_local_name.erl ### ~node-process@1.0 (Node process; in plain terms, The Superintendent) - id: node-process - family: Run. Devices that do the actual work. - status: built into HyperBEAM - job: A process that belongs to this one node and always comes back. - explainer: Some processes should exist once per node: a helper that cleans up, or a node's own token ledger. Node process spawns them by name from the node's settings, and finds them again after a reboot. - for example: The building's superintendent. There is one, it lives on site, and it's there after every restart. - works with: process, local-name - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/node/dev_node_process.erl ### ~patch@1.0 (Patch; in plain terms, The Reorganizer) - id: patch - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Moves data from one spot in a message to another. - explainer: A process often wants to publish part of its state so a website can just read it with a normal web address. Patch copies data from inside the process to the outside where anyone can GET it. No indexer needed. - for example: Pinning the current stats to the lobby noticeboard so nobody has to ask. - works with: process, stack - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/util/dev_patch.erl ### ~dedup@1.0 (Dedup; in plain terms, The Duplicate Checker) - id: dedup - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Skips a message it's already seen. - explainer: If the same message shows up twice, running it twice could be bad. You'd pay someone double. Dedup remembers what's been done and says 'skip' the second time. - for example: The accountant who refuses to pay the same invoice twice. - works with: stack, process - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/util/dev_dedup.erl ### ~multipass@1.0 (Multipass; in plain terms, The Second Coat) - id: multipass - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Runs the assembly line again until it's done enough laps. - explainer: Some jobs need the whole line to run more than once: first pass to set up, second pass to finish. Multipass says 'go again' until the count is reached. - for example: A coat of paint, dry, second coat. Some jobs need more than one pass. - works with: stack - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/util/dev_multipass.erl ### ~apply@1.0 (Apply; in plain terms, The Do-It Button) - id: apply - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Runs whatever path you point it at. - explainer: A utility device: give it a message and a path, and it runs that path. It's what devices use to call other devices without hard-coding names. - for example: The Enter key. - works with: stack, lua - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/util/dev_apply.erl ### ~message@1.0 (Message; in plain terms, The Plain Box) - id: message - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: The basic message with nothing special added. - explainer: Every message in AO is a box of keys and values. This device is what a message is when no other device is in charge: you can read its keys, get its ID, see who signed it, and check the signature. Every other device builds on this one. - for example: A plain cardboard box, before anything is written on it. - works with: httpsig, json, structured - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/message/dev_message.erl ### ~httpsig@1.0 (HTTP signatures; in plain terms, The Signature Pen) - id: httpsig - family: Protect. Devices that keep things safe and locked. - status: built into HyperBEAM - job: Signs messages and checks signatures using a web standard. - explainer: HTTP has an official way to sign requests (RFC 9421). This device uses it so an AO message is also a valid signed web request. That means a normal web browser or server can verify AO messages without special software. - for example: A signature on a contract. Anyone can check it's yours. - works with: message, ans104, tx - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/codec/dev_httpsig.erl ### ~ans104@1.0 (ANS-104; in plain terms, The Arweave Translator) - id: ans104 - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Turns AO messages into Arweave bundle items and back. - explainer: Arweave has its own file format for bundled data (ANS-104). This translator converts between that and AO messages, so things saved on Arweave can be read as messages and messages can be saved to Arweave. - for example: A translator at a border crossing, fluent in both formats. - works with: bundler, message, tx - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/codec/dev_ans104.erl ### ~tx@1.0 (TX codec; in plain terms, The Old-Style Translator) - id: tx - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Reads and writes plain Arweave transactions. - explainer: Before bundles, Arweave used plain transactions. This translator handles those, so old data and base-layer transactions show up as normal AO messages. - for example: Reading an older filing format because some records still use it. - works with: arweave, ans104, message - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/codec/dev_tx.erl ### ~json@1.0 (JSON; in plain terms, The JSON Translator) - id: json - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Turns messages into JSON and back. - explainer: JSON is the format most websites and apps speak. This translator lets you read any message as JSON and send JSON in as a message. Add '/~json@1.0' to a path and you get JSON out. - for example: The format every app and website already speaks. - works with: message, wasm64 - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/codec/dev_json.erl ### ~structured@1.0 (Structured codec; in plain terms, The Type Labeler) - id: structured - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Remembers whether a value is a number, a list, or text. - explainer: Underneath, everything travels as plain text. This device tags values with their real type (integer, float, list) so '42' comes back as a number, not a string. - for example: Labeling jars so sugar and salt never get mixed up. - works with: message, httpsig - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/codec/dev_structured.erl ### ~flat@1.0 (Flat codec; in plain terms, The Flattener) - id: flat - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Squashes nested messages into one flat list of paths. - explainer: A message inside a message inside a message is hard to store. Flat codec turns it into simple 'a/b/c = value' lines and can puff it back up later. - for example: Folding a road map flat so it fits in the glovebox. - works with: message, cache - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/codec/dev_flat.erl ### ~gzip@1.0 (Gzip; in plain terms, The Squeezer) - id: gzip - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Makes data smaller, then makes it big again. - explainer: Standard compression as a device. Squeeze a body before sending, unsqueeze on the other side. - for example: A vacuum bag for luggage. Same clothes, less space. - works with: message - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/codec/dev_gzip.erl ### ~base64url@1.0 (Base64url; in plain terms, The Safe Speller) - id: base64url - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Rewrites any data using only URL-safe letters. - explainer: Raw bytes can't go in a web address. This device rewrites them with letters, numbers, dashes and underscores, the way every Arweave ID is written. - for example: Spelling a word with only the characters a license plate allows. - works with: message - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/codec/dev_base64url.erl ### ~bits@1.0 (Bits codec; in plain terms, The Bit Reader) - id: bits - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Reads tightly packed binary data using a little format string. - explainer: Some data is packed bit-by-bit to save space. Describe the layout ('4 bits for this, 12 for that') and this device unpacks it into named fields. - for example: Reading a barcode: each stripe means something, if you know the layout. - works with: message, tx - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/codec/dev_bits.erl ### ~manifest@1.0 (Manifest; in plain terms, The Site Map) - id: manifest - family: Store. Devices that remember and save things. - status: built into HyperBEAM - job: Turns a folder of files on Arweave into a website with paths. - explainer: A website is a bunch of files. An Arweave manifest is a list saying 'index.html is this ID, style.css is that ID.' This device reads the list so a node can serve the whole site from one address. - for example: The table of contents in a binder. Which document is on which tab. - works with: arweave, cache - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/arweave/dev_manifest.erl ### ~trie@1.0 (Trie; in plain terms, The Branching Tree) - id: trie - family: Store. Devices that remember and save things. - status: built into HyperBEAM - job: Stores lots of keys in a tree so lookups stay fast. - explainer: A radix trie is a data structure that groups keys by their shared beginnings. This device builds one out of messages, so a process can hold millions of entries without slowing down. - for example: A phone book. Every name starting with 'Sm' is on the same page. - works with: message, process - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/message/dev_trie.erl ### ~wasi@1.0 (WASI; in plain terms, The Pretend Hard Drive) - id: wasi - family: Run. Devices that do the actual work. - status: built into HyperBEAM - job: Gives WASM programs a file system to read and write. - explainer: Programs expect files and folders. This device fakes a file system out of messages so a WASM program can open, read, and write files as if it had a disk. - for example: A hotel room set up to feel like home, so a program that expects files and folders finds them. - works with: wasm64 - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/vm/dev_wasi.erl ### ~json-iface@1.0 (JSON interface; in plain terms, The Interpreter) - id: json-iface - family: Run. Devices that do the actual work. - status: built into HyperBEAM - job: Lets a WASM program and the node talk using JSON. - explainer: A WASM program can't see AO messages directly. JSON interface hands the program JSON on the way in and reads JSON on the way out, translating each direction. - for example: An interpreter sitting between two people who speak different languages. - works with: wasm64, json, genesis-wasm - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/codec/dev_json_iface.erl ### ~genesis-wasm@1.0 (Genesis WASM; in plain terms, The Time Machine) - id: genesis-wasm - family: Run. Devices that do the actual work. - status: built into HyperBEAM - job: Runs old AO processes the way the original network did. - explainer: Before HyperBEAM, AO processes ran on an older system called legacynet. This device recreates that world so all those existing processes keep working without changes. - for example: An adapter that lets old equipment run on the new system. - works with: process, wasm64, json-iface, delegated-compute - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/vm/dev_genesis_wasm.erl ### ~delegated-compute@1.0 (Delegated compute; in plain terms, The Outsourcer) - id: delegated-compute - family: Run. Devices that do the actual work. - status: built into HyperBEAM - job: Asks another machine to do the work and brings back the answer. - explainer: Not every node needs to run every program. Delegated compute sends the job to a machine you trust and treats its result as if it ran here. - for example: Sending laundry out instead of doing it in-house. - works with: process, genesis-wasm, relay - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/vm/dev_delegated_compute.erl ### ~recorder@1.0 (Recorder; in plain terms, The Black Box) - id: recorder - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Records everything that happened during a request, for when things break. - explainer: Like the flight recorder on a plane. Turn it on for one request and it captures every step, then shows you the trace as JSON, text, or a little web page. Great for figuring out why something went wrong. - for example: The flight recorder on a plane. When something goes wrong, you can replay every step. - works with: meta, profile - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/debug/dev_recorder.erl ### ~profile@1.0 (Profile; in plain terms, The Stopwatch) - id: profile - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Measures which parts of a request are slow. - explainer: Runs a request under a profiler and reports where the time went. For builders trying to speed things up. - for example: A lap timer. Which section of the course is costing you seconds. - works with: recorder - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/node/dev_profile.erl ### ~hyperbuddy@1.0 (Hyperbuddy; in plain terms, The Tour Guide) - id: hyperbuddy - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: The node's built-in web dashboard. - explainer: Visit a node in your browser and Hyperbuddy shows you around: what's running, node stats, a place to poke at messages. It's the friendly face on top of all the other devices. - for example: The visitor center at a national park. - works with: meta, cacheviz, query - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/node/dev_hyperbuddy.erl ### ~cacheviz@1.0 (Cache viz; in plain terms, The Map Maker) - id: cacheviz - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Draws a picture of what's on the shelf. - explainer: Turns the node's saved messages into a diagram so you can see how they connect. - for example: A map of the office showing how the departments connect. - works with: cache, hyperbuddy - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/node/dev_cacheviz.erl ### ~whois@1.0 (Whois; in plain terms, The Mirror) - id: whois - family: Tools. Devices that help builders build. - status: built into HyperBEAM - job: Tells you your own internet address, or the node's. - explainer: Ask it and it says what IP and host it sees. Simple, but useful when setting up nodes. - for example: Caller ID. - works with: location - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/node/dev_whois.erl ### ~b32-name@1.0 (Base32 names; in plain terms, The Subdomain Trick) - id: b32-name - family: Find. Devices that search and look things up. - status: built into HyperBEAM - job: Lets any message ID be used as a website subdomain. - explainer: Message IDs have characters that can't go in a domain name. This device rewrites them so 'someid.node.example' just works, so every message can have its own web address. - for example: Giving every apartment its own street address. - works with: name, manifest - source: https://github.com/permaweb/HyperBEAM/blob/edge/src/preloaded/name/dev_b32_name.erl ### token@1.0 (Token; in plain terms, The Coin Maker) - id: token - family: Pay. Devices that handle money and fairness. - status: community device (published with Forge) - job: A ready-made token: balances, transfers, the works. - explainer: Instead of writing your own token from scratch in Lua, snap this in. It keeps balances, moves coins between owners, and sends the usual notices when money moves. - for example: A gift card balance. It can be checked, spent, and transferred. - works with: process, process-outbox, pot - forge spec id: Y0oqgFc3B88Xz_RcgWn2PlgJtUn7uzCH0aPtlAChXGY; implementation id: yGNpkVZIP2Ou1VRCn9Nw7yeJJ_HqYe42umDKEnpB7MU; signer: vZY2XY1RD9HIfWi8ift-1_DnHLDadZMWrufSh-_rKF0 - source: https://github.com/permaweb/token-1.0 ### process-outbox@1.0 (Process outbox; in plain terms, The Newsletter) - id: process-outbox - family: Connect. Devices that talk to the outside world. - status: community device (published with Forge) - job: Lets people subscribe to a process and get told when things happen. - explainer: A process puts outgoing messages in an outbox. This device manages that outbox and lets other processes sign up: 'tell me whenever a Transfer happens.' Then it fans the news out to every subscriber. - for example: Signing up for shipping notifications. You're told the moment something moves. - works with: process, push, token - forge spec id: nqT2LAb7T0UbRdZ3Srixr7Zcfb5JRvTzHIIsSCIIaK0; implementation id: Zj1bSwn-GsLlOwZQvuOKas4pv80tRwrrLDZiSOpM5JU; signer: vZY2XY1RD9HIfWi8ift-1_DnHLDadZMWrufSh-_rKF0 ### recharging-ledger@1.0 (Recharging ledger; in plain terms, The Refilling Allowance) - id: recharging-ledger - family: Pay. Devices that handle money and fairness. - status: community device (published with Forge) - job: Everyone gets a balance that slowly refills on its own. - explainer: A ledger for P4 where you don't top up with money. Your balance just refills over time, like energy in a mobile game. Operators can give bigger refills to people who hold more AO tokens. - for example: A phone plan with monthly data. Use it, and it refills on schedule. - works with: p4, metering - source: https://github.com/permaweb/recharging-ledger ### eth-client@1.0 (ETH client; in plain terms, The Ethereum Window) - id: eth-client - family: Connect. Devices that talk to the outside world. - status: community device (published with Forge) - job: Lets AO look at what's happening on Ethereum. - explainer: A client device that reads Ethereum data so processes on AO can react to it: balances, devices, events. A first step toward bridges between the two worlds. - for example: A window into the office next door, so you can react to what they're doing. - works with: relay, process - source: https://github.com/permaweb/eth-client-1.0 ### pot@1.0 (PoT minting; in plain terms, The Slow Cooker) - id: pot - family: Pay. Devices that handle money and fairness. - status: community device (published with Forge) - job: Mints new tokens based on how much time has passed. - explainer: Proof-of-time minting: instead of mining, tokens are created on a clock. Works with Token to make a token that grows steadily. - for example: Interest on a savings account. It accrues on its own. - works with: token, process-outbox, cron ### reference@1.0 (Reference; in plain terms, The Whiteboard) - id: reference - family: Store. Devices that remember and save things. - status: community device (published with Forge) - job: One permanent name, one value you can change whenever. - explainer: Create a reference and it gets an ID that never changes. Its value can be replaced any time by the one owner who made it. Unlike a process, you don't replay history. The latest value is just the latest value. - for example: The specials board at a restaurant. Same board, new writing every day. - works with: name, cache - source: https://github.com/samcamwilliams/reference-1.0 ### simple-oracle@1.0 (Simple oracle; in plain terms, The Price Checker) - id: simple-oracle - family: Connect. Devices that talk to the outside world. - status: community device (published with Forge) - job: Fetches the price of AO and AR in dollars. - explainer: Asks a few price websites through Relay, averages the answers, and remembers them for a bit. Handy for any device that needs to charge in dollars. - for example: Checking three sites for a price and going with the average. - works with: relay, p4, arweave-byte-pricing - source: https://github.com/xylophonez/simple-oracle-device ### pricing-router@1.0 (Pricing router; in plain terms, The Price Switchboard) - id: pricing-router - family: Pay. Devices that handle money and fairness. - status: community device (published with Forge) - job: Sends each kind of request to the right pricing device. - explainer: One node might want to charge per-byte for uploads but a flat fee for reads. This device looks at the request and routes it to the pricing device that fits. - for example: A cashier who knows coffee is one price and lunch is another. - works with: p4, metering, simple-pay, arweave-byte-pricing - source: https://github.com/xylophonez/pricing-router-device ### arweave-byte-pricing@1.0 (Byte pricing; in plain terms, The Scale) - id: arweave-byte-pricing - family: Pay. Devices that handle money and fairness. - status: community device (published with Forge) - job: Charges uploads by weight: how many bytes you're storing. - explainer: A pricing device that weighs what you're saving to Arweave and charges per byte, so the node can cover its own storage cost. - for example: Paying for shipping by weight. - works with: p4, bundler, pricing-router, simple-oracle - source: https://github.com/xylophonez/arweave-byte-pricing-device ### gateway-shim@1.0 (Gateway shim; in plain terms, The Path Rewriter) - id: gateway-shim - family: Connect. Devices that talk to the outside world. - status: community device (published with Forge) - job: Rewrites incoming web addresses so old-style links still work. - explainer: Arweave gateways have their own URL style. This device catches those requests and rewrites the path into what HyperBEAM expects, so a HyperBEAM node can stand in for a gateway. - for example: Mail forwarding after you move. Old addresses still reach you. - works with: meta, manifest - source: https://github.com/permaweb/gateway-shim-1.0 ### git@1.0 (Git; in plain terms, The Repo Reader) - id: git - family: Connect. Devices that talk to the outside world. - status: community device (published with Forge) - job: Reads a git repository, checks every file, and serves it from a node, even to git clone. - explainer: Point it at a public project on GitHub, GitLab, or Codeberg and pick a commit. The node downloads that exact snapshot, checks every file against its git fingerprint, and keeps a copy it can hand to anyone who asks. Anyone can also git clone it straight from the node, and git checks every file again. If the host sends something wrong or a saved file gets damaged, the fingerprint won't match and the node refuses it. - for example: A certified copy of a deed. Anyone can check it matches the original without calling the county office. - works with: cache, httpsig, lua - forge spec id: S5AySdmyR5nOicnUzXfTl6lnbjfSreMNU4pAQw9sbFE; implementation id: CRrtwlp9c6rVDPtl5sJeR-bWzXrBAh2eK2nYgWyiMtY; signer: aklq1HkVWIE7DWLKjUlyYdFT6plUV7TMpLl16aOU-BU - source: https://molecule.arweave.net/#/git-device ## Builds: real chains of devices and what each device does in them ### Build 01: How a message gets answered The everyday loop. Almost every AO app is this story. An AO app is a program on computers anyone can run, not one company's server. These devices carry your message from the door to an answer. - meta: A request walks in. Meta checks who's asking. - scheduler: Scheduler gives it a number so it waits its turn. - process: The process opens its log to where things left off. - lua: Lua runs the code and writes down what changed. - push: Push delivers any replies to the next process. ### Build 02: How a node earns money Same loop, but strangers pay for what they use. A node is one of those computers, and whoever runs it can charge for the work. It works like a parking garage: a gate, a meter, and a charge against your account. - rate-limit: Rate limit makes sure nobody hammers the door. - p4: P4 asks: how much, and can they pay? - metering: Metering counts what the job actually used. - recharging-ledger: Recharging ledger takes the charge from a balance that slowly refills. - lua: Only then does Lua do the work. ### Build 03: How a website lives forever Host a site from permanent storage and let people search it. Arweave is storage you pay for once and keep for good, like buying a house instead of renting. Once a site is saved there, nobody can take it down. - arweave: Arweave opens onto everything ever saved. - manifest: Manifest turns a folder of files into pages. - copycat: Copycat keeps a local copy so it's fast. - match: Match files every page by what's in it. - query: Query finds any page in a blink. - bundler: Bundler ships new pages back to storage in one box. ### Build 04: How a browser gets a wallet A normal web page can talk to AO with no crypto popup. A wallet is your signature on AO: it proves a message came from you. Here the node holds your key for you, like a hotel desk holding your room key. - cookie: Cookie remembers your browser. - secret: Secret keeps a key for you on the node. - auth-hook: Auth hook signs each request with it. - process: The process sees a properly signed message and trusts it. ## In the works (open pull requests on permaweb/HyperBEAM) - llm@1.0, harness@1.0, skills@1.0 (The Agent Stack): An AI agent as devices: a model, the loop that runs it, and the skills it can use. [In review, PR #1064, Forward Research] https://github.com/permaweb/HyperBEAM/pull/1064 - ~rac@1.0 (The Registered Mail): Messages between processes arrive in order, exactly once, and can't be replayed. [In review, PR #1033, Forward Research] https://github.com/permaweb/HyperBEAM/pull/1033 - ~arweave-scheduler@1.0 (The Chain Clerk): A scheduler that takes its order from the Arweave chain itself, so there is no scheduler wallet to trust. [In review, PR #1022, Forward Research] https://github.com/permaweb/HyperBEAM/pull/1022 - router node (The Fastest Answer): A node that asks about thirty peers and takes the first good answer. [In review, PR #988, Forward Research] https://github.com/permaweb/HyperBEAM/pull/988 - ~ipfs@1.0 codecs (The IPFS Door): Read and serve anything on IPFS by its CID, verified, and push it to Arweave for good. [Draft, PR #868, Sam Williams] https://github.com/permaweb/HyperBEAM/pull/868 ## Wanted (asked for out loud, not built yet). Each is a real opportunity for a new device. ### ~gpu-infer@1.0 (The Heavy Thinker) - job: Run a model on a GPU and hand back the answer with proof of what ran. - why: Agents on AO need inference that is fast and provable. Today a node has no way to use a GPU. - inputs: A model id, a prompt or tensor, a budget. - outputs: The output plus an attestation of the run. - sits next to: wasm64, delegated-compute, snp - who asked: HyperBEAM docs, AO Devices, the potential of devices: "Devices could be created to interface directly with specialized hardware accelerators like GPUs" https://github.com/permaweb/HyperBEAM/blob/edge/docs/introduction/ao-devices.md ### ~zk-verify@1.0 (The Stamp Checker) - job: Check a zero-knowledge proof in one step, natively, instead of inside slow WASM. - why: Private state, ZK bridges, and provable off-chain work all need a cheap verifier. Nothing in the tree does this yet. - inputs: A verifying key, a proof, public inputs. - outputs: Valid or not, committed into the message. - sits next to: httpsig, wasm64 - who asked: HyperBEAM docs, AO Devices, the potential of devices: "New devices could implement cutting-edge cryptographic techniques, such as zero-knowledge proofs" https://github.com/permaweb/HyperBEAM/blob/edge/docs/introduction/ao-devices.md ### ~vrf@1.0 (The Fair Dice) - job: A random number nobody can rig, with a receipt proving it was fair. - why: Games, lotteries, and fair ordering need randomness. There is no randomness device at all; the old way was slow commit-and-reveal in Lua. - inputs: A seed, usually the message's own hash chain. - outputs: A random value and a signature anyone can check. - sits next to: httpsig, snp - who asked: Device Proshop, our read of the edge branch: "No randomness primitive anywhere in the preloaded devices." https://github.com/permaweb/HyperBEAM/tree/edge/src/preloaded ### ~vector-memory@1.0 (The Long Memory) - job: Turn saved messages into embeddings and find the closest ones fast. - why: The agent stack's memory is markdown files. Real recall needs a vector index that fills itself from the cache. - inputs: Messages as they are written to the cache. - outputs: Nearest matches for any query, with scores. - sits next to: match, query, copycat - who asked: Device Proshop, reading PR #1064: "Agent memory today is a folder of markdown files." https://github.com/permaweb/HyperBEAM/pull/1064 ### ~chain-clients@1.0 (The Other Windows) - job: Read Bitcoin and Solana the way eth-client reads Ethereum. - why: eth-client exists. The same shape for the other big chains would let AO processes react to all of them. - inputs: Block headers and proofs from a chain. - outputs: Verified chain state as AO messages. - sits next to: eth-client, relay - who asked: HyperBEAM docs, AO Devices, the potential of devices: "Devices could act as secure bridges to other blockchain networks" https://github.com/permaweb/HyperBEAM/blob/edge/docs/introduction/ao-devices.md ## How to make a device (Forge) Devices live in their own repos as ordinary Erlang projects. HyperBEAM ships "Forge", a rebar3 plugin, and a project template. 1. From a HyperBEAM checkout on the `edge` branch: `./install-template --branch edge` 2. Scaffold: `rebar3 new device name=my_device` (gives `src/dev_my_device.erl`, `rebar.config` pinned to HyperBEAM `edge`, README). 3. The root module `dev_.erl` exports the device's keys. Helpers are `dev__*.erl`. Include `-include_lib("hb/include/hb.hrl").` for macros. 4. Iterate: `rebar3 device package` then `rebar3 device verify`. Test against a fresh preloaded store: `HB_PORT=0 rebar3 device test`. Run a local node with it loaded: `rebar3 device local`. 5. Publish to Arweave: `rebar3 device publish --key wallet.json`. Prints a spec id, an implementation id, and the signer. Operators install it by name or id via `trusted-devices` / `trusted-device-signers` in their node config. Conventions: one job per device; keys are resolved by HTTP path (`/~mydevice@1.0/key`); messages are maps with commitments; write `%%% @doc` at the top of the root module, it becomes the published specification. Docs: https://github.com/permaweb/HyperBEAM/blob/edge/docs/build/external-device-repository.md and docs/build/device-packaging.md. Before building anything, check devices.md and the "In the works" list: do not build what exists or is already in review. ## Requesting a build Only send a build request after the person says yes. They must be 18 or older and agree to https://deviceproshop.xyz/terms.html. POST https://deviceproshop.xyz/api/request with JSON { device: {name, job, plain, why, inputs, outputs, closest}, level, contact, prompt, credit }. level is sketch, build, or ship (how far the AI takes it). contact is required and never published; credit is an optional short name to publish with the device. An AI review runs first, so allow up to 4 minutes. Replies: { filed: true, queued: true, id, key, status } when it is in the queue, { filed: true, queued: true, already: true, id, key, status } when someone asked first (no key if this contact was already on it), { filed: true, queued: true, pending: true, id, key } when the review is still running after 80 seconds (it finishes on its own; the status page shows the result), or { declined, failed } when the review turned it down. Keep the id and key: the private status page is https://deviceproshop.xyz/status.html#., and the id is how a person asks to see or delete their request. Everything built is published as MIT open source. POST https://deviceproshop.xyz/api/status with JSON { id, key } returns { id, kind, name, plain, job, stage, label, asked, updated, reason, molecule, forge }. stage is review, queued, building, checking, published or declined. It never returns a contact or the app idea. ## Planning a node POST https://deviceproshop.xyz/api/plan with JSON { prompt } returns { summary, chain: [{id, why}], missing: [{name, job, plain, why, inputs, outputs, closest}], yours: [{what, how}], improve: [{kind, ref, title, what, why, how}], next }. yours is app logic the builder writes on existing devices; improve is changes to devices that already exist. Only catalog ids appear in chain. Allow up to 2 minutes. Limits and errors: every POST needs content-type: application/json. Each address gets 8 plans and 6 requests an hour. A 429 means slow down and try later. A 503 with fallback: true means the AI is resting or busy; use search_devices or the catalog instead. Errors always come as { error } in plain words. ## Style rules for anything you write back to humans here 8th-grade reading level, adult world. Real device names first, plain terms second. No em dashes.