rescuekit-quickstart

To set up the RescueKit CLI and SDK environment, run bun run setup to install dependencies, then configure your environment variables and RPC endpoints to initialize the workspace. This guided onboarding ensures new users can safely validate configurations with read-only scans before attempting live rescue operations.

The safest way to onboard a new incident responder to rescue planning is using guided setup with enforced safety constraints and explicit incident flags. This approach prevents accidental fund transfers or credential exposure by requiring environment-based secret handling and applying safe defaults during triage and rescue operations.

Yes, you need Bun and Alchemy configured before running RescueKit scans and triage. The onboarding process explicitly requires setting up these dependencies, alongside RPC endpoints and environment variables, to ensure the CLI and SDK can execute core workflows like read-only scans and incident triage safely.

Environment-based secret handling prevents unsafe fund transfers during rescue operations by isolating credentials in configured environment variables rather than inline code. This safety constraint, combined with explicit incident flags, ensures the RescueKit CLI requires deliberate authorization before executing any action that impacts live funds.

Yes, you can perform a read-only scan to validate your RescueKit configuration before executing a live rescue. The quick start workflow specifically recommends beginning with a read-only scan to ensure your environment variables, RPC endpoints, and Bun setup are correctly configured without risking actual fund transfers.

When using RescueKit for triage, the primary safety constraints are the enforcement of explicit incident flags and environment-based secret handling. These limitations prevent the CLI from executing unsafe fund transfers or exposing credentials, meaning you must deliberately authorize any live rescue actions beyond read-only scans.