Troubleshooting
Common issues and solutions for Paraloom
Troubleshooting
Quick solutions for common issues you might encounter.
Build Errors
Runtime Errors
Network Issues
Validator Issues
Proof Generation Issues
Common Error Codes
| Code | Meaning | Solution |
|---|---|---|
| E001 | Invalid proof | Regenerate proof |
| E002 | Nullifier spent | Note already used |
| E003 | Root not found | Refresh merkle root |
| E004 | Insufficient funds | Check pool balance |
| E005 | Consensus failed | Retry operation |
| E006 | Invalid signature | Check authority key |
| E007 | Timeout | Increase timeout, retry |
| E008 | Serialization error | Check data format |
Debug Mode
Enable verbose logging for debugging:
# Full debug output
RUST_LOG=debug cargo run --bin paraloom-cli
# Specific module debug
RUST_LOG=paraloom_privacy=debug cargo run
# Write to file
RUST_LOG=debug cargo run 2>&1 | tee debug.logGetting Help
If you're still stuck:
- Search existing issues: GitHub Issues
- Check logs:
tail -f logs/*.log - Report bug: Include:
- Error message
- Steps to reproduce
- System info (
uname -a,rustc --version) - Relevant logs
Never share your secret keys, mnemonics, or shielded note data when reporting issues!