Troubleshooting

If something is broken, the order to check is almost always: logs → metrics → on-chain state → restart. Don't reach for cargo clean or rm -rf data/ first; those usually mask the real problem.

Build

Runtime — withdrawals & proofs

Validator

Bridge & Solana

Networking

Proof generation

Compute (alpha)

Logging & metrics

# Full debug
RUST_LOG=debug paraloom validator start --config ./validator.toml

# Per-module
RUST_LOG=paraloom_consensus=debug,paraloom_bridge=info paraloom validator start ...

# To file
RUST_LOG=info paraloom validator start --config ./validator.toml 2>&1 | tee /var/log/paraloom.log

# Metrics
curl -s http://localhost:9300/metrics | grep paraloom_

Full metrics reference: Monitoring.

When to ask for help

Before opening an issue, gather:

• Exact command + output
• paraloom --version, rustc --version, solana --version, anchor --version
• Relevant log excerpts (with RUST_LOG=info minimum)
• Whether this reproduces with a fresh data/ and a fresh build

Open the issue at paraloom-labs/paraloom-core/issues. For security-sensitive findings, do not open a public issue — see Security.

Never include shielded notes, secrets, or wallet keypairs in a bug report. Logs sometimes capture them by accident; redact before sharing.