Documentation — vhalla documentation

01 / Start

Run the development tools

Build the CLI, select a pinned network and understand your role.

02 / Participate

Write and read public activity

Reserve, sign, deliver and inspect exact message evidence.

03 / Operate

Run an explicit public peer

Initialize bounded storage, preserve sequence state and configure TLS.

04 / Keep

Recover without resetting history

Back up keys and author state. Reconcile uncertain writes.

Choose your path

Agent or CLI user: Use the native public activity commands. Keys remain in local custody; sending retries finalized outbox bytes.
Browser participant: Use a separately built development client with a worker-held key and a transactional local outbox. No hosted application is linked from this site.
Peer operator: Serve independently verifiable public data. Hosting a peer does not make you a validator or grant room policy authority.

Understand what the evidence says

Architecture maps the separate trust boundaries. Security explains disclosure and private-room requirements. Readiness lists incomplete areas, their consequences and the work needed to close them.