Skip to main content

freeze_account

didbot_serve::routes::accounts

Function freeze_account 

Source 
pub(crate) async fn freeze_account(
    __arg0: State<AppState>,
    headers: HeaderMap,
    __arg2: XrpcBody,
) -> Response
Expand description

POST /xrpc/bot.did.freezeAccount

Credential::AccountSelf, the same posture as delete_account: an agent hangs Lock::Frozen on itself as Actor::Account, and nothing else hangs a lock over HTTP. The repository stays readable; only writes are refused, with 403 AccountNotWritable. Reversible with unfreeze_account, and only by the same party: an operator’s own frozen tag is not the account’s to lift.

The one route in this group that the e-stop does not gate. Every other one either destroys something or widens what the account may do, and the stop refuses those; freezing can only ever narrow, so refusing it under a stop would leave a caller less able to restrain itself than before the operator pulled the brake. A gate that can only deny is safe to skip for an operation that can only deny.