Documentation

USTA Token, like some legendary meme coins, may mean different things to different people; however, at its core, it has a very clear idea: to be a simple, verifiable, transparent, and "fun" part of the community. USTA's slogan summarizes this in a single sentence: "USTA knows."

 

When you ask, "What is USTA?", the answer isn't just "a token." USTA is also an approach: doing things openly, not secretly; generating verifiability, not claims; entering the space with a simple standard (ERC-20) instead of complex token economy tricks. The language of the Ustadept website says the same thing: "do things openly, keep it verifiable, keep it fun."

 

The essence of USTA: a boring ERC-20 tournament (and that's a good thing).

 

USTA is a stable-supply ERC-20 token on Ethereum. This is not "surprising." It has no buttons that could later lead to problems, such as tax, blacklisting, owner-issued, or an admin panel. USTA's claim is: lock the supply, simplify the rules, and let the community decide what to build.

 

This is clearly stated in the warehouse:

 

Total supply: 100,000,000,000 USTA (fixed, no inflation)

 

Mint: only once during deployment, in the constructor function.

 

There is no administrator key for the supply: "owner mint / emissions" is missing.

 

Purpose: Tipping, community activities, small experiments, and in-chain social coordination.

 

Warning: No profit guarantee is given, this is not investment advice.

 

In my opinion, this "boring design" is a virtue: the element of humor can be entertaining; the element of contract, however, doesn't have to be. The purpose of the contract is not to entertain, but to avoid surprises.

 

What does USTA mean, technically?

 

The USTA contract is quite simple:

 

It uses OpenZeppelin's ERC-20 implementation.

 

MAX_SUPPLY is a constant: 100B * 1e18

 

During distribution, the initialRecipient address cannot be 0x0 (a special error was returned with ZeroAddress()).

 

In the constructor function, MAX_SUPPLY is created once and given to the first receiver.

 

The contract also includes a "build marker" called USTA_BUILD: This doesn't change the behavior; rather, it's a tracking mechanism aimed at eliminating nonsensical entries like "Similar Match" in the explorers and achieving exact verification (Exact Match).

 

The tests focus specifically on these points: name/symbol/decimal number and totalSupply == MAX_SUPPLY, as well as failure to distribute to a zero address.

 

How do you recognize what is "official/canonical"? (Clear rules against forgeries)

 

The most important practical reflex in the USTA ecosystem is: "Automatically be suspicious if you see double-entry contracts." This repository explicitly maintains a "single official source list" for this: docs/OFFICIAL-LINKS.md. Please do not consider any links not listed there as "official."

 

Ethereum Main Network (Canonical Contract)

 

The valid address for the mainnet contract in the README file in the repository is as follows:

• 0x8D15C25E0fF24256401Fd4DA6d85301084FC3672

 

This address is also listed as "Ethereum Mainnet (USTA v1)" in the OFFICIAL-LINKS file. In Etherscan, this address also appears as "ERC-20: USTA (USTA)", indicating that the contract's Source Code is Verified (Exact Match).

 

Sepolia (test network/development canonicals)

 

The DEPLOYMENTS.md file begins with the phrase "sole source of truth for canonical distributions" and lists the v3/v2/v2-legacy addresses for Sepolia (e.g., v3: 0x52FD...).
The token follower also appears as "USTA (USTA)" on the Sepolia Etherscan page.

 

Note: Repository docs are intended to stay aligned. DEPLOYMENTS.md is the single source of truth for canonical deployments (including Ethereum mainnet USTA v1), and docs/OFFICIAL-LINKS.md is the single source of truth for what is “official” (website, email, socials, and the canonical contract). If you ever suspect drift, trust OFFICIAL-LINKS first, then independently confirm the canonical contract on Etherscan and look for “Contract Source Code Verified (Exact Match)”.

 

Distribution: "No magic sale," transfers are involved.

 

It is clearly stated in Litepaper:

 

All supply is given to the first recipient at the time of distribution.

 

Subsequent distributions will take place via normal transfers.

 

"This document does not claim to be an initial public offering (IPO) or similar event."

 

This approach means that USTA's "story" will be written not on the exchange, but by the actions of the community. The token is a tool; the "product" is community coordination.

 

USTA's culture: "Usta" persona, but disciplined craftsmanship.

 

USTA is rooted in the Turkish word "usta" (skilled craftsman). The humor can be absurd; the foundation must be rigorous: open source, repeatable distribution, verifiable address, simple rules.

 

You can see traces of this in the tools used:

 

Deployment scripts include a strict protection mechanism: this mechanism prevents accidental deployment to the mainnet and also requires manual confirmation such as "CONFIRM_MAINNET_DEPLOY=YES".

 

Sepolia distribution is also locked into a chain identity.

 

verify.mjs retrieves the addresses/recipients from the DEPLOYMENTS.md file and performs the verification process: this is a "provability" reflex.

 

The audit-high.mjs file is written in such a way that it causes the high/critical npm audit finding to fail in CI, which means "package security is taken seriously".

 

Security and Identity: USTA's "Official" Boundaries

 

USTA specifically highlights the risk of unofficial phishing/impersonation. The Litepaper explicitly states the risk of "phishing/impersonation" and that only links from OFFICIAL-LINKS should be considered.

 

If you find a security vulnerability, you can also report it via this channel: ustadept@ustadept.com (SECURITY.md).