> For the complete documentation index, see [llms.txt](https://docs.useicaria.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useicaria.xyz/risk/issuer.md).

# Issuer risk

The counterparty sitting inside every tokenized security, and what the venue does about it.

Owning a Stock Token is not owning a share. It is holding a tokenized debt security from Robinhood Assets (Jersey) Ltd that follows a share kept in US custody. That distinction travels inside every position traded or held here, and the venue treats it as a risk in its own right.

## The shape of the risk

| Component              | Description                                                                                                                                                                  |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Credit risk            | Insolvency at the issuer would leave holders as creditors with a claim over the custodied shares, and recovery might be partial or slow.                                     |
| Freeze and restriction | The issuer's terms reserve a right to suspend, freeze or restrict tokens under certain conditions. Exercised, that could leave vault inventory and trader holdings immobile. |
| Redemption terms       | Redeeming at the issuer runs through KYC. Nothing in the venue depends on redemption; what it depends on is secondary pricing through the oracle.                            |
| Regulatory action      | A regulator could force the issuer to rewrite its terms, drop jurisdictions or stop issuing.                                                                                 |

## How the venue handles it

### Disclosure before exposure

Each market's listing page names the issuer, spells out what the token is legally, and reports what the bytecode review found. A trader's first swap and an LP's first deposit both pass through a plain-language explanation of the debt-claim structure. Engineering issuer risk out of existence is beyond any venue; making it impossible to hold unknowingly is not.

### Bytecode reviewed ahead of any market

The published documentation says Stock Tokens carry no on-chain freeze function, which is not by itself enough. Ahead of any market opening, that token's deployed bytecode gets reviewed for pause, freeze, blacklist and forced-transfer roles, and the finding goes onto the listing page. Where one of those roles turns up, tier assignment and caps account for it.

### Proof of reserve

Wherever a Chainlink Proof-of-Reserve feed or comparable attestation covers the issuer's custodied shares, `OracleRouter` reads it and the listing page displays it beside the market. Markets without such a feed say so in as many words.

### Caps, and one number for issuer concentration

TVL and volume caps bound each market's exposure. Because one issuer stands behind every Stock Token, the [trade explorer](/using-icaria/trade-explorer.md) additionally publishes total vault inventory exposed to Robinhood Assets (Jersey) Ltd as a single figure, which makes the concentration something stated outright rather than something to be pieced together.

### Isolation

Nothing is shared between markets, so an issuer event affecting one token, or affecting every Stock Token at once, cannot reach a market whose asset is bridged treasury or gold. Broadening the issuer set is a declared goal of the [Asset roadmap](/assets/asset-roadmap.md).

## What LPs and traders ought to understand

Whether it sits in a wallet or behind a vault share, a Stock Token is a claim on a regulated broker's custody arrangement rather than the share underneath it. If that issuer fails, the contracts keep functioning exactly as designed and in-kind withdrawals keep working, but what comes out is the claim, and pricing it stops being a market question and becomes a legal one. Caps and disclosures are how the venue proposes to bound that; anyone is free to take a more cautious view.


---

# 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.useicaria.xyz/risk/issuer.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.