> HyperBEAM devices

x402-compliant facilitator implemented with native ao token support, built as a HyperBEAM device

An EVM/Ethereum consensus light client packaged as a HyperBEAM device

A RISC-V smart contract execution machine built on a custom fork of R55

An EVM bytecode emulator built on top of Revm. Allows evaluation of bytecode against a given state db, statefulness and EVM context customization

Simulated quantum circuit compute in the architecture of a serverless functions runtime

Temporary S3-compatible storage either with an on-mode MinIO cluster or external connection

A device for fully homomorphic encryption (FHE). Enables computation on encrypted data without decrypting it first

Device for interfacing with llama.cpp server, handling both completion and chat completion endpoints based on session management.

NVIDIA GPU TEE attestation device which provides GPU attestation token generation and verification

Implements wasi_nn API functions as imported functions by WASM modules

Provides access to Arweave network information, relayed from a designated node.

A device that executes AO resolutions.

A device offering an on-request hook that signs incoming messages with node-hosted wallets, in accordance with the node operator's configuration.

Codec for managing transformations from `ar_bundles'-style Arweave TX records to and from TABMs.

Codec for managing transformations from `ar_tx'-style Arweave TX records to and from TABMs.

Device to emulate legacynet compute unit (CU) behavior

A device that looks up an ID from a local store and returns it, honoring the `accept' key to return the correct format.

A device that generates renders (or renderable dot output) of a node's cache.

A utility device that manages setting and encoding/decoding the cookies found in requests from a caller.

A device that inserts new messages into the schedule to allow processes to passively 'call' themselves without user interaction.

A device that deduplicates messages in an evaluation stream, returning status `skip' if the message has already been seen.

Simple wrapper module that enables compute on remote machines, implementing the JSON-Iface.

A module that implements a 'friends and family' pricing policy.

A codec for turning TABMs into/from flat Erlang maps that have paths as their keys, and a normal TABM binary as their value.

A device that mimics an environment suitable for `legacynet' AO processes, using HyperBEAM infrastructure.

The green zone device, which provides secure communication and identity management between trusted nodes.

This module implements HTTP Message Signatures as described in RFC-9421, as an AO-Core device.

Implements a two-step authentication process for HTTP requests, using the `Basic' authentication scheme.

A generalized interface for `hooking' into HyperBEAM nodes.

A device that renders a REPL-like interface for AO-Core via HTML.

A device for orchestrating indexing of messages from foreign sources into a HyperBEAM node's caches.

A simple JSON codec for HyperBEAM's message format.

A device that provides a way for WASM execution to interact with the HyperBEAM (and AO) systems, using JSON as a shared data representation.

A device for registering and looking up local names. This device uses the node message to store a local cache of its known names, and the typical non-volatile storage of the node message to store the names long-term.

A device that looks up an ID from a local store and returns it, honoring the `accept' key to return the correct format.

A device that calls a Lua module upon a request and returns the result.

An Arweave path manifest resolution device.

The identity device.

The default entry point for all messages processed by the machine.

A simple device that allows flexible monitoring of a process execution.

A device that triggers repass events until a certain counter has been reached.

A device for resolving names to their corresponding values, through the use of a `resolver' interface.

A device that implements the singleton pattern for processes specific to an individual node.

The HyperBEAM core payment ledger.

A device that can be used to reorganize a message: Moving data from one path inside it to another.

A simple example of a decentralized proof of authority consensus algorithm

This module contains the device implementation of AO processes in AO-Core.

A module for running different profiling tools upon HyperBEAM executions.

Takes a message or slot number, evaluates it, and recursively pushes the resulting messages to other processes.

A discovery engine for searching for and returning messages found in a node's cache, through supported stores.

This module implements the relay device, which is responsible for relaying messages between nodes and other HTTP(S) endpoints.

Routes outbound messages from the node to their appropriate network recipients via HTTP.

A simple scheduler scheme for AO.

Allows the operator to specify a price for a request and then charge the user for it, on a per route and optionally per message basis.

Provides an interface for validating and generating AMD SEV-SNP commitment reports.

A device that contains a stack of other devices, and manages their execution.

A device implementing the codec interface for HyperBEAM's internal, richly typed message format.

Implements a radix trie.

Handles encrypted storage operations for HyperBEAM, providing a robust and secure approach to data persistence.

Allows a node to create, export, and commit messages with secrets that are stored on the node itself.

A virtual filesystem device.

A device that executes a WASM image on messages using the Memory-64 preview standard.

A device for returning the IP/host information of a requester or itself.