# TBY

## Overview

Term Bound Yield tokens or `TBY`s for shorts are the yield generating receipt tokens for lenders within `BloomPool`s. `TBY`s are `ERC1155` compatible multi-tokens who's token `id`s represent specific yield generating periods. Token `id`s will start at `0` and increment sequential by one. For me information on `TBY`s please refer to the `Tokenized Rwa` section of the docs.&#x20;

Below is the unique interface of `TBY`s.  Additionally, all `ERC1155` functions are present within the contract as well.

## Contract API

### `bloomPool`

```solidity
function bloomPool() external view returns (address);
```

Returns the address of the BloomPool contract.

### `name`

```solidity
function name() external view returns (string memory);
```

Returns the name of the token. Will return `Term Bound Yield`.

### `symbol`

```solidity
function symbol() external view returns (string memory);
```

Returns the symbol of the token. Will always return `TBY`

### `decimals`

```solidity
function decimals() external view returns (uint8);
```

Returns the number of decimals for the token. This value will match the `asset` of the associated `BloomPool`.

### `totalSupply`

```solidity
function totalSupply(uint256 id) external view returns (uint256);
```

Returns the total supply of a given token `id`.


---

# 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.bloom.garden/technical-docs/smart-contracts/tby.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.
