zeus-diagnostics-and-tooling

Locate logs, inspect network traffic, and run diagnostic scripts for the Zeus React Native Lightning wallet.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/aswin-dev-debug/Ai-Finance-analyzer --skill zeus-diagnostics-and-tooling-aswin-dev-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zeus-diagnostics-and-tooling
Source: https://github.com/aswin-dev-debug/Ai-Finance-analyzer/tree/main/lib/zeus-contrib/zeus/.claude/skills/zeus-diagnostics-and-tooling
Command: npx skills add https://github.com/aswin-dev-debug/Ai-Finance-analyzer --skill zeus-diagnostics-and-tooling-aswin-dev-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Debugging the Zeus Bitcoin/Lightning wallet is hard because logs, capabilities, and settings are scattered across seven node backends, native Android/iOS layers, and generated code. This Skill tells you exactly where every log lives, how to read native and JS-layer output, how to inspect REST/WebSocket/Tor traffic, and provides scripts that extract ground truth from the codebase instead of stale documentation. ## Core Features & Use Cases - Log Access Per Backend: Exact file paths and commands for embedded LND lnd.log on Android/iOS, LDK Node ldk_node.log, adb logcat tag filters, Metro and Xcode consoles, plus in-app log viewers. - In-App Diagnostics: Use the Developer Tools view (18 raw RPC probes), Keychain Recovery scanner, and Activity CSV export to compare app state against node truth. - Network Inspection: Understand TLS verification defaults, WebSocket-bypasses-Tor behavior, Tor request paths, and the request-dedup cache that can replay stale failures. - Measurement Scripts: Run find-debt.sh for TODO/FIXME census, capability-matrix.sh for the live supports* matrix across all 7 backends, and list-settings-defaults.sh to catch settings default drift. - Use Case: A user's embedded LND node appears stuck syncing. Use this Skill to tail lnd.log via adb, watch the WalletState machine in logcat, check SyncStore block-height polling, and determine whether the issue is neutrino peers or an RPC timeout. ## Quick Start Ask the assistant to show you where the embedded LND logs are on Android and how to tail them from a connected device.

Frequently Asked Questions about zeus-diagnostics-and-tooling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the embedded LND log file in the Zeus Android app?

The embedded LND log lives at /data/user/0/app.zeusln.zeus/files/logs/bitcoin/<network>/lnd.log for the legacy wallet, or under a per-wallet uuid directory for newer wallets. On debug builds, tail it with adb shell run-as app.zeusln.zeus tail -n 200 files/logs/bitcoin/mainnet/lnd.log.

How do I check which features each Zeus backend supports?

Run the capability-matrix.sh script, which extracts all supports* flags live from the backends/*.ts files and prints a table across LND, EmbeddedLND, LNC, LDK Node, CLN REST, LndHub, and Nostr Wallet Connect. Pass a flag name like supportsOffers to filter the output.

Can I intercept Zeus app network traffic with a proxy like mitmproxy?

Yes for remote REST backends, because TLS certificate verification is off by default and there is no cert pinning, so a proxy works without installing a CA cert. Tor-routed requests go through the embedded nitro-tor daemon and cannot be proxied this way; observe those at the node side instead.

Why does my grep of the Zeus codebase return thousands of irrelevant hits?

Generated files like proto/lightning.js (~133k lines) and uniffi bindings (~31k lines) bury real results. Use git grep with the documented exclude list for zeus_modules, proto output, and uniffi bindings, and use -w instead of \b because macOS git grep silently fails on \b.

Why does the same network error repeat instantly with no traffic in Zeus?

The LND backend keeps a request-dedup cache keyed by URL and body, and on the Tor branch failed entries are only cleared on reconnect. An instantly repeating identical error usually means a stale cached rejection, not a live network problem.

When should I not use this diagnostics skill?

Use sibling skills for symptom-to-root-cause triage flowcharts, backend quirks and adding RPCs, storage migration rules, or build environment setup. This skill covers measurement and observation only, not the fix procedures themselves.