cryptosnif
Fei Protocol (FEI)
Documentary contract0x956f47f50a910163d8bf957cf5846d573e7f87ca
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.
Promise
This dossier examines the documented purpose and mechanisms of Fei Protocol (FEI) on the Ethereum network. The objective is to explain the stated aims of the token as recorded in community-maintained registries, without verifying live network operation or investment outcomes.
Established facts
The primary documentary record identifies the asset as Fei USD with the symbol FEI and contract address 0x956f47f50a910163d8bf957cf5846d573e7f87ca on the eip155:1 network. This entry exists within the Trust Wallet Assets repository, a community-maintained registry used by the wallet software. The registry labels the entry as ERC20 and active. Decimal places are noted as 18, which concerns amount representation rather than supply or value measurement. The community-maintained description states that this is the stablecoin created by Fei Protocol. These descriptions are attributed registry claims, not independently verified issuer statements. The general ERC-20 specification defines a standard interface for fungible tokens, including totalSupply, balanceOf, transfers, and allowances. An allowance permits a named spender to use a specified amount, with repeated approvals overwriting previous amounts. The ERC-20 standard also defines Transfer and Approval events. Name, symbol, and decimal metadata are optional under this specification. A wallet label of ERC20 establishes no independently checked compliance or actual deployed implementation. The network context confirms Ethereum uses the symbol ETH. Inclusion in the registry does not imply a direct partnership with the listed projects, and the registry excludes brand-new tokens from submissions. No live network observation, security audit, or operational verification was performed.
Unknowns
Independent control, beneficial ownership, actual usage, client adoption, supply distribution, concentration, liquidity, and complete incident history remain unverified. The registry status is a metadata label with no live-network validation. No deployed bytecode, controller permissions, reserve composition, or security posture has been established. The gap between the documentary claim of being a stablecoin and its actual economic niche remains unknown.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. Relying solely on registry labels risks conflating community-submitted descriptions with operational reality. Without independent verification, the stability mechanism and risk profile of the asset cannot be assessed. Users cannot infer safety, performance, or return from the presence of the asset in the integration registry.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage. Critical criteria including identity, supply, and control are missing essential evidence. The dossier provides a useful documentary explanation of stated aims but implies no independent audit has occurred. The verdict is based strictly on the absence of verified operational data.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to alter this status. Calibration and editorial review following such verification could enable a scored assessment. Until then, the unrated status stands due to lack of independent operational verification.
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: Observable usage, token necessity and dependencies.
Inspect the evidence
Sources behind this analysis
Trust Wallet: captured Ethereum record for Fei USD
The pinned Trust Wallet Ethereum integration record names Fei USD with symbol FEI, contract 0x956f47f50a910163d8bf957cf5846d573e7f87ca and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry ERC20 and active. Its community-maintained description states: "The stablecoin created by Fei Protocol" Every project, economic, partnership, performance, supply, date and adoption statement within this quoted description is an attributed registry claim, not an independently established issuer statement or operational observation. This dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The general ERC-20 specification is separate from this token implementation. Treat the generic application family as a documentary contract subject; its economic niche and scoring criteria remain unclassified and unknown.
Inspect the primary source ↗Trust Wallet Assets: blockchains/ethereum/info/info.json (bbe582d25a22)
The pinned wallet blockchain-information file names the network Ethereum, symbol ETH, and lists its project website and explorer. That named network context accompanies token records in the repository's Ethereum subtree. This identifies the documented integration network without reproducing its operation. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.
Inspect the primary source ↗Trust Wallet Assets: README.md (bbe582d25a22)
The Trust Wallet Assets README describes a community-maintained registry of token information and logos across blockchains, used by the wallet and other projects. It says additional token information is optional and unavailable on-chain. Anyone can submit assets, and inclusion does not imply a direct partnership with the listed projects. It also explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The README states that its scripts and documentation use the MIT license. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.
Inspect the primary source ↗Ethereum ERC-20: pinned token interface specification
The pinned ERC-20 specification describes a standard interface for fungible tokens in smart contracts. It defines totalSupply and balanceOf reads, transfers, third-party transfers after authorization, approval and remaining allowance. An allowance is the amount a named spender may use; a repeated approval overwrites that amount. The specification says callers must handle a false transfer result and describes Transfer and Approval events. Name, symbol and decimal-place metadata are optional in the standard. These interface requirements describe what a conforming implementation should do. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply or security. No token transaction was performed in this review. Copyright and related rights are waived under CC0.
Inspect the primary source ↗Only original summaries are distributed. Licensed raw market data stays private.