Check a token's flags first

Before you add a trust line, ask three questions about the issuer:

1. Can it take my tokens back? Look for clawback.
2. Can it freeze me? Look for No Freeze.
3. Is anything frozen right now? Look for a global freeze, and for a freeze on your own line.

Most explorers show these settings on the issuer's account page. This table reads them:

No setting is good or bad on its own. Some jurisdictions require issuers to be able to recover funds, which is why clawback exists. An issuer that wants its token to act like cash between holders can set No Freeze.

The point is to know before you hold, not after.

Issuer flags. Call account_info on the issuer:

{ "method": "account_info", "params": [{ "account": "r...issuer", "ledger_index": "validated" }] }

The result has an account_flags object of booleans. rippled includes allowTrustLineClawback there, next to the fields in the docs table. The raw bits are in account_data.Flags:

Your line. Call account_lines with your address as account and the issuer as peer. Each line reports flags from your point of view:

• freeze_peer: true means the issuer froze the line. freeze: true means you did.
• rippled also returns deep_freeze and deep_freeze_peer when a deep freeze is set.

You can also read the RippleState entry with ledger_entry and test the issuer's side: lsfLowFreeze or lsfHighFreeze, and lsfLowDeepFreeze (0x02000000) or lsfHighDeepFreeze (0x04000000). The low account is the one whose address sorts lower numerically.

Pools. amm_info returns asset_frozen and asset2_frozen for each token in a pool.

Related: Checking a token before you trust it.