> For the complete documentation index, see [llms.txt](https://docs.lnfi.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lnfi.network/products/ln-bridge/verify.md).

# Steps to Verify TA-USDT

Due to inherent constraints, real-time bridging and on-demand minting of Taproot Assets are not possible. As a result, we have pre-minted 1,000,000 TA-USDT.

The LN Bridge ensures that the amount of TA-USDT in circulation (i.e., usable or tradable on Lnfi) is always equivalent to or less than the reserve balance of ERC-20 USDT, maintaining at least a 1:1 reserve backing.

{% hint style="success" %}
All information is publicly available, allowing anyone to verify and track it in real-time.
{% endhint %}

***

### Here are the steps a user can undertake to verify

#### **Step 1**

Users can validate the total on-chain balance of ERC-20 USDT, consisting of the Bridged amount and Staking rewards via:

{% code title="Staking Contract Address" %}

```
0xbd3cDE46F73F771eEE99cc0fB13e595E7b608efB
```

{% endcode %}

#### **Step 2**

Users can validate the amount of pre-minted TA-USDT by Lnfi on the following:

<https://terminal.lightning.engineering/assets/>\
Asset ID: 0f929c417705fd4ad6fda742e107809367c7f5f10135cc6c5302bde3cb5982f1

<figure><img src="/files/bIrTkwlyZSZEaHp1K0cM" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %} <mark style="color:red;">The deployment has 2 decimals, hence displayed as 100,000,000</mark>
{% endhint %}

#### **Step 3**

Users can check the amount of TA-USDT not in circulation, by using Lnfi Explorer > Holding List&#x20;

{% code title="Lnfi Explorer URL" overflow="wrap" %}

```
https://mainnet.lnfi.network/#/explore/holding-list
```

{% endcode %}

On the Explorer Assets filter, select \[USDT].

<figure><img src="/files/suAvThZ0F9MMYy3KkE8G" alt=""><figcaption></figcaption></figure>

and search for this Nostr Address

{% code overflow="wrap" %}

```
npub19qfwjn7f2vtgvrcn06apyj5kass2huunalcwewdxjzcx5zupcjkqp7pnz5
```

{% endcode %}

#### **Step 4**

The TA-USDT in circulation can be calculated as the sum of the balances across all other Nostr addresses (excluding npub19qfwjn7f2vtgvrcn06apyj5kass2huunalcwewdxjzcx5zupcjkqp7pnz5) listed on the Lnfi Explorer > Holding List.

#### **Step 5**

The reserve balance of ERC-20 USDT and the circulating TA-USDT are displayed on our LN Bridge page, making it easy for users to track.

{% code title="LN Bridge URL" overflow="wrap" %}

```
https://mainnet.lnfi.network/#/bridge
```

{% endcode %}

***

## Important Note

(i) The reserve balance of ERC-20 USDT will always be greater than or equal to the amount of circulating TA-USDT.

(ii) We will perform regular rebalancing to distribute the accrued Staking Rewards from the Nostr address holding the TA-USDT that is not in circulation to current holders of TA-USDT who are entitled to these rewards. After rebalancing, the reserve balance of ERC-20 USDT will be adjusted to match the amount of circulating TA-USDT.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.lnfi.network/products/ln-bridge/verify.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.