| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No data | Transfer simulation | 20 Oct 2026 |
| Buy tax | No data | Contract | 20 Oct 2026 |
| Sell tax | No data | Contract | 20 Oct 2026 |
| Admin mint | Enabled | Implementation code | 20 Oct 2026 |
| Transfers pausable | Enabled | Implementation code | 20 Oct 2026 |
| Address blacklist | Enabled | Implementation code | 20 Oct 2026 |
| Upgradeable proxy | Yes — a 2-of-4 multisig can replace the code | Proxy contract | 20 Oct 2026 |
| Source verified | Yes | Block explorer | 20 Oct 2026 |
| Top-10 holders | 100% | Holder distribution | 20 Oct 2026 |
| Holders | 1 | Token contract | 20 Oct 2026 |
| Deployed by | 0xc84fe5…47882e |
| Code can be replaced by | 0x59f94a…e37187 — a 2-of-4 multisig |
| Current code | 0xbef213…473dfc |
| Holders | 1 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0xc19339…1588a4 | 100.00% |
This automated check scored United Stables (U) 4 out of 10, and each finding points to a specific power the contract owner holds over anyone who holds the token. Admin mint being enabled means the owner can create new tokens at will, which can dilute the value of existing holdings. Transfers being pausable means the owner can freeze all movement of the token, so holders could be unable to sell or transfer at a given moment. Blacklisting support means specific wallet addresses can be blocked from transacting entirely. On top of that, the contract uses an upgradeable proxy controlled by a 2-of-4 multisig, meaning a small group of signers can swap out the underlying code — including removing or changing every one of these mechanisms, for better or worse — without needing the token holders' consent. The source code is verified, which means the code is publicly readable, but verification alone says nothing about whether these powers will or won't be used. Holder concentration is also worth noting here: the top 10 holders control 100% of supply, and the data source reports just one holder, which suggests this token may be very new, barely distributed, or not yet trading on the open market.
It's important to be clear about what this check does not cover. This is an automated read of the contract's mechanical capabilities — what the code technically allows — on the date it was run. It says nothing about who the team behind United Stables is, whether they have a track record, what the token is meant to be used for, how its economics are designed to work over time, or what legal structure (if any) sits behind the project. None of that intent or context is assessed here, and no human has reviewed this project or vouched for it in any way.
Before considering any transaction, it would be worth looking into who controls the 2-of-4 multisig and whether those signers are identified or pseudonymous, checking whether the project has published audits from a named security firm, looking at the contract's transaction history on a block explorer to see if mint, pause, or blacklist functions have actually been used, and searching for any independent discussion of the team or project outside of its own channels. Given that transfers can be paused and addresses can be blacklisted, it's also worth considering what that would mean practically if it affected a wallet you control. None of this should be read as a recommendation to proceed or avoid the token — it's simply a map of what to verify next.
Contracts change after they are checked. Tell us where to reach you and we will say when this one does. Free for three contracts, no account.
We checked 10 points out of 100.
The other 90 are where money is usually lost: who the team is, where the tokens sit, what the documents actually say, and what the project chose not to put on its front page.