# Freezes and lawful requests

> How a freeze is requested, applied and recorded, and how to check whether an address is frozen.

## Process

:::steps
### Request
A law enforcement agency or other competent authority sends a request to USD.NET, the operator of USD Network.

### Review
The request is checked for authority, scope and legal basis. Requests that do not meet the bar are refused.

### Apply
The address is frozen with a `freeze` event from the issuer address, sealed into the next block. The event carries a short reason, such as the category of request.

### Publish
The event appears on the [compliance log](https://usd.net/explorer/compliance) and the account shows `"frozen": true`.

### Release
When the legal basis ends, an `unfreeze` event restores the address. It is recorded the same way.
:::

## Checking an address

```bash title="Terminal"
curl https://usd.net/explorer/testnet/api/v1/address/0x…
```

The response includes `"frozen": true` or `false`. The full history is at `GET /compliance`, newest first.

## Effects

| Action | Frozen sender | Frozen recipient |
| --- | --- | --- |
| Submit a transfer | Rejected, `403` | Rejected, `403` |
| Balance | Unchanged | Unchanged |
| Bridge or fiat withdrawal | Not possible | Not applicable |

A freeze never moves funds. On testnet, the operator can apply freezes to demonstrate the flow, and they are recorded the same way.

## Contact

Authorities can reach the compliance team at **compliance@usd.net**.
