> ## Documentation Index
> Fetch the complete documentation index at: https://api-docs.nexbridge.finance/llms.txt
> Use this file to discover all available pages before exploring further.

# Address Management

# Address Management

Partners must register approved addresses before creating subscription or redemption requests.

Only approved addresses may participate in operational settlement flows.

***

# Supported Address Types

| Asset | Network |
| ----- | ------- |
| USTBL | Liquid  |
| USDT  | Liquid  |

***

# Address Registration

Partners may create addresses through the Address Management API.

Each address includes:

* asset
* network
* blockchain address
* optional label

***

# Address Lifecycle

Addresses support the following lifecycle states.

## PENDING

The address was submitted and is awaiting operational approval.

Pending addresses cannot be used for settlement.

***

## ACTIVE

The address has been approved and may be used operationally.

Only active addresses may participate in request settlement.

***

## INACTIVE

The address has been disabled or logically deleted.

Inactive addresses cannot be used operationally.

***

# Operational Rules

## Approved Addresses Only

Settlement operations require approved addresses.

Requests referencing inactive or pending addresses are rejected.

***

## Single Active USDT Address

Only one active USDT payout address is supported at a time.

This restriction applies to automated payout operations.

***

## Address Rotation

An active USDT address may only be deleted if another USDT address is currently pending approval.

This ensures payout continuity and prevents operational interruptions.

***

# Address Approval

Address approval is performed operationally by Nexbridge.

Address creation does not imply automatic approval.

***

# Address Deletion

Address deletion is logical.

Deleted addresses transition to:

```text theme={null}
INACTIVE
```

Historical operational references remain preserved after deletion.

***

# Validation Rules

Addresses are validated for:

* supported network
* supported asset
* address format compatibility
* operational eligibility

Invalid addresses are rejected during registration.

***

# Address Usage

Addresses may be used for:

* subscription settlement
* redemption settlement
* operational funding validation

Address usage depends on:

* asset
* network
* operational approval status

***

# Future Scope

The following capabilities are currently out of scope for V1:

* self-service address approval
* batch address registration
* multi-network support
* address tagging rules
* webhook notifications for approvals