Named Lists

Named lists are reusable collections of addresses or values used in policy rules. They simplify policy management by centralizing allowlists, blocklists, and other collections.

What is a Named List?

A named list is a collection of values that can be referenced by policies:

• Centralized Management — Update once, apply everywhere
• Policy Reuse — Reference lists in multiple policies
• Easy Auditing — Track list membership changes
• Dynamic Updates — Modify lists without changing policies

List Types

How Lists Work with Policies

Named lists are referenced in policy conditions using the IN_LIST and NOT_IN_LIST operators:

Common Use Cases

Counterparty Allowlist

Maintain a list of verified business partners and exchanges:

Policy usage: Block transfers to addresses NOT in this list.

Sanctions Blocklist

Block known sanctioned or high-risk addresses:

Policy usage: Block transfers to addresses IN this list.

Internal Vaults

Track your organization's vault addresses:

Policy usage: Allow transfers between internal vaults without approval.

Policy usage: Block transactions to chains NOT in this list.

List Membership Checking

Before submitting a transaction, you can verify if an address is in a list:

This enables:

• Pre-flight validation before transaction submission
• User feedback ("This recipient is not on your allowlist")
• Conditional UI flows

Best Practices

Naming Conventions

Use clear, descriptive names:

Organization

Maintenance

Security

Integration Patterns

Automated Allowlist Sync

Sync your allowlist with an external KYC system:

Related Topics

• Policies — Using lists in policy rules
• Transactions — Policy evaluation during transactions

API Reference

For complete API documentation including endpoints, request/response examples, and code samples:

• List all named lists — GET /api/v1/named-lists
• Create a new named list — POST /api/v1/named-lists
• Get named list by ID — GET /api/v1/named-lists/{id}
• Update a named list — PUT /api/v1/named-lists/{id}
• Delete a named list — DELETE /api/v1/named-lists/{id}
• Add items to a named list — POST /api/v1/named-lists/{id}/items
• Remove items from a named list — DELETE /api/v1/named-lists/{id}/items
• Check if value exists in list — GET /api/v1/named-lists/{id}/check/{value}

Named Lists

Named lists are reusable collections of addresses or values used in policy rules. They simplify policy management by centralizing allowlists, blocklists, and other collections.

What is a Named List?

A named list is a collection of values that can be referenced by policies:

• Centralized Management — Update once, apply everywhere
• Policy Reuse — Reference lists in multiple policies
• Easy Auditing — Track list membership changes
• Dynamic Updates — Modify lists without changing policies

List Types

How Lists Work with Policies

Named lists are referenced in policy conditions using the IN_LIST and NOT_IN_LIST operators:

Common Use Cases

Counterparty Allowlist

Maintain a list of verified business partners and exchanges:

Policy usage: Block transfers to addresses NOT in this list.

Sanctions Blocklist

Block known sanctioned or high-risk addresses:

Policy usage: Block transfers to addresses IN this list.

Internal Vaults

Track your organization's vault addresses:

Policy usage: Allow transfers between internal vaults without approval.

Policy usage: Block transactions to chains NOT in this list.

List Membership Checking

Before submitting a transaction, you can verify if an address is in a list:

This enables:

• Pre-flight validation before transaction submission
• User feedback ("This recipient is not on your allowlist")
• Conditional UI flows

Best Practices

Naming Conventions

Use clear, descriptive names:

Organization

Maintenance

Security

Integration Patterns

Automated Allowlist Sync

Sync your allowlist with an external KYC system:

Related Topics

• Policies — Using lists in policy rules
• Transactions — Policy evaluation during transactions

API Reference

For complete API documentation including endpoints, request/response examples, and code samples:

• List all named lists — GET /api/v1/named-lists
• Create a new named list — POST /api/v1/named-lists
• Get named list by ID — GET /api/v1/named-lists/{id}
• Update a named list — PUT /api/v1/named-lists/{id}
• Delete a named list — DELETE /api/v1/named-lists/{id}
• Add items to a named list — POST /api/v1/named-lists/{id}/items
• Remove items from a named list — DELETE /api/v1/named-lists/{id}/items
• Check if value exists in list — GET /api/v1/named-lists/{id}/check/{value}