Weave documentation
dBrowser

Node and Wallet

get_status and get_peers are Tauri commands backed by AppState.

Embedded node state

get_status and get_peers are Tauri commands backed by AppState. They are called through the desktop application's invoke bridge, not through a dbrowser node shell command. Read returned status and peer state separately: an initialized desktop process does not prove peer connectivity.

There is no commands/wallet.rs module or the dbrowser wallet generate/export command tree. Identity and signing operations must use the actual application or SDK integration. Do not fabricate an agent DID string as evidence that its private signing key exists.

Source reference

On this page