Skip to content
Logo

What is Bloom? Partial

Bloom is a framework for creating agent-safe software components. The first application of Bloom is an agentic Ethereum wallet. We call this walletFS.

Instead of handing an agent RPC credentials, signing code, and a Web3 SDK, walletFS exposes wallet and chain operations as a filesystem. Agents already know how to navigate files. walletFS makes onchain work discoverable, auditable, and policy-gated through that interface.

/bloom/
  chains/<chain>/...      # live chain state
  wallets/<name>/...      # wallet state, outbox, signatures
  defi/intents/...        # routed DeFi plans
  watch/<id>/...          # live subscriptions
  simulate/<session>/...  # dry-run calls
  tools/...               # ABI, hashes, units, EIP-712 helpers
  petals/...              # Petals (walletFS extensions)

Current walletFS state

  • read live EVM state as files: balances, blocks, gas, contracts, ABI methods, storage, events, NFTs, ENS, token prices, and address history;
  • create or import encrypted wallets without exposing private keys through the filesystem;
  • stage ETH, ERC-20, NFT, contract-call, signing, and DeFi intents by writing plain-language or structured files;
  • inspect a generated plan.md before signing;
  • confirm a staged transaction only after user approval;
  • enforce policy through spend caps, allow/deny lists, contract-call gates, private orderflow settings, and hash-chained audit logging.

On the filesystem this looks like: The current product surface is walletFS: an agentic wallet mounted as a virtual filesystem. Reads are blockchain queries. Writes are transaction intents. Nothing moves until a policy-checked plan is approved and signed outside the agent sandbox.

Broader direction

Bloom’s broader architecture extends this filesystem model to small, composable, verifiable programs called Petals. In the case of walletFS, Petals enable agent-safe wallet-extensions. This allows you and your agent to extend walletFS, safely, to accomplish innovative use cases e.g. a Polymarket trading bot, a Hyperliquid strategy or whatever you and your agent think of.

Status

The current Bloom implementation is a Rust workspace with a CLI, daemon, in-process VFS, wallet transaction engine, encrypted keystore, chain readers, DeFi routing, and an optional NFSv4 mount adapter. Live reads and local development flows work out of the box. Live mainnet and L2 broadcasts are intentionally opt-in.