# Persistent Addresses

{% hint style="warning" %}
**Pre-release** — Details are subject to change as the architecture is finalised.
{% endhint %}

Persistent Addresses are deterministic, chain-specific addresses derived from a fixed set of inputs: the user identifier, the source chain, the recipient address, and the output asset. Given the same inputs, the API always returns the same address. There is no expiry, no regeneration, and no per-transaction state to manage.

{% hint style="info" %}
The UDA is unique per chain and supports multiple asset deposits.
{% endhint %}

## Business Flow

When your app calls the Persistent Addresses API, it receives a reusable deposit address tied to a specific source chain and destination. The user sends a regular token transfer to that address — no bridging UI, no extra steps. The system detects the deposit, routes it through NEAR Intents, executes any required swap, and funds the destination.

<figure><img src="/files/7VG0cTPrYqJiPs0l4LDT" alt=""><figcaption><p>Example Persistent Addresses flow with recipient address on BASE chain</p></figcaption></figure>

{% stepper %}
{% step %}

### App requests a deposit address

Apps call the UDA API with the minimal parameters: deposit chain, recipient and output asset.
{% endstep %}

{% step %}

### Receive a reusable address

The UDA API returns a reusable Deposit Address along with the current exchange rates.
{% endstep %}

{% step %}

### User sends funds

User transfers tokens to the Deposit Address.
{% endstep %}

{% step %}

### System processes the transfer

NEAR Intents swap agent handles routing and processes the transaction.
{% endstep %}

{% step %}

### Recipient gets funds

The destination asset is delivered to the recipient on the destination chain.
{% endstep %}
{% endstepper %}

## Features

### Static address

Each address is permanent and reusable. There is no TTL, no session, and no requirement to re-generate between deposits. The same address accepts unlimited sequential deposits.

### Asset conversion

An optional output asset can be specified at address generation time. If the deposited asset differs from the output asset, a swap is executed in the same atomic flow via NEAR Intents solvers. Example: `USDT on Tron → USDC on Base`.

### Destination action

You define what happens on arrival: credit a balance, execute a contract call, or fund a position. The destination action is encoded at generation time and does not require a separate call.

## Use Cases

### Neobank & fintech top-up

Give every user a persistent top-up address. They can send from any chain or CEX, and the funds are automatically added to their balance. No bridging instructions, no wrong-chain support tickets.

```
Example: SOL on Solana → routed → Neobank account credited in USDC on Base
```

### Prediction market funding

Users with assets on any chain can fund positions directly: no redirect, no bridge UI, no chain-switching prompt in the middle of a flow.

```
Example: USDT on Arbitrum → routed → prediction market account balance credited
```

### Trading account deposit

A persistent deposit address means capital flows from any chain or CEX directly into a trading account: no manual bridging, no network selection, no drop-off between decision and execution.

### Infrastructure & protocol inbound liquidity

Handle deposits from any chain natively without maintaining per-chain connectors. Embed one address generation call and let the routing layer handle the rest.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.intents.aurora.dev/intents-deposits/persistent-addresses.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.