cryptosnif
PolySwarm (NCT)
Documentary contract0x9e46a38f5daabe8683e10793b06749eef7d733d1
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 PolySwarm (NCT) on the Ethereum network. The goal is to explain the stated aims of the project as recorded in community-maintained registries, without implying that an independent audit or operational verification has occurred.
Established facts
The pinned Trust Wallet Ethereum integration record identifies Nectar with symbol NCT at contract address 0x9e46a38f5daabe8683e10793b06749eef7d733d1. This entry specifies 18 decimal places for amount representation and labels the asset as ERC20 and active. The registry description states that PolySwarm is a more effective way to detect, analyze and respond to threats likely to go undetected by existing solutions. These statements are attributed registry claims, not independently established issuer statements. The network context confirms the integration occurs on Ethereum, identified by symbol ETH. The Trust Wallet Assets repository is a community-maintained registry where anyone can submit assets. Inclusion does not imply a direct partnership with listed projects, and the active status is a metadata label without live-network validation. The 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 specified amount, which can be overwritten by repeated approvals. A wallet ERC20 label establishes no independently checked compliance or actual deployed implementation.
Unknowns
Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity and complete incident history remain unverified. No deployed bytecode, controller permissions, token use, security audit results or investment returns have been established. The general ERC-20 specification is separate from this specific token implementation, and it is unknown if this contract implements the interface correctly. Documentary mechanisms alone cannot establish actual network behavior.
Consequences
Because the scoring coverage is 0%, the asset remains unrated. The absence of verified operational data means that the documentary claims about threat detection capabilities cannot be linked to actual performance or safety outcomes. Users relying solely on registry labels cannot assess the technical integrity or economic viability of the token.
Verdict
Operational strength remains unproven. The dossier provides a documentary explanation of the stated purpose but assigns no score due to zero evidence coverage across all criteria. The asset is classified as unrated.
What would change it
Reproduced identity checks, independent dated network observations and criterion-specific evidence would be required to move beyond this documentary status. Calibration and editorial review following such verification could allow for a scored assessment.
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 Nectar
The pinned Trust Wallet Ethereum integration record names Nectar with symbol NCT, contract 0x9e46a38f5daabe8683e10793b06749eef7d733d1 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: "PolySwarm is a more effective way to detect, analyze and respond to the latest threats, the ones more likely to go undetected by existing solutions." 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.