Purpose
This page helps users identify official ASTROC2M resources before opening an application,
connecting a wallet, signing a message, or interacting with a smart contract.
The Trust Center is a verification reference, not a guarantee that every external device,
wallet, browser extension, network provider, or third-party service is risk-free.
Verification standard. Official production domains and contract addresses are listed publicly.
Experimental or retired environments are clearly separated from current entry points.
Ecosystem purpose and utility
ASTROC2M is an educational, gamified, and community-oriented Web3 ecosystem. Its NFTs and token are
designed for interaction with project experiences, learning modules, access features, rewards,
progression systems, simulations, and other ecosystem functions.
Ecosystem utility
Internal interaction
ASTROC2M NFTs and tokens are presented as utility components intended for participation and
interaction within the ASTROC2M ecosystem.
Project purpose
Continued development
Primary NFT sales are intended to support the continued development and operation of the
ASTROC2M ecosystem.
Important notice
No financial rights or guarantees
These digital assets do not represent equity, debt, ownership, revenue participation, dividends,
or any promise of profit, appreciation, liquidity, resale availability, or financial return.
Public blockchain
Independent third-party activity
External transfers, listings, or third-party market activity may occur independently and do not
represent a guarantee, recommendation, or endorsement by ASTROC2M.
Utility-first principle. Participation should be based on access, interaction, learning,
and ecosystem use rather than an expectation of financial return.
Official domains
Use the links below as the official ASTROC2M entry points. Check the complete hostname before any wallet action.
Official
Institutional
astroc2m.com
Main ecosystem website, institutional information, official documentation, FAQ, and project references.
Official
Education
astroc2m.space
Web3 education hub, security guidance, learning resources, and this Trust Center.
Official
Application
app.astroc2m.com
Official application and NFT interaction layer. Wallet requests should appear only after a user-initiated action.
Official
Game Hub
hub.astroc2m.com
Official hub for game-related experiences, ecosystem modules, access features, and community interaction layers.
Legacy environment: play.astroc2m.space was used as an early experimental game environment
and is not the current production entry point. Use hub.astroc2m.com for current Hub access.
Official smart contracts
Match the complete address shown in your wallet or application against the references below.
A similar name, logo, or shortened address is not sufficient verification.
ERC-721
Polygon
Source verified
No audit listed
NFTASTROC2M Collection
On-chain contract name: Astroc2mDynamicEraNFT
Purpose: NFT collection, access layer, minting, gifting, and bonus mechanics.
Contract address
0x7bd589a507f6140fCD65158fc30A44d0D035d8DF
ERC-20
Polygon
Source verified
No audit listed
ASTROC2M Token
On-chain contract name: ASTROCHIMPSGOTOTHEMOON
Purpose: Ecosystem utility token used across ASTROC2M modules.
Contract address
0x59fa5D8ec6074Cb67dda26E447506c510d940A07
Verification is not the same as an audit. PolygonScan currently shows exact-match verified source code
for both contracts, but no external security audit is listed there as of July 17, 2026. This statement avoids overstating
the security status while keeping the contracts publicly verifiable.
External reputation review and false-positive resolution
Wallet warnings and external reputation alerts must be treated seriously, even when they may result from an
incorrect classification. In May 2026, a “Malicious address” warning appeared during a standard mint transaction
simulation involving the official ASTROC2M NFT contract on Polygon.
No funds were lost and no transaction was confirmed. ASTROC2M paused the affected interaction flow, reviewed the
frontend and NFT metadata, documented the official domains and contracts, and submitted a public false-positive
review request through the MetaMask eth-phishing-detect repository.
False-positive review resolved. The public MetaMask repository issue was closed after indicating
that the domain was not present on the eth-phishing-detect list and was being blocked through another
external list. Blockaid subsequently confirmed in writing that its review found the flagging of the official
ASTROC2M NFT contract and astroc2m.com to be incorrect and that the classification was modified.
Public review
Closed
MetaMask eth-phishing-detect
Request opened: May 9, 2026
Issue: #244637 — Blocklist removal request for official ASTROC2M domains.
Repository result: Closed with the label “other list blocked,” meaning the flagged domain was
not present on the MetaMask eth-phishing-detect list and was blocked through another list.
External provider
Resolved
Blockaid false-positive appeal
Written response received: May 21, 2026
Resources reviewed: astroc2m.com and the official ASTROC2M NFT contract
0x7bd589a507f6140fCD65158fc30A44d0D035d8DF.
Provider finding: Blockaid stated that the flagging was incorrect and that the classification
was modified accordingly.
-
MetaMask public request
Closed
-
eth-phishing-detect status
Domain not present on that list
-
Blockaid appeal
Review completed
-
Blockaid finding
Incorrect flagging modified
-
Reported user loss
None
-
Confirmed transaction
None
Important limitation. This resolution concerns an incorrect external reputation or blocklist
classification. It is not a smart-contract audit, penetration test, security certification, endorsement, or
guarantee that every interaction is risk-free. ASTROC2M does not currently claim an independent external
smart-contract audit.
Wallet interaction standard
ASTROC2M applications may request a wallet connection, signature, approval, or transaction when the user starts an action
that requires blockchain interaction. Every request should be reviewed before confirmation.
Recommended wallet practice. Always use a dedicated secondary wallet for Web3 and ASTROC2M interactions,
and keep only the amount required for the intended activity. Do not connect your primary wallet or any wallet containing
significant funds, valuable NFTs, or long-term holdings.
- ASTROC2M will never ask for a seed phrase, private key, recovery phrase, or wallet backup file.
- Confirm that the wallet is connected to the intended Polygon network before submitting a transaction.
- Check the destination contract address and requested permission in the wallet confirmation screen.
- Cancel any request that appears unexpectedly or does not match the action you initiated.
- Review token spending limits and avoid unnecessary unlimited approvals.
How to verify an ASTROC2M resource
- Start from an official domain listed in this Trust Center.
- Check spelling, HTTPS, the complete hostname, and any subdomain before proceeding.
- Compare the complete smart contract address with the address published above.
- Open the address directly on PolygonScan and confirm the network, token tracker, and verified source status.
- Review the wallet action, value, recipient, and approval scope before confirming.
- Do not treat screenshots, shortened URLs, direct messages, or copied addresses as independent proof.
Official communications and security reporting
Infrastructure updates, contract references, and official entry points should remain consistent with the information
published on ASTROC2M-controlled domains.
Suspicious domains, impersonation attempts, unexpected wallet prompts, conflicting contract addresses, or other
security concerns should be reported through the official project contact channel.
Include useful evidence: the complete URL, wallet address or contract address, screenshots with sensitive
information removed, the date and time of the event, and the transaction hash when applicable. Never send a seed phrase,
private key, recovery phrase, password, or wallet backup file.
Security commitment
ASTROC2M treats security as an ongoing process based on public references, clear separation of environments,
user education, responsible disclosure, and progressive improvement of operational controls.
Core principle. Trust should be supported by verifiable information and transparent limitations,
not by promises that no system can responsibly guarantee.