Node and Wallet

Purpose

Tauri desktop browser with agent, browser, DNS, files, node, spaces, and wallet commands.

This page follows the real source shape for Dbrowser and explains the workflow a developer is likely to use first.

Developer workflow

Start from the smallest constructor or builder, perform one meaningful operation, inspect the returned state, then add the relevant policy, storage, or network integration. The examples below should be expanded whenever the crate API changes.

Primary types to know

• AgentAction — tools/dbrowser/src-tauri/src/commands/agent.rs
• AgentMessage — tools/dbrowser/src-tauri/src/commands/agent.rs
• AgentResponse — tools/dbrowser/src-tauri/src/commands/agent.rs
• AgentStatus — tools/dbrowser/src-tauri/src/commands/agent.rs
• AppState — tools/dbrowser/src-tauri/src/state.rs
• AuditLog — tools/dbrowser/src-tauri/src/commands/agent.rs
• AuditRecord — tools/dbrowser/src-tauri/src/commands/agent.rs
• ChainBalance — tools/dbrowser/src-tauri/src/commands/wallet.rs
• DnsRecord — tools/dbrowser/src-tauri/src/commands/dns.rs
• DomainLookup — tools/dbrowser/src-tauri/src/commands/dns.rs
• DomainSearchResult — tools/dbrowser/src-tauri/src/commands/dns.rs
• FileEntry — tools/dbrowser/src-tauri/src/commands/files.rs

Example shape

# dBrowser pairs each window with a Weave node + wallet through commands::node.
# Bootstrap the node, then list the identities the wallet can sign for.

# Boot the embedded node against a local storage root.
dbrowser node init --storage ~/.dbrowser/node --bootstrap /ip4/198.51.100.7/udp/4040/quic

# Show the identities currently held by the wallet sidecar.
dbrowser wallet ls

# Mint a fresh agent identity and bind it to the active window.
dbrowser wallet generate --kind agent --label ops-bot
dbrowser node attach --identity did:l1fe:agent:ops-bot

# Export the identity document (for backup or peer attestation).
dbrowser wallet export did:l1fe:agent:ops-bot --out ./ops-bot.identity.json