| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | ChainSift simulation | 21 Nov 2026 |
| Buy tax | 0% | Contract | 21 Nov 2026 |
| Sell tax | No data | Contract | 21 Nov 2026 |
| Admin mint | Enabled | Contract bytecode | 21 Nov 2026 |
| Transfers pausable | No data | Contract | 21 Nov 2026 |
| Address blacklist | No data | Contract | 21 Nov 2026 |
| Upgradeable proxy | No data | Contract | 21 Nov 2026 |
| Source verified | No | Block explorer | 21 Nov 2026 |
| Top-10 holders | 99.9% | Holder distribution | 21 Nov 2026 |
| Liquidity locked | No | LP holders | 21 Nov 2026 |
| Holders | 885 | Token contract | 21 Nov 2026 |
| Deployed by | 0xc0016f…c46cc3 |
| Holders | 885 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0xc0016f…c46cc3 | 99.54% |
| #2 | 0x2ddbdb…cd17de | 0.17% |
| #3 | 0x8d418b…afee33 | 0.07% |
| #4 | 0x343a3d…633f8a | 0.03% |
| #5 | 0xaa0c3f…77a31b | 0.03% |
This automated check scored this BSC token 0 out of 18, and the most serious finding is that a simulated sell transaction failed: the contract blocked it. In practice, this means wallets that acquire this token may not be able to convert it back into another asset, regardless of price movement — money placed into a token with this behaviour can become permanently stuck. Beyond that, the contract's bytecode shows the owner has the ability to mint new tokens at will, which can dilute existing holders' share of supply at any time. The top 10 wallets hold 99.9% of all tokens, meaning a very small number of addresses could move or sell enough supply to affect the market materially. Liquidity is not locked, so whoever controls the liquidity pool could withdraw it. The contract's source code is also not verified on the block explorer, so this check was run against raw bytecode rather than human-readable code, which limits how much automated analysis could confirm about other mechanics (several fields above are marked "no data" for this reason).
It's worth being clear about what this check does not do. This is an automated read of contract mechanics only — it looks at code behaviour like mint functions, sell simulations, and holder concentration. It says nothing about who is behind this token, whether DigiByte's name or branding is being used without authorisation, what the stated purpose or roadmap is, whether any team has legal accountability, or whether tokenomics make sense as a long-term structure. None of that is assessable from bytecode, and no human has reviewed this contract or its surrounding claims — this is a machine-generated check against known risk patterns, run on the date shown.
Given the sell block specifically, this is not a situation where a small test transaction would resolve the uncertainty: if the contract is blocking sells for other holders, a test purchase would likely also become unsellable rather than proving anything useful. Concretely, next steps would include checking the official DigiByte project channels to see whether they acknowledge any token on BSC at this contract address at all, searching the address on the block explorer for owner transaction history and any renounce-ownership events, and treating unverified source code and blocked sells as reasons to seek independent technical confirmation before any funds are committed. Any decision about this token sits entirely with the holder, based on indicators like these rather than on any conclusion this page is making for them.
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.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.