# reset-server

Owner-only destructive action through `daski_use_asset`. Input: `serverId`, `revision` (from `get-server`) and `sshPublicKey` (the new key).

The first wallet-authorized call stages the reset and returns the effect summary (server, revision, new key and the data-loss warning) and the earliest execution time. After the delay a fresh wallet authorization must confirm that exact staged action; you can cancel instead. A server whose revision changed meanwhile refuses the reset.

The reset reinstalls the clean image by root-volume replacement: the server is isolated and stopped, given new boot data with your key, started isolated, its root disk is replaced, and the replacement disk and fresh boot evidence are verified before SSH and then ports 80/443 reopen. All guest data is erased; the server keeps its ID, IP address, disk size and paid time (paused while it reinstalls). It works even if the old guest disabled SSH.

The receipt (`status: accepted`, `operationId`) means the reset was admitted; check `get-server` for completion and the new `hostKeyFingerprint`. Holds cannot be cleared by a reset.