cryptosnif
Magic Square (SQR)
Documentary contract0x2b72867c32cf673f7b02d208b26889fed353b1f8
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 Magic Square (SQR) on the eip155:56 network. The objective is to evaluate the claims associated with this asset based strictly on available documentary records, without inferring current operational status or investment viability.
Established facts
The pinned Trust Wallet BNB Smart Chain integration record identifies Magic Square with the symbol SQR at documentary address 0x2b72867c32cf673f7b02d208b26889fed353b1f8. This entry uses eight decimal places for amount representation, a technical detail that defines precision but does not measure supply or value. The registry labels the token as BEP20, which refers to the specific implementation of the ERC-20 standard adapted for the BNB Smart Chain. The community-maintained description states that Magic Square aims to be at the forefront of the Web3 space by featuring a vetted Web3 App Store called the Magic Store, offering curated apps, games, and an advanced Loyalty System. These statements are attributed registry claims from a community-maintained directory where anyone can submit assets. Inclusion in this registry does not imply a direct partnership with the listed projects, nor does it verify deployed bytecode, current controllers, or live network operation. The general ERC-20 specification defines a standard interface for fungible tokens, including functions for reading total supply and balances, executing transfers, and managing allowances, which is the amount a named spender may use. However, a wallet ERC20 label establishes no independently checked compliance or actual deployed implementation.
Unknowns
Present independent control, beneficial ownership, usage patterns, client adoption rates, total supply distribution, concentration of holdings, liquidity depth, and complete incident history remain unverified. No live network observation was performed to confirm if the contract at the documented address matches the described functionality or if it is currently active. The dossier may explain stated aims with attribution, but no economic niche, scoring criteria, or operational safety has been established through independent verification.
Consequences
Documentary mechanisms alone cannot establish actual network behavior, security posture, or investment outcomes. Without independent dated network observations, the gap between the registry description and the live smart contract state remains unbridged. Users relying solely on this registry entry lack verified data on who controls the contract, how tokens are distributed, or whether the promised loyalty system functions as described.
Verdict
Operational strength remains unproven. The asset is unrated with zero percent scoring coverage. Critical missing elements include identity verification, supply confirmation, and control analysis. The current evidence base is insufficient to assign any score or validate the project's claims beyond its presence in the community registry.
What would change it
Reproduced identity checks confirming the contract address matches the issuer, independent dated network observations verifying active deployment and behavior, and criterion-specific evidence covering usage, supply, control, and security would be required. Calibration and editorial review following such independent 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 BNB Smart Chain record for Magic Square
The pinned Trust Wallet BNB Smart Chain integration record names Magic Square with symbol SQR, documentary address 0x2b72867c32cf673f7b02d208b26889fed353b1f8 and 8 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: "Magic Square is at the forefront of the Web3 space, featuring the unique 'Magic Store' - a vetted Web3 App Store with a curated range of apps, games, and an advanced Loyalty System." 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.