| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 5 Sept 2026 |
| Buy tax | 0% | Contract | 5 Sept 2026 |
| Sell tax | 0% | Contract | 5 Sept 2026 |
| Admin mint | Not present | Contract | 5 Sept 2026 |
| Transfers pausable | Not present | Contract | 5 Sept 2026 |
| Address blacklist | Not present | Contract | 5 Sept 2026 |
| Upgradeable proxy | Yes | Contract | 5 Sept 2026 |
| Source verified | Yes | Block explorer | 5 Sept 2026 |
| Top-10 holders | 96.4% | Holder distribution | 5 Sept 2026 |
| Holders | 4257 | Token contract | 5 Sept 2026 |
| Contract deployed | 28 Apr 2023 — 1,226 days ago |
| Deployment transaction | 0x0bf3a2…6eb074 |
| Deployed by | 0x240145…69be44 |
| Holders | 4,257 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0xf97781…41acec | 59.37% |
| #2 | 0x5a52e9…70efcb | 13.86% |
| #3 | 0x43684d…26f042 | 5.74% |
| #4 | 0x21a31e…285549 | 4.00% |
| #5 | 0xa7c0d3…e2592d | 3.75% |
This automated check found that FDUSD can be bought and sold without any tax applied on either side of the transaction, and no mechanism for admin minting, transfer pausing, or address blacklisting was detected in the contract on the date of this check. What was found is that the contract is built as an upgradeable proxy, which means the logic governing how the token behaves can be replaced by whoever controls the upgrade permissions, without holders needing to approve or even be notified in advance. In practice, this gives the contract owner the ability to change the rules of the token after the fact — including potentially introducing behaviours like fees, transfer restrictions, or other mechanics that are not present today. It was also found that the top 10 holders control 96.4% of the supply, meaning a small number of wallets hold the large majority of tokens in circulation; this level of concentration means that large movements by any one of these holders could have an outsized effect on available liquidity or market conditions. The contract source code is verified on the block explorer, which means the deployed code is publicly readable and matches what has been published, though this does not by itself say anything about what that code allows or how it may be changed via the proxy.
This check only reads contract mechanics — what the code technically permits and what was observed in a transfer simulation. It does not assess who is behind the project, how the upgrade keys are managed or by whom, the token's economic design, any legal or regulatory structure, reserve backing, or the intent of the people operating it. A stablecoin like FDUSD is typically issued with centralised controls by design, so findings like upgradeability are expected in this category rather than unusual, but that context is not something this automated tool can confirm on its own.
Before relying on any of this, it's worth checking who holds the upgrade/admin keys and whether they are a known, identifiable entity or a multisig with disclosed signers, looking for independent attestations or audits of reserves if this token is meant to represent a stable value, reviewing the issuer's public documentation on redemption and governance, and checking recent on-chain activity from the top holder wallets to see whether concentration has been changing over time.
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 18 points out of 100.
The other 82 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.