# SFTs

SFT stands for "Semi-Fungible Token." To understand what this is, we first need to understand two concepts:

1. **Fungible**: Fungibility refers to items that are interchangeable. The classic example is money. One $10 bill is the same as any other $10 bill, so they're interchangeable or "fungible."
2. **Non-Fungible**: Non-fungibility refers to unique items that aren't interchangeable. Think of rare collectible cards. Each card has a distinct value and features, so they're not interchangeable or "non-fungible."

Now, where does the "Semi-Fungible" part come in?

**Semi-Fungible Token (SFT)**: An SFT combines the features of both fungible and non-fungible items. This means that within the SFT standard, there are items that are interchangeable (like the $10 bills) and there are items that are distinct (like the collectible cards).

According to the ERC-3525 documentation, the standard allows for both fungible and non-fungible tokens to be represented within a single smart contract. This can be helpful for projects that want to represent both types of assets without deploying multiple contracts.

To put it in a real-world context, imagine a concert ticketing system. General admission tickets are interchangeable (or fungible), but VIP tickets with specific seat numbers are unique (or non-fungible). An SFT could represent both types of tickets in one system.

In summary, an SFT according to the ERC-3525 standard allows for the representation of both fungible and non-fungible tokens in a single contract, giving developers more flexibility in how they create and manage digital assets on the blockchain.

To learn more check out: <https://docs.solv.finance/solv-documentation/getting-started/overview>

**Interesting in obtaining SFTs?**\
Check out [https://v2.solv.finance/marketplace/basic-sft](https://v2.solv.finance/marketplace/basic-sft?network=polygon)


---

# 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.pine.loans/faqs/sfts.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.