cryptosnif
Lista USD (lisUSD)
Documentary contract0x0782b6d8c4551b9760e74c0545a9bcd90bdc41e5
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 Lista USD (lisUSD) on the BNB Smart Chain network. The scope is limited to verifying the identity and stated aims found in community-maintained registry records. We do not verify deployed bytecode, current controllers, or live network operation. The goal is to establish what the documentation claims versus what has been independently observed.
Established facts
The pinned Trust Wallet integration record for BNB Smart Chain identifies Lista USD with the symbol lisUSD at documentary address 0x0782b6d8c4551b9760e74c0545a9bcd90bdc41e5. The record specifies 18 decimal places, a technical term referring to how token amounts are represented internally, which does not measure supply or value. The entry is labeled BEP20, indicating it conforms to the standard interface for fungible tokens on this network. The community-maintained description states that Lista DAO is a decentralized over-collateralized lending and liquid staking platform on the BNB chain. These statements are attributed registry claims from the wallet project's directory. They are not independently verified issuer statements or operational observations. The ERC-20 specification defines standard functions like totalSupply and balanceOf, but an ERC20 label establishes no independently checked compliance or actual deployed implementation. The Trust Wallet Assets README confirms this is a community-maintained registry where anyone can submit assets, and inclusion does not imply a direct partnership with listed projects. No live-network validation of deployment, control, or safety exists in this source.
Unknowns
Present independent control, beneficial ownership, usage patterns, client adoption, total supply, concentration of holdings, liquidity depth, and complete incident history remain unverified. The dossier may explain stated aims with attribution, but no deployed implementation rights or economic niche have been classified. Documentary address matching establishes no current program behavior or safety guarantees. The generic application family identifies only a documentary token subject; its specific scoring criteria remain unknown. No token transaction was performed in this review. The active status is a metadata label without live-network validation. Missing evidence does not make the project fraudulent or unsafe; it simply means these critical dimensions are outside the scope of this documentary check.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. Relying solely on registry labels risks conflating community-submitted descriptions with verified operational reality. Users must distinguish between the pinned registry claim of being a lending platform and any independently confirmed functionality. Without independent dated network observations, the gap between stated purpose and actual execution remains unbridged. This limits the ability to assess risk or utility based on current data.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage. No public admission of audit results or independent verification is available. The calculated scores reflect this lack of essential data, leaving identity, supply, and control as missing essentials. The verdict is strictly based on the absence of independent operational verification, not on negative findings.
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 assign a score. Until then, the dossier remains a documentary record of registry claims without operational validation. Concrete research questions include verifying the deployed bytecode against the documented address, confirming controller permissions through on-chain analysis, and assessing actual user adoption metrics separate from registry labels.
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 BNB Smart Chain record for Lista USD
The pinned Trust Wallet BNB Smart Chain integration record names Lista USD with symbol lisUSD, documentary address 0x0782b6d8c4551b9760e74c0545a9bcd90bdc41e5 and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry BEP20 and active. Its community-maintained description states: "TWhat is Lista DAO (lisUSD)Lista DAO is a decentralized over-collateralized lending and liquid staking platform on the BNB chain." 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. The dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified and unknown. The general ERC-20 specification is separate from this token implementation.
Inspect the primary source ↗Trust Wallet: pinned BNB Smart Chain directory context
The pinned Trust Wallet smartchain network-context record identifies the community registry directory for BNB Smart Chain. This supplies documentary network context for entries in the same pinned directory. Promotional statements, network performance, consensus behavior, current deployment and control are not verified or admitted from this context.
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.