cryptosnif
Basis Cash (BAC)
Documentary contract0x3449fc1cd036255ba1eb19d65ff4ba2b8903a69a
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 Basis Cash (BAC) on the Ethereum network. The goal is to explain the stated aims of this token based on registry records, while clearly distinguishing between project claims and independent verification.
Established facts
The Trust Wallet Ethereum integration record identifies Basis Cash with the symbol BAC and contract address 0x3449fc1cd036255ba1eb19d65ff4ba2b8903a69a. This entry specifies 18 decimal places for amount representation. The record labels the asset as ERC20 and active. The community-maintained description states that Basis Cash is an open source, permissionless stablecoin pegged to USD. It explains that the protocol is designed to expand and contract supply similarly to how central banks manage fiscal debt to stabilize purchasing power, without using REBASES or risking collateral. These statements are attributed registry claims from a community-maintained repository. The repository allows anyone to submit assets, and inclusion does not imply a partnership with the listed projects. The general ERC-20 specification defines a standard interface for fungible tokens, including functions for total supply, balance checks, transfers, and allowances. An allowance permits a named spender to use a specific amount of tokens. This specification describes what a conforming implementation should do, but the wallet label establishes no independently checked compliance or actual deployed implementation.
Unknowns
No live network observation was performed. Independent control, beneficial ownership, usage patterns, client adoption, supply distribution, concentration, liquidity, and complete incident history remain unverified. The documentary mechanism alone cannot establish actual network behavior or investment outcomes. No deployed bytecode, controller permissions, or security audits have been confirmed in this review.
Consequences
Because the operational strength remains unproven, the asset carries an unrated status with zero percent scoring coverage. Users relying on this documentation cannot infer safety, performance, or return potential from the registry entry alone. The distinction between the generic ERC-20 interface and the specific contract implementation remains unvalidated.
Verdict
Operational strength remains unproven; the asset is unrated with 0% scoring coverage. The provided summaries describe pinned primary documentation and software context only. No independent verification of the contract's actual function or economic impact has occurred.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to move beyond this documentary assessment. Calibration and editorial review following such verification could alter the unrated status.
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 Basis Cash
The pinned Trust Wallet Ethereum integration record names Basis Cash with symbol BAC, contract 0x3449fc1cd036255ba1eb19d65ff4ba2b8903a69a 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: "Basis Cash is an open source, permissionless stablecoin pegged to USD. The protocol is designed to expand and contract supply similarly to the way central banks buy and sell fiscal debt to stabilze purchasing power, without any REBASES or risking colletrals." 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.