Research / Crypto token education
Solana Mint Authorities: A Reproducible PVTY and USDC Check
What does a token's mint account actually establish? On 3 October 2026, PactVerity checked two mainnet mints using the same read-only RPC method. The results demonstrate three claim boundaries—not a ranking of tokens or an independent audit.
Published · By PactVerity
Affiliation disclosed: PactVerity is the project associated with PVTY. This is first-party educational material, not an independent audit or investment recommendation.
01 / Explained
Observation method and selection
We selected PVTY because it is this project's token and USDC because Solana's own mint documentation identifies its mainnet mint. This is a deliberately selected two-mint demonstration, not a random sample of Solana tokens. There is no partnership or endorsement implied by the comparison.
Both successful observations came from https://solana-rpc.publicnode.com at finalized slot 452952737. The PVTY response was processed at 2026-10-03T13:54:13.321Z and the USDC response at 2026-10-03T13:54:13.405Z. We requested getAccountInfo with jsonParsed encoding and finalized commitment, validated the owner program and initialized mint type, and preserved the returned supply and authority fields. These are historical observations, not a promise that every field is unchanged when you read this.
02 / Explained
Claim 1: original issuance equals current total supply
PVTY's published original issuance is 50,000,000. The observed mint 8a9P2My6dUhKYJacztYv6bSjKJ1XZwTYY3qz5VwgcGML instead returned raw supply 49999989566655689 with 9 decimals: exactly 49,999,989.566655689 PVTY. That is 10.433344311 below original issuance. The current-supply-equals-original-issuance claim is therefore not supported by this snapshot.
The arithmetic is raw supply divided by 10 to the power of decimals, using integer/string arithmetic to avoid rounding. This observation alone does not identify each historical burn transaction, determine circulating supply or establish beneficial ownership. Those require separate history and account evidence.
03 / Explained
Claim 2: PVTY's base mint and freeze authorities are absent
The same PVTY response reports mintAuthority: null and freezeAuthority: null under the original SPL Token Program, TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA. This supports the narrow statement that those two base authorities were absent at the observed finalized slot.
It does not prove independent holder distribution, an LP lock, market depth, a sell route or a security audit. It also does not establish that every token account is unfrozen: account state is a separate check. A fixed supply cannot establish future demand or value.
04 / Explained
Claim 3: an existing authority by itself proves a scam
The comparison mint EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v, identified as USDC by Solana's documentation, returned a mint authority of BJE5MMbqXjVwjAF7oxwPYXnTXDyspzZyt4vwenNw5ruG and a freeze authority of 7dGbd2QZcCKcTndnHcTL8q7SMVXAkp688NTQYwrRCrar. Its raw supply was 8419503575335435 with 6 decimals, or 8,419,503,575.335435 for this mint at this slot.
The evidence establishes that controls exist; it does not determine whether a project is a scam or which asset someone should hold. Interpreting an authority requires the issuer's operating model and control disclosures. Conversely, removed authorities do not prove safety. The comparison is about fields, not a recommendation or assessment of USDC reserves, redemption rights or issuer risk.
05 / Explained
Reproduce the result instead of trusting the headline
Use the free Solana mint checker linked below with either full mint, or submit getAccountInfo directly to a mainnet RPC. Set encoding to jsonParsed and commitment to finalized. Compare result.context.slot, result.value.owner, data.parsed.type and the supply, decimals, mintAuthority and freezeAuthority fields in data.parsed.info.
The evidence download preserves the original response text, endpoint, retrieval time and SHA-256 digest for each returned response. A digest detects a change to that captured text; it does not authenticate the RPC provider or independently prove consensus. Repeating the request later gives a fresh slot and may give different state. Preserve the new timestamp rather than labelling an old snapshot live.
06 / Explained
Limitations and corrections
This study does not inspect all holders, Token-2022 extension controls, pool accounts or transactions. Neither observation checks liquidity, price, LP custody, exchange badges, metadata ownership or product adoption. Public RPC providers can be unavailable or inaccurate; a single-provider observation has that trust boundary.
PactVerity publishes the checker and this study and is associated with PVTY. Corrections can be sent to contact@pactverity.com with the public mint, method, slot and reproducible discrepancy. Do not send recovery phrases, private keys or confidential records. No token purchase is needed to reproduce the work.
Check the claim against a mint account
Use the read-only checker for any supported Solana mint. It shows source, UTC time, finalized slot and exact supply; it does not issue a safety score.
Sources and further research
- Raw dated mint observations, requests and response digests (JSON) ↗
- Solana: getAccountInfo method ↗
- Solana: mint account fields and USDC mint example ↗
- Solana: authority operations ↗
Shallow liquidity, high volatility and possible total loss. No guaranteed value or resale.
Related guides
- PVTY in Phantom and Jupiter: Mint Address & Swap Help
- How to Research a Solana Token Before a Swap
- Liquidity Lock vs Token Lock: What Is Actually Protected?
- Crypto Market Cap vs Liquidity: A Reproducible Example
- Bitcoin, Ethereum, Solana and Shiba Inu: Coins vs Tokens
- Crypto News Verification: Check Token Claims Before Acting