Question 1

What is SUT?

Accepted Answer

SUT is a utility token used by the SUPERTRUST ecosystem. The project positions it as a tool connecting digital finance, SuperSave credit transactions, and related services. It does not represent equity in a company or inherently generate fixed returns through ownership; its actual role depends on whether the relevant services are available and accept SUT.

Question 2

What can SUT be used for?

Accepted Answer

The project states that SUT can be used for its connected services and payment scenarios and is associated with the SuperSave credit transaction system. “Can be used” does not mean that every holder can immediately access the same service everywhere: users must first confirm that the specific platform has enabled SUT, that their region and account meet the service rules, and then complete payment, exchange, or other actions as prescribed by that platform.

Question 3

Which network does SUT run on?

Accepted Answer

SUT is based on the Polygon network. It operates as an ERC-20 token, so token balances and transfers are recorded by a smart contract on that network; when users send SUT to an on-chain address, the transaction is processed by the Polygon network rather than being recorded directly by the project's website. This distinction determines the operating conditions: both the wallet and recipient must support the correct Polygon network and corresponding token, and the sender must hold the native fee asset required by that network. Knowing only the recipient address without checking the network does not ensure that the asset will be recognized correctly.

Question 4

How should SUT supply be understood?

Accepted Answer

The audit report describes SUT as an ERC-20 token with 18 decimals and a fixed total supply of 238,403,732 tokens; the project website also discloses this total. A fixed supply means the contract design is not intended to continuously add supply through a standard minting path, but it does not mean the quantity tradable on the market is fixed. The project also discloses that 50,000,000 tokens have been burned. Burning removes the corresponding tokens from a spendable state; however, “total supply,” “amount burned,” and circulating supply at a given point in time are different measures. Available materials do not provide the timing and calculation methodology needed to reconcile these measures, so they should not be used to infer the current circulating supply.

Question 5

How do SUT transfers and approvals work?

Accepted Answer

SUT uses the ERC-20 standard. The basic process is that a holder initiates a transfer, and after the network validates and executes the contract, the sender's and recipient's balances are updated. ERC-20 also allows a holder to set an allowance for another address or contract; the approved party can transfer tokens on the holder's behalf only within the allowance and the scope permitted by contract rules. Approval is not a required step for an ordinary transfer and generally appears only when a user interacts with an application that needs to debit tokens. After granting approval, users should check the approved party and amount; when it is no longer needed, they can revoke or reduce the allowance through a wallet or an interface that supports the action.

Question 6

How can the contract pause function affect SUT?

Accepted Answer

The audit report notes that the SUT contract has a trading-pause function. This means the contract contains a control mechanism that can temporarily prevent token transfers from executing in the usual way; whether a pause occurs, how long it lasts, and when it is lifted depend on the actual exercise of contract permissions. For users, this is not price information but an availability condition: even if a wallet displays a balance, on-chain transfers or operations that rely on transfers may not be completed while transfers are paused. Holders should distinguish such permissions from network congestion and platform maintenance.

Question 7

What should be checked before transferring SUT?

Accepted Answer

Before sending SUT, first confirm that the recipient explicitly supports SUT on Polygon, and verify the address, network, and amount. Then ensure the wallet has sufficient Polygon network fee assets; without fee assets, an on-chain transaction cannot be submitted even if the user holds SUT. Once a transaction is confirmed on-chain, the sender generally cannot unilaterally reverse it. Whether an incorrect transfer to an unsupported network, address, or service can be recovered depends on whether the party controlling that address or platform has and is willing to provide recovery capability; therefore, a small test transfer should not replace verification of critical information.

Question 8

What on-chain fees are required to use SUT?

Accepted Answer

The cost of transferring SUT on-chain is determined by Polygon network transaction fees, not directly by the number of SUT tokens. When a user submits a transfer, the network charges its native fee asset according to the computational resources required by the transaction and current network conditions; SUT itself is generally only the asset being transferred. Accordingly, receiving 1 SUT or many SUT does not necessarily change the base transfer cost in the same proportion, but approvals, interactions with other contracts, or network congestion can change the computational resources and fees actually required. Before operating, users should rely on the transaction estimate displayed by their wallet.

Question 9

Does holding SUT guarantee access to ecosystem services?

Accepted Answer

Holding SUT does not itself guarantee eligibility for all SUPERTRUST services. The project associates the token with connected services, payments, and the SuperSave system, but availability of a specific service remains subject to platform launch status, account requirements, regional restrictions, and terms of service. To assess a particular use, three things should be confirmed separately: whether the service is actually available, whether it explicitly accepts SUT, and whether the user meets the participation conditions. Treating the project's ecosystem positioning directly as an unconditional right of use may confuse token functionality with service access.

Question 10

How can SUT utility and supply information affect market performance?

Accepted Answer

Fixed-supply and burn disclosures describe only some supply-side conditions and do not set SUT's market price. Price also depends on the willingness of buyers and sellers in tradable markets, the quantity available for trading, liquidity, and expectations about the actual availability of related services. For example, making a service available does not necessarily create sustained purchase demand; only if users genuinely need SUT to complete that operation, alternatives are limited, and market sellers do not increase accordingly might transaction demand affect price. Conversely, service restrictions, insufficient liquidity, or selling demand may prevent that connection from holding.

Question 11

What are the main risks of holding or using SUT?

Accepted Answer

The main risks of holding or using SUT include price volatility, insufficient market liquidity, changes to service rules or availability, and on-chain operational errors. Project statements about payment or ecosystem uses are not promises of returns and cannot guarantee that users can buy, sell, or exchange at a particular price. In addition, the contract has a trading-pause function, insufficient network fee assets will prevent transactions, and an incorrect network or address may cause losses that are difficult to recover. When assessing risk, token price risk, platform service risk, and on-chain execution risk should be considered separately.

Question 12

What can and cannot an SUT audit report establish?

Accepted Answer

The audit report explains contract-code characteristics within its review scope, such as ERC-20 functionality, fixed supply, and the pause mechanism; it cannot replace an assessment of project services, market liquidity, or future operations. Audit findings also do not mean the token price is stable, every integrator is secure, or any use case will necessarily remain available. Before using a contract, users should still verify the network and token version they are interacting with and understand how contract permissions can affect transfers. Code-level review and the platform terms, account eligibility, and market risks users actually face are different issues.

SUPERTRUST (SUT) Price