cryptosnif
Swarm Markets (SMT)
Documentary contract0xb17548c7b510427baac4e267bea62e800b247173
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 Swarm Markets (SMT) on the Ethereum network. The goal is to explain the stated aims of this token based on available registry records, without implying that an independent audit or operational verification has occurred.
Established facts
The pinned Trust Wallet Ethereum integration record identifies Swarm Markets with the symbol SMT and contract address 0xb17548c7b510427baac4e267bea62e800b247173. This record specifies 18 decimal places for amount representation, a technical detail that does not measure supply or value. The entry is labeled ERC20 and active within the community-maintained registry. The general ERC-20 specification defines a standard interface for fungible tokens in smart contracts, including functions for total supply, balance checks, transfers, and allowances. An allowance permits a named spender to use a specified amount, where repeated approval overwrites the previous limit. The specification also outlines optional metadata such as name, symbol, and decimals. The wallet blockchain-information file confirms the network context as Ethereum, providing the project website and explorer links associated with the token record. These sources establish the documentary identity and technical classification but do not verify live network operation.
Unknowns
Present independent control, beneficial ownership, usage patterns, client adoption, total supply distribution, concentration of holdings, liquidity depth, and complete incident history remain unverified. The registry description attributes claims about being a licensed DeFi platform and a unified exchange for securities and crypto to the community-maintained entry. These are attributed registry claims, not independently established issuer statements or operational observations. No deployed implementation, rights, safety, or investment outcome was checked. The active status is a metadata label with no live-network validation. A documentation review is not an independent operational verification.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. Without independent dated network observations, it is impossible to confirm if the contract implements the ERC-20 standard correctly or if the stated economic niche is functioning as described. The lack of verified supply and control data prevents any assessment of risk or utility. Users relying solely on registry labels may misinterpret metadata status as proof of operational security or regulatory compliance.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage. Critical essential criteria including identity verification beyond registry listing, supply transparency, and control structure are missing. The current evidence supports only a documentary explanation of stated aims, not an evaluation of performance or safety.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to move from an unrated status to a scored assessment. Calibration and editorial review must follow the collection of these independent proofs to assign a meaningful 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: Observable usage, token necessity and dependencies.
Inspect the evidence
Sources behind this analysis
Trust Wallet: captured Ethereum record for Swarm Markets
The pinned Trust Wallet Ethereum integration record names Swarm Markets with symbol SMT, contract 0xb17548c7b510427baac4e267bea62e800b247173 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: "Swarm Markets is a licensed DeFi platform a unified exchange for securities and crypto. Swarm Markets makes it possible for institutional and retail investors to trade tokens based on all kinds of real-world assets, such as commodities and traditional market securities." 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.