Reflecto
Reflecto (RTO) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).
Reflecto — a token project on the BNB Smart Chain network (BEP‑20). Tier‑1 sources (website/whitepaper) claim AI components/products, but verifiable artifacts (metrics/architecture/demo) are not established per Tier‑1.
Disclaimer
Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.
TL;DR (for readers who are not into AI)
- What it is: a BEP‑20 token and an ecosystem/products described in the whitepaper (Tier‑1).
- Who it’s for: users of the ecosystem/community (claimed).
- Why onchain/token: the token contract on BSC is confirmed; the necessity of the token as a mandatory mechanism of the product is not established per Tier‑1.
How it works (very briefly)
- The user does: interacts with the token/products of the ecosystem (claimed).
- The system does: provides the claimed features (details are not established per Tier‑1).
- The user gets: access/features of the ecosystem (claimed).
- Where the blockchain is: the Reflecto token contract on BNB Smart Chain is confirmed.
- Token role (if any): the token exists; the specific necessity of the token (payment/incentives/governance) is not established per Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Reflecto |
| Also known as (aliases) | Reflecto Coin; RTO |
| Logo (logo) | ../assets/548_reflecto_logo.svg |
| Token symbol (ticker) | RTO |
| Category | AI/Other |
| Primary chain (chain) | BNB Smart Chain |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoSA (BNB Smart Chain; 21 validators) |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | BEP-20 |
| Token contract | 0x5A341DCF49e161CC73591f02e5f8CDE8A29733fb |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | yes |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI features/products |
| Use‑case (use_case) | token ecosystem |
| DecAI Fit — AI thesis fit | 2/6 — low alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 1 / 1 / 0 / 1 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://reflectocoin.com |
| Docs | https://reflectocoin.com/assets/docs/safunet-whitepaper.pdf |
| GitHub | — |
| Releases / Changelog | https://medium.com/@reflectocoin |
| Whitepaper | https://reflectocoin.com/whitepaper |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://bscscan.com/token/0x5A341DCF49e161CC73591f02e5f8CDE8A29733fb |
| X | https://twitter.com/reflectocoin |
| Discord | https://discord.com/invite/jsqp2chuPY |
| Telegram | https://t.me/reflectocoin |
| Medium | https://medium.com/@reflectocoin |
| Audit report(s) | https://reflectocoin.com/assets/docs/audit-report.pdf |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/reflecto |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/reflecto/ |
General project overview
Reflecto is a token project on BNB Smart Chain. The project’s Tier‑1 documents/pages claim ecosystem elements and AI components; however, verifiable AI artifacts (metrics/architecture/demo) and the necessity of the token in the product are not established per Tier‑1.
Features/modules
- Whitepaper/ecosystem documents (Tier‑1: links_*).
- Audit document (the link is in links_*; third‑party report).
Typical scenarios
- Scenario 1: a user interacts with the token → gets onchain operations (BSC).
- Scenario 2: a user uses the products/features of the ecosystem → details are not established per Tier‑1.
Getting started (wallet/network)
- What you need: a BSC wallet and the token address/contract (see links_*).
- Network/chain: BNB Smart Chain.
- Fees: BSC fees (gas) for transactions.
Architecture/tech (non‑AI)
- Components: the token contract on BSC + offchain components of the ecosystem (details not established).
- Participant roles: users/token holders.
- Where logic runs: onchain is confirmed at the token level; the rest — not established.
- Dependencies: — (not found per Tier‑1).
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1 (other than the fact of the token’s existence).
- Protocol necessity drivers: not established.
- Who pays fees: BSC users for transactions.
- Where fees go: to BSC validators (gas).
- Issuance/burn: — (not established).
- Security/incentive mechanisms: — (not established).
- Distribution and token issuance schedule: — (not established).
- Treasury: — (not established).
Governance
- Who makes decisions: — (not established).
- How protocol parameters change: — (not established).
- Where decisions are discussed/made: — (not established).
- Keys/multisig: — (not established).
Security and incidents
- Audits: there is a link to an audit report in links_*.
- Bug bounty: —.
- Incidents: — (not found per Tier‑1).
- Threat model: the utility is not confirmed; AI is also claimed without supporting artifacts.
Project status and timeline
- Current status: mainnet (based on the presence of the contract on BSC).
- Key releases/milestones: — (not established).
- Roadmap: —.
Ecosystem/integrations
- Integrations: — (not established per Tier‑1).
- Partners: — (not established per Tier‑1).
- Where it’s actually used: — (not established per Tier‑1).
AI component of the project
- What is real AI here? Tier‑1 sources claim AI elements, but no metrics/architecture/demo were found per Tier‑1.
- What is truly onchain? The token contract on BNB Smart Chain is confirmed.
- Why is a token needed? The existence of the token is confirmed; the necessity of the token in the product is not established per Tier‑1.
- Red flags (based on the information found): the risk of “AI‑washing” and token‑washing; the whitepaper/docs and the actual products require re‑checking.
DecAI Fit component summary
- DecAI Fit: 2/6 — low alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | low | 1 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 partial | 1 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 1
- Claim (one line): the project’s Tier‑1 sources claim AI components/products.
- Evidence: Tier‑1 — https://reflectocoin.com/whitepaper
- Why sufficient / why not (one line): this is intent; without metrics/architecture per Tier‑1.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): a verifiable description of the functions of the AI part is not established per Tier‑1.
- Evidence: Tier‑1 — https://reflectocoin.com/whitepaper
- Why sufficient / why not (one line): insufficient specifics for 1 → 0.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): a Tier‑1 demo/example of the AI products is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no Tier‑1 demo → 0.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: not found.
- Context (version/date/how measured): not found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): metrics not found → 0.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): the tech description/architecture of the AI part is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): insufficient data → 0.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: BNB Smart Chain
- Addresses/identifiers: Reflecto token (BEP‑20): 0x5A341DCF49e161CC73591f02e5f8CDE8A29733fb
- Evidence: Tier‑1 — https://bscscan.com/token/0x5A341DCF49e161CC73591f02e5f8CDE8A29733fb
- Why sufficient / why not (one line): the existence of the onchain artifact is confirmed by the explorer.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: not established (other than the token).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no grounds for 1 were found → 0.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established (strictly).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): insufficient justification → 0.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a token, Reflecto (BEP‑20).
- Evidence: Tier‑1 — https://bscscan.com/token/0x5A341DCF49e161CC73591f02e5f8CDE8A29733fb
- Why sufficient / why not (one line): the existence of the token is confirmed by the contract.
- Conflict note (if any): —
TK_1..TK_4 (1/0)
TK_1 — payment for the service (1/0)
- TK_1 (decision): 0
- Claim (one line): Tier‑1 confirmation of payment for services with the token is not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): without confirmation → 0.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): incentives/collateral/penalties via the token are not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no grounds for 1 were found → 0.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): governance via the token is not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): no grounds for 1 were found → 0.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): the replaceability of the token is not established.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): insufficient data → 0.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://reflectocoin.com/whitepaper | intent: whitepaper/positioning and the context of the ecosystem |
| Tier‑1 | https://bscscan.com/token/0x5A341DCF49e161CC73591f02e5f8CDE8A29733fb | onchain: the token contract on BSC |
| Tier‑2 | https://reflectocoin.com/assets/docs/audit-report.pdf | audit (third‑party report; not Tier‑1) |
| Tier‑1 | — | Tier‑1 sources on the necessity of the token (payment/incentives/governance) are not established. |
| Tier‑2 | https://coinmarketcap.com/currencies/reflecto/ | reference token profile (not proof of utility) |
| Tier‑3 | — | — |
No comments to display
No comments to display