Core concepts

Virtual filesystem

Bloom exposes blockchain and wallet operations as paths. Reading a file performs a query. Writing a file stages an intent or updates local configuration.

Mounted directory

The preferred interface is the mounted /bloom directory. The mount lets any agent or shell tool interact with Bloom using ordinary filesystem operations.

ls /bloom/
cat /bloom/docs/README.md
echo alice > /bloom/wallets/new

Stage-confirm flow

Bloom does not treat a write as immediate permission to broadcast. A transaction intent becomes a pending entry with a plan and policy check. The user or controlling process must confirm before signing and broadcasting.

Policy

Policies live per wallet and enforce caps, recipient rules, contract-call gates, automation thresholds, and private orderflow behavior.

Audit log

Bloom appends writes and side-effecting reads to a hash-chained audit log under the Bloom home directory. The current head is exposed through /bloom/status/audit/head.