cryptosnif
SwissBorg (BORG)
Documentary contract0x64d0f55cd8c7133a9d7102b13987235f486f2224
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 SwissBorg (BORG) on the Ethereum network. The goal is to explain the stated aims of the token as recorded in community-maintained registries, without implying that an independent audit has occurred or that the project meets any safety standards.
Established facts
The pinned Trust Wallet Ethereum integration record identifies SwissBorg with the symbol BORG and contract address 0x64d0f55cd8c7133a9d7102b13987235f486f2224. The record specifies 18 decimal places for amount representation. This label does not measure supply or value. The registry entry describes SwissBorg as a crypto management app offering services such as exchanging crypto and fiat, earning yield, and accessing launchpad investment opportunities. It states the project was established during the ICO era of 2017 and claims over 1 million registered users by 2024. These statements are attributed registry claims from a community-maintained source, 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. A repeated approval overwrites the previous allowance. The wallet ERC20 label establishes no independently checked compliance or actual deployed implementation. The network context confirms the Ethereum blockchain hosts this record, but the active status is a metadata label with no live-network validation.
Unknowns
Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity, and complete incident history remain unverified. No deployed bytecode, current controllers, or network operation have been observed. The documentary mechanism alone cannot establish actual network behavior or investment outcomes. The registry scope excludes brand-new tokens and relies on community submissions, meaning inclusion does not imply a direct partnership with the listed projects.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The lack of independent verification means that operational strength remains unproven. Users relying on this information should understand that registry descriptions are promotional claims rather than factual audits of security or performance.
Verdict
Operational strength remains unproven; unrated with 0% scoring coverage. No public admission of risk or safety has been made. The dossier provides a useful documentary explanation of stated aims but does not constitute an independent operational verification.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to move beyond this unrated status. Calibration and editorial review following such evidence would 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 SwissBorg
The pinned Trust Wallet Ethereum integration record names SwissBorg with symbol BORG, contract 0x64d0f55cd8c7133a9d7102b13987235f486f2224 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: "SwissBorg is an all-encompassing crypto management app designed to offer services such as exchanging crypto and fiat, earning yield, and accessing launchpad investment opportunities. Established during the ICO era of 2017, it has amassed over 1 million registered users by 2024. The BORG is the token powering this revolutionary financial ecosystem." 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.