Automated Website Trust Scores
TokenOps/BEX may be evaluated by automated website trust or scam-rating services such as Scam Detector, ScamAdviser, or similar platforms. This FAQ explains how to interpret those signals for an early-stage blockchain platform.
Automated website trust scores are useful signals, but they are not a complete technical, legal, or on-chain assessment.
Why can new blockchain or Web3 projects receive low automated trust scores?
Early-stage blockchain projects may receive conservative ratings because automated systems rely heavily on domain age, reputation history, traffic, backlinks, and public third-party references.
- young domain age
- limited traffic history
- limited backlink profile
- limited third-party reviews
- limited public company footprint
- crypto or blockchain terminology triggering higher-risk classification
- lack of long historical reputation data
Does a low automated website score mean TokenOps or BEX is unsafe?
Not automatically. Automated scores are one signal, not a full technical audit, legal review, or blockchain-level verification. Users should review multiple sources before deciding whether to interact with any Web3 platform.
TokenOps is improving public transparency through documentation, legal pages, team visibility, LinkedIn presence, a public security transparency repository, and a dedicated Security & Transparency page.
How are automated website trust scores different from BEX trust signals?
Automated website scanners mainly evaluate website and domain reputation. BEX is designed to evaluate blockchain-project-level transparency.
BEX trust signals are designed to focus on verifiable project-level and on-chain evidence, not only website reputation. BEX focuses on burn events, ownership or authority signals, on-chain payment verification, project activity, and public evidence that can be inspected over time.
Has TokenOps contacted third-party rating platforms for reassessment?
TokenOps has prioritized product completion and core transparency infrastructure first. Now TokenOps is building the public documentation footprint needed for future review or reassessment requests where appropriate.
We do not claim that every negative automated score is wrong, and we do not promise guaranteed score improvement.
What is TokenOps doing to increase transparency?
- publishing a TokenOps LinkedIn presence
- publishing team and company information
- adding Risk, Terms, and Privacy pages
- adding a Security & Transparency page
- documenting the non-custodial wallet and payment model
- publishing a public GitHub security transparency repository
- supporting responsible disclosure through the public transparency reference
Why does TokenOps publish a public security transparency repository?
The public repository documents the non-custodial wallet and payment architecture. It explains that users sign transactions directly in their own wallets and that TokenOps/BEX does not receive, store, or control private keys, seed phrases, or wallet credentials.
The repository supports independent review of security-relevant architecture while protecting proprietary business logic.
Can I review the BEX security model myself, even if I am not a developer?
Yes. The public GitHub transparency repository was created to make the customer-relevant wallet and payment architecture easier to review. Even if you are not a developer, you can share the GitHub link or selected files with an AI assistant, an independent developer, or a security-aware reviewer.
A useful review should check whether the documented flow ever requests seed phrases, private keys, wallet passwords, or custody over user funds. The repository is designed to make the non-custodial architecture easier to understand, but it is a transparency reference, not the full proprietary source code, and it does not replace a formal security audit.
Users should still review wallet prompts carefully before signing any transaction. Never share seed phrases or private keys with TokenOps, BEX, an AI assistant, or anyone else.
Should users rely only on automated trust scores?
No. Users should review website and legal pages, GitHub references, social profiles, team visibility, wallet prompts, and on-chain evidence. Users should never share seed phrases or private keys with any platform.