cryptosnif
USDC (USDC)
Documentary contract0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
Unrated · 0% Evidence coverage
Operational strength remains unproven; unrated with 0% scoring coverage.
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.
Inspect the evidenceThe source review explains documented mechanisms. Independent network checks remain pending.
Examined promise
This dossier examines the pinned project documentation for USDC (USDC). The documentary subject is the token address 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 on Ethereum mainnet. The review establishes a documentary research scope and leaves current deployment and operation unverified.
Established facts
The Compound mainnet configuration lists USDC at 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48. This is Compound project documentation of its token integration on Ethereum, rather than an issuer deployment verification. The entry identifies the documentary subject and makes no assertion about present reserves, redemption rights, stable price or running implementation.
The Compound project describes its supply and borrowing contracts as Ethereum contracts. This supplies the network context for its separate mainnet USDC registry entry. Nothing here verifies the issuer, the deployment at that address or current monetary backing.
Circle FiatToken documentation describes an ERC-20-compatible design with pausing, blacklisting, upgrades, minting and burning. A pauser can freeze transfers in the described design; a blacklister restricts listed addresses. The master minter controls minter allowances, while the owner can change several administrative roles and the proxy owner controls upgrades. A proxy forwards calls to an implementation contract. These documented roles are distinct research questions: the exact live code, current role holders, issuer reserve assets, redemption terms and economic outcomes were not checked.
Unknowns
This dossier contains no independently reproduced operational observations. Current deployed versions, controller identities, beneficial ownership, usage, supply, concentration, liquidity and the complete incident record remain unverified within this review.
Consequences
The issuer implementation describes several distinct administrative roles. A fuller review would first identify the deployed implementation and role holders, then examine issuer reserves and redemption terms using their own dated evidence.
Verdict
Unrated, with 0% scoring coverage. The captured documentation establishes the scope of further research, while every operational scoring criterion remains unknown. No total score or investment-return forecast follows from this corpus.
Evidence that would change it
A further review would compare the documented identities with deployed code, identify current control powers and reproduce mechanism-specific observations with dates and test conditions. Supply, usage and incident evidence would then require separate checks before method calibration and editorial review could support a score.
Each check earns its result.
| Check | Weight | Result |
|---|---|---|
| Exact asset identityEssential | 3% | Verification pending |
| Observable use | 15% | Verification pending |
| Economic role of the token | 10% | Verification pending |
| Supply mechanismsEssential | 10% | Verification pending |
| Ownership concentration | 8% | Verification pending |
| Value capture | 7% | Verification pending |
| Control powersEssential | 10% | Verification pending |
| Security verification | 7% | Verification pending |
| Decision process | 8% | Verification pending |
| Accountability | 7% | Verification pending |
| Incident history | 6% | Verification pending |
| Operational continuity | 4% | Verification pending |
| Execution conditions | 5% | Verification pending |
Family-specific checks: Reserves, redemptions, collateral and peg stability.
Inspect the evidence
Sources behind this analysis
compound-finance/compound-protocol: networks/mainnet.json (a3214f67b733)
The Compound mainnet configuration lists USDC at 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48. This is Compound project documentation of its token integration on Ethereum, rather than an issuer deployment verification. The entry identifies the documentary subject and makes no assertion about present reserves, redemption rights, stable price or running implementation. This review read the pinned primary files and their licence captures. No deployed bytecode, transaction, network node, controller balance or governance vote was independently inspected. Current ownership, concentration, operational activity, market conditions and complete incident history remain unknown. These documentary observations provide no scoring coverage or forecast of investment returns.
Inspect the primary source ↗compound-finance/compound-protocol: README.md (a3214f67b733)
The Compound project describes its supply and borrowing contracts as Ethereum contracts. This supplies the network context for its separate mainnet USDC registry entry. Nothing here verifies the issuer, the deployment at that address or current monetary backing. This review read the pinned primary files and their licence captures. No deployed bytecode, transaction, network node, controller balance or governance vote was independently inspected. Current ownership, concentration, operational activity, market conditions and complete incident history remain unknown. These documentary observations provide no scoring coverage or forecast of investment returns.
Inspect the primary source ↗circlefin/stablecoin-evm: README.md (fc85788bc7c2)
Circle FiatToken documentation describes an ERC-20-compatible design with pausing, blacklisting, upgrades, minting and burning. A pauser can freeze transfers in the described design; a blacklister restricts listed addresses. The master minter controls minter allowances, while the owner can change several administrative roles and the proxy owner controls upgrades. A proxy forwards calls to an implementation contract. These documented roles are distinct research questions: the exact live code, current role holders, issuer reserve assets, redemption terms and economic outcomes were not checked. This review read the pinned primary files and their licence captures. No deployed bytecode, transaction, network node, controller balance or governance vote was independently inspected. Current ownership, concentration, operational activity, market conditions and complete incident history remain unknown. These documentary observations provide no scoring coverage or forecast of investment returns.
Inspect the primary source ↗Only original summaries are distributed. Licensed raw market data stays private.