Provider-level evidence
Route notes with unmerged identities
Site or app primary route current
3Commas route note
The current provider-controlled route begins at the 3Commas website or mobile app. Telegram appears as an integration layer, not as evidence that any Telegram signal source, marketplace seller, or exchange account is operated by 3Commas.
Observed route anchors
- 3commas.io website
- 3Commas mobile app
- Telegram integrations
Gates or collision markers
- global and EEA service routes use different contracting entities
- connected signal and exchange accounts remain separate counterparties
Frozen platform context
Website, mobile app, exchange API automation, and Telegram integrations
Conflict context retained from the dossier
- The global and EEA routes use different contracting entities and legal regimes, so the applicable operator cannot be stated without the user’s route and residence.
- Non-custodial and no-withdrawal language coexists with exchange trade authority; it limits custody risk but does not remove unauthorized-trade or configuration risk.
- Platform backtest and marketplace outputs can be mistaken for 3Commas-wide profitability even though performance is strategy- and signal-source-specific.
Selected exact route risks
- risk[0] Exchange API permissions can place and close real trades even when withdrawal permission is disabled.
- risk[3] Connected Marketplace signals, webhooks, and bot settings add third-party and configuration risk.
Selected exact missing proof
- missingProof[1] Each connected signal source still needs its own loss-inclusive record and operator review.
- missingProof[2] The user’s exact route, governing operator, taxes, and EEA refund terms must be confirmed at checkout.
- missingProof[3] A current independent security assessment covering the user’s intended exchange connection was not established by this research.
Source-preserved safest action
Use the correct regional route and test with a segregated exchange subaccount, minimal capital, 2FA, no withdrawal permission, IP allowlisting or Fast Connect, trade alerts, and a tested emergency stop; evaluate every connected signal source separately.
Attribution limit: The frozen packet contains a current provider-controlled website or application route that is primary for access. That route attribution does not verify every operator, connected account, support contact, safety control, user acceptance decision, or performance claim. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Assigned route dormant, historical, or reassigned
4C Trading Signals route note
The assigned 4C network is historical: @News_4CTrading still points to 4c-trading.com, but the feed is stale and the domain does not expose a current service. Competing same-name Telegram handles remain separate because no historical primary route cross-links them.
Observed route anchors
- historical @News_4CTrading Telegram channel
- historical 4c-trading.com website
- historical 4C Trading GitBook
Gates or collision markers
- latest visible assigned-channel post is dated 2023-02-27
- current website is only a coming-soon page
- @trading4Csignals1 and @trading4csignals are unlinked same-name routes
Frozen platform context
Telegram and historically a website dashboard with exchange API bot connections
Conflict context retained from the dossier
- The historical official Telegram route still points to 4c-trading.com, but that domain currently shows only a coming-soon page.
- The historical official channel’s latest visible post is dated 2023-02-27, so it does not establish a current offer.
- The residual 4ctradingsignals.com review page links @trading4Csignals1, while @trading4csignals separately calls itself the only official channel; neither is cross-linked from the historical official network.
- The residual same-name review page contains generic testimonials and the unfilled placeholder [Crypto Signals Company].
- The historical @ben_solfin handle and a Solfin Consulting registry record are not enough to infer a legal-entity relationship.
Selected exact route risks
- risk[0] Identity collision creates a material risk of paying or sharing information with an unrelated same-name operator.
- risk[1] No current legal terms, refund policy, payment recipient, or official checkout was verified.
Selected exact missing proof
- missingProof[0] A current domain cross-linked from the historical official channel.
- missingProof[1] A current contracting entity, jurisdiction, named responsible people, and legal terms.
- missingProof[2] Current exact products, prices, billing cycles, payment recipient, and refund terms.
Source-preserved safest action
Do not pay, provide identity documents, or connect exchange APIs until a current domain is cross-linked from the historical official route and publishes a contracting entity, checkout identity, refund terms, API scope, and a complete loss-inclusive signal record.
Attribution limit: The exact assigned route is dormant, historical, inactive, unavailable, or apparently reassigned. Similar current properties stay separate unless a primary cross-link proves continuity; the posture is not an accusation about any route owner. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Site and messaging route mutually attributable
Binance Killers route note
The website and @BinanceKillers channel form a mutually attributable publishing and access chain. That chain identifies where the offer is presented; it does not settle which legal entity invoices a user or validate every support account reached later.
Observed route anchors
- binancekillers.com website
- @BinanceKillers Telegram channel
- linked Telegram bot and support routes
Gates or collision markers
- production terms do not name the full contracting entity
- dev-domain operator wording cannot alone control the production route
Frozen platform context
Website, Telegram, NowPayments, Cornix, and Signalize AI
Conflict context retained from the dossier
- Production terms do not identify Swissbull Group – FZCO, while dev terms name it as operator.
- Plan cards advertise 3-5 premium signals per day while the FAQ says 1-3 per day.
- A July 10 post claims more than 300% total July profit while describing seven signals as still in play, so the headline is not closed realized PNL.
- The FAQ directs US and Canadian members toward Bybit while Bybit’s official restricted-country page lists both jurisdictions.
Selected exact route risks
- risk[2] An unresolved production contracting entity complicates invoicing, disputes, privacy accountability, and refund enforcement.
- risk[3] Exchange jurisdiction conflicts could cause onboarding rejection or account restriction.
Selected exact missing proof
- missingProof[0] One controlling production operator with registry extract and company number
- missingProof[1] Named principals and independently corroborated team roles
Source-preserved safest action
Verify the production legal entity, invoice issuer, payment network, access term, and jurisdiction eligibility before sending cryptocurrency; require a complete signal-ID export, and if testing Cornix use a separate trade-only API key with withdrawals disabled.
Attribution limit: A current provider website and a messaging route cross-support the same access chain strongly enough to attribute the route to the named provider in this snapshot. Mutual attribution is not legal-operator verification, safety certification, endorsement, account acceptance, or performance proof. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Messaging or bot route; counterparty chain unresolved
Bitcoin Bullets route note
The main @BitcoinBullets channel visibly points to a VIP bot, a contact alias, and exchange referral pages. The observed chain is provider-specific, but the bot, payment recipient, secondary channel, and legal counterparty cannot be collapsed into one verified operator.
Observed route anchors
- @BitcoinBullets Telegram channel
- @VIPBulletsBot Telegram bot
- @joe1322 Telegram contact
- BingX and MEXC referral destinations
Gates or collision markers
- VIP payment recipient and legal operator are not published
- secondary @BitcoinBullets_VipOfficial channel is not linked by the main route
- bot data handling and access contract remain unresolved
Frozen platform context
Telegram, VIP bot, exchange referrals, and Cornix
Conflict context retained from the dossier
- A secondary Bitcoin Bullets VIP Official channel claims a team headquartered in Kiev, Russia, an internally invalid location description.
- The main channel does not link the secondary channel, so identity continuity and the secondary jurisdiction claim cannot be inferred.
- The VIP sale uses limited-time prices without a visible expiry or controlling checkout terms.
- A signal sequence can be edited and averaged into while open, preventing reconstruction from headline target updates alone.
Selected exact route risks
- risk[0] An unresolved operator and payment method create counterparty, refund, and Telegram impersonation risk.
- risk[1] Exchange referral incentives may influence platform routing and do not establish exchange suitability.
- risk[2] Cornix automation requires exchange read and trade permissions, potentially including futures permissions.
Selected exact missing proof
- missingProof[0] Legal operator, registration, jurisdiction, and full named team
- missingProof[1] Controlling payment, renewal, refund, cancellation, and access-suspension terms
- missingProof[2] Evidence that the secondary channel belongs to the same current operator
Source-preserved safest action
Do not pay through a bot or connect an exchange API until the operator, invoice issuer, payment network, access and refund terms, and official route ownership are documented; then paper-trade a complete unedited period before considering any trade-only API test.
Attribution limit: Telegram is the primary observed access surface and the path continues through a contact, bot, referral, deposit, or identifier step whose legal counterparty and control chain remain unresolved. Availability of the path does not prove operator identity, safe handling, durable access, or results. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Assigned route dormant, historical, or reassigned
Bitcoin Trading Club route note
The exact assigned @BitcoinTradingClub route is dormant and materially different from lowercase @btctradingclub. Capitalization alone is not the issue; the live destinations, histories, names, and links differ, so the lowercase offer cannot repair the exact route’s missing continuity.
Observed route anchors
- exact @BitcoinTradingClub Telegram channel
- historical @BitcoinTradingClub feed
Gates or collision markers
- exact channel contains 2018 inactivity warnings
- lowercase @btctradingclub is active under a different name
- no primary cross-link connects the exact and lowercase handles
Frozen platform context
Telegram; exact assigned channel dormant; separate lowercase Telegram route and result channel have unresolved attribution
Conflict context retained from the dossier
- CoinSwitch listed @BitcoinTradingClub as a 35,000-plus free and paid channel on 2025-09-22, but the live exact channel has six subscribers and only historical inactivity warnings.
- A 2023 promotional forum post used the lowercase @btctradingclub route, not the exact @BitcoinTradingClub handle.
- The lowercase route now brands itself Free Crypto Signals (Profitable Zone), not Bitcoin Trading Club.
- iFundTraders separately sells an Oliver Velez program that includes a product called Bitcoin Trading Club; it is a distinct same-name offering with no evidenced connection.
- The exact channel’s last visible messages are 2018 owner-inactivity warnings, so current control and handle continuity are unknown.
Selected exact route risks
- risk[0] Dormant or reassigned handles create impersonation and misdirected-payment risk.
- risk[1] The separate lowercase route requests direct crypto or netbanking payment to a pseudonymous admin.
Selected exact missing proof
- missingProof[0] Current control of the exact @BitcoinTradingClub handle
- missingProof[1] Legal operator, jurisdiction, and accountable team
- missingProof[2] Primary cross-link between the exact and lowercase Telegram handles, if continuity is claimed
Source-preserved safest action
Treat the exact record as inactive and every same-name route as separate, and do not pay until a current legal operator proves handle control, terms, and a complete loss-inclusive history.
Attribution limit: The exact assigned route is dormant, historical, inactive, unavailable, or apparently reassigned. Similar current properties stay separate unless a primary cross-link proves continuity; the posture is not an accusation about any route owner. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Same-name, cross-link, or alias collision unresolved
Coin Signals route note
The current @coin_signals channel and @Last_Satoshi contact cross-link each other, while the old CoinSignals.io association no longer authenticates that route. A separate historical use of the Coin Signals name is explicitly not merged with this provider.
Observed route anchors
- @coin_signals Telegram channel
- @Last_Satoshi Telegram admin contact
Gates or collision markers
- old CoinSignals.io association is no longer present in the channel
- CoinSignals.io now serves unrelated content
- separate historical Coin Signals enforcement identity is not linked
Frozen platform context
Telegram
Conflict context retained from the dossier
- CoinSignals.io was associated with the channel in an older directory record but now serves unrelated KClub gambling content, and the current Telegram description no longer links it.
- The current channel claims a professional trading team but identifies only the pseudonymous @Last_Satoshi contact.
- Result posts are frequently forwarded from a private VIP channel and some public commentary is edited, so the public feed cannot establish completeness.
- A separate historical U.S. enforcement matter used the name Coin Signals for Jeremy Spence; no evidence links that person or scheme to @coin_signals, so the identities must remain separate.
Selected exact route risks
- risk[0] VIP access is sold through a pseudonymous direct-message route without public price, billing, payment-recipient, or refund terms.
- risk[2] Auto Trading is advertised without API permission, custody, exchange, credential-storage, or emergency-stop documentation.
- risk[4] The formerly associated domain is no longer a reliable route for identity or payment verification.
Selected exact missing proof
- missingProof[0] A stable current domain cross-linked from the Telegram channel and admin account.
- missingProof[1] A legal operator, jurisdiction, named analysts, terms, privacy policy, and refund policy.
- missingProof[5] Auto-trading API permission, custody, security, and emergency-stop documentation.
Source-preserved safest action
Do not pay by direct message or enable automation until the channel publishes a stable cross-linked domain, contracting identity, written commercial terms, complete loss-inclusive alert history, and exact return and API-risk methodology; paper-test the leveraged calls first.
Attribution limit: The record contains same-name properties, lookalike handles, unlinked sites, or alias uncertainty that prevents a single current control chain from being established. The audit does not merge those identities, accuse them of coordination, or infer ownership from name similarity. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Site and messaging route mutually attributable
CoinCodeCap Signals route note
CoinCodeCap’s site, @coincodecap channel, contact page, and InviteMember checkout support one current route chain. The route can be attributed without treating the unresolved legal entity, second analyst, Cornix setup, or exchange copy profile as verified by association.
Observed route anchors
- signals.coincodecap.com website
- @coincodecap Telegram channel
- InviteMember checkout route
- @gaurav_zen contact
Gates or collision markers
- website and Telegram routes cross-support the same service
- contracting entity and second analyst remain incomplete
- copy-trading profiles require separate exchange attribution
Frozen platform context
Website, Telegram, InviteMember checkout, optional Cornix automation, and exchange copy-trading routes
Conflict context retained from the dossier
- Current pricing and contact pages promise a seven-day full refund, while the legal terms state three days.
- The legal terms say subscriptions automatically renew, while the current pricing page says only Monthly recurs and Six Months, Annual, and Lifetime are one-time payments.
- Current pricing lists Lifetime at $729, while a live legacy product page dated 2021-06-11 lists Lifetime at $199.
- The Results page says every 2026 signal is available row by row, but the linked workbook’s default export contains only headings and a direction to monthly summary sheets.
- The service says two analysts generate signals, but only Gaurav Agarwal is named.
- The Results headline says Jan-Jun 2026 while its aggregate excludes February and represents five complete months.
Selected exact route risks
- risk[0] The unresolved contracting entity and conflicting refund language complicate payment and dispute handling.
- risk[2] Cornix automation requires exchange integration and can convert signals into live orders; permissions, sizing, and emergency stops need separate review.
- risk[3] Copy trading adds exchange custody, futures liquidation, profit-share, and affiliate-routing risk.
Selected exact missing proof
- missingProof[0] A registered contracting entity, address, and jurisdiction beyond the Indian governing-law clause.
- missingProof[5] The identity and track record of the second analyst.
- missingProof[6] Exchange-owned confirmation of the current copy-trading profiles and exact fee or profit-share terms.
Source-preserved safest action
Before payment, obtain written confirmation of the governing refund window, renewal term, contracting party, and correct checkout price. If testing, use the $99 monthly card route rather than crypto, Lifetime, or the legacy cart, and paper-test any Cornix or copy-trading setup while requesting a complete row-level 2026 export.
Attribution limit: A current provider website and a messaging route cross-support the same access chain strongly enough to attribute the route to the named provider in this snapshot. Mutual attribution is not legal-operator verification, safety certification, endorsement, account acceptance, or performance proof. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Free observation route current; accountable contact incomplete
CoinSig route note
CoinSig’s current website and @coinsig_io channel form an attributable free observation route. The absence of a reviewed payment or API gate narrows operational exposure in this snapshot but does not identify the accountable operator or validate report timing and accuracy.
Observed route anchors
- coinsig.io website
- @coinsig_io Telegram channel
Gates or collision markers
- website links the current free Telegram observation route
- no reviewed payment, subscription, custody, or exchange-key gate
- accountable contact remains a domain email rather than a named operator
Frozen platform context
Free website and Telegram alert channel for rules-engine signals, LLM-assisted daily reports, derivatives metrics, BTC options analysis, and a public prediction track record.
Conflict context retained from the dossier
- Structured page metadata referred to 82 predictions while the visible rules-based UI totaled 90 entries on 2026-07-10.
- Telegram messages timestamped 2026-07-10 included a report body dated 2026-02-17, leaving the publication, delay, or backfill sequence unexplained.
- The latest report displayed rolling 5 wins and 2 losses, 71%, alongside an average accuracy value of 64; these are different provider-defined windows and should not be read as one standardized performance measure.
- Historical uses of the CoinSig name or domain cannot be attributed to the current 2026 site without operator continuity evidence.
Selected exact route risks
- risk[0] No payment, subscription, custody, or exchange API-key exposure was found on the reviewed current pages, reducing but not eliminating operational risk.
- risk[1] Third-party market APIs can be stale, unavailable, revised, or internally inconsistent, while source-level timestamps and incident handling are not fully exposed.
- risk[4] Unexplained Telegram timestamp differences can undermine proof that an alert existed before the measured market move.
Selected exact missing proof
- missingProof[0] Legal operator, jurisdiction, named developer, and accountable contact beyond a domain email.
- missingProof[3] Per-source timestamps, latency, revision behavior, outage treatment, and incident history.
- missingProof[5] Explanation and correction policy for prediction-count and Telegram report-date conflicts.
Source-preserved safest action
Use CoinSig as a free observation source only, capture each signal before the measured move, verify underlying metrics at their primary data providers, and do not allocate capital from its labels until the scoring, versioning, source timing, and immutable prediction history are reproducible.
Attribution limit: A current website and Telegram observation route were found without a reviewed payment, custody, subscription, or exchange-key gate, while accountable operator or contact proof remains incomplete. Free access does not establish safety, accuracy, endorsement, or future route stability. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Assigned route dormant, historical, or reassigned
Crypto Bulls route note
The exact @CryptoBulls destination no longer supplies an attributable active service. cryptobulls.biz and @bulls_biz support each other, yet that pair cannot be assigned to @CryptoBulls without a bridging primary link; the separate current properties therefore stay outside the assigned route.
Observed route anchors
- exact @CryptoBulls Telegram handle
Gates or collision markers
- exact assigned handle is inactive or reassigned
- cryptobulls.biz and @bulls_biz mutually cross-link but do not link to @CryptoBulls
- other same-name channels remain unlinked
Frozen platform context
Exact Telegram route is inactive or reassigned; separate same-name website, Telegram promotion channel, and private back office have unresolved attribution
Conflict context retained from the dossier
- CoinSwitch listed @CryptoBulls as a 30,000-plus free and paid channel on 2025-09-22, but the live handle now resolves to an empty contact profile.
- cryptobulls.biz and @bulls_biz mutually cross-link, but neither is linked from the assigned @CryptoBulls route.
- The current @the_crypto_bulls channel publishes automated low-cap token alerts and is not evidenced as the assigned provider.
- The separate @crypto_bulls_officials channel publishes deposit and fixed-return language and cannot be merged with the assigned provider.
- The cryptobulls.biz app subdomain currently renders an unrelated bus-company site, while its login hostname did not resolve during the check.
- The website says it is based in the United Kingdom, but an exact Cryptobulls Companies House search returned no result.
- The FAQ refers readers to Terms, but the current site does not expose a working Terms page.
Selected exact route risks
- risk[0] Handle reassignment and multiple same-name properties create a high risk of paying the wrong operator.
- risk[2] The app and login routes are unavailable or misrouted, weakening access and account-recovery evidence.
Selected exact missing proof
- missingProof[0] A current primary cross-link connecting @CryptoBulls to any active property
- missingProof[1] Legal entity, jurisdiction, company number, and accountable team
- missingProof[2] Working application, login, support, and account-recovery routes
Source-preserved safest action
Treat @CryptoBulls and every same-name property as separate until a stable primary route proves continuity, and do not pay, create an account, or provide exchange credentials before legal, access, and result evidence is supplied.
Attribution limit: The exact assigned route is dormant, historical, inactive, unavailable, or apparently reassigned. Similar current properties stay separate unless a primary cross-link proves continuity; the posture is not an accusation about any route owner. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Same-name, cross-link, or alias collision unresolved
Crypto Classics route note
The current @CryptoClassics profile cross-links @CCVIPCHAT, which supports a limited current contact route. Historical @CryptoClasssssics and @ui_ferna evidence is preserved as a lookalike chain, not merged, and the parked domain cannot bridge the identities.
Observed route anchors
- @CryptoClassics Telegram channel
- @CCVIPCHAT Telegram admin contact
Gates or collision markers
- historical @CryptoClasssssics is a different handle
- historical @ui_ferna route is not current-route proof
- crypto-classics.com is parked and re-registered
- current WhatsApp route is unconfirmed
Frozen platform context
Telegram; premium access by direct admin contact; Cornix support claimed in the last visible price table
Conflict context retained from the dossier
- The current @CryptoClassics history contains materially different admin handles and price offers, including @CryptoBeastAdmin, @NadiaHafsa, @CCANALYST, @CCVIPSIGNALS, and @CCVIPCHAT; operator continuity is not proven.
- The historical lookalike @CryptoClasssssics used @ui_ferna and linked crypto-classics.com, but it is a different handle and cannot be merged with the current channel.
- The current crypto-classics.com page is parked, and its current registration began on 2025-08-09, so it does not authenticate the historical 2021 route.
- The local Crypto Classics WhatsApp alias has no current primary-source confirmation.
- The last visible price table is dated 2025-10-09 and has not been reconfirmed through a public current checkout.
Selected exact route risks
- risk[0] Direct-message premium access creates impersonation and payment-route substitution risk.
- risk[4] A parked and re-registered domain cannot currently serve as stable identity proof.
Selected exact missing proof
- missingProof[0] Current legal operator and jurisdiction
- missingProof[1] Admin identity and continuity evidence
- missingProof[6] Current official WhatsApp route, if one exists
Source-preserved safest action
Start only from the current public Telegram profile, do not pay or connect Cornix until the operator and terms are documented, and independently paper-track future timestamped calls before considering paid access.
Attribution limit: The record contains same-name properties, lookalike handles, unlinked sites, or alias uncertainty that prevents a single current control chain from being established. The audit does not merge those identities, accuse them of coordination, or infer ownership from name similarity. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Same-name, cross-link, or alias collision unresolved
Crypto Inner Circle route note
The active observed route is @cryptoinnercircle, not the stale @CryptoInnerCircleOfficial listing. Neither the .io nor .vip same-name website is cross-linked by the channel, so their teams, prices, bots, wallets, and company histories cannot be attributed to the Telegram operator.
Observed route anchors
- @cryptoinnercircle Telegram channel
- CIC Alex Telegram admin contact
- BingX invite on the channel
Gates or collision markers
- historical @CryptoInnerCircleOfficial now presents an unrelated identity
- cryptoinnercircle.io is not linked from the channel
- cryptoinnercircle.vip is not linked from the channel
- the .io and .vip sites disagree on contacts and history
Frozen platform context
Telegram; direct USDT TRC20 VIP payment; BingX invite; provider-published Cornix result posts
Conflict context retained from the dossier
- The repo’s historical @CryptoInnerCircleOfficial route now displays an unrelated name and small audience, while the active observed route is @cryptoinnercircle.
- The current Telegram profile does not link cryptoinnercircle.io or cryptoinnercircle.vip, so neither site is attributed to the channel.
- The .io and .vip sites publish different Telegram contacts, team names, prices, product wording, and company histories.
- cryptoinnercircle.io claims establishment in 2014, but its current domain registration began on 2025-09-24.
- Telegram offers show 99 USDT monthly and 399 USDT lifetime, while unlinked sites show $70, $100, and $500 plans.
- The Telegram offer says signal frequency is not fixed and tells readers not to ask how many trades occur, while Kraken describes approximately 1-2 verified signals per day.
- Public direct-payment addresses changed across historical offer posts, and wallet continuity is not independently verified.
Selected exact route risks
- risk[0] Direct USDT TRC20 payment followed by a screenshot to a pseudonymous admin is irreversible and lacks card-style dispute protection.
- risk[1] Multiple stale, lookalike, and unlinked routes create impersonation and clone-channel risk.
- risk[2] The BingX invite introduces a possible commercial incentive that is not fully disclosed on the channel profile.
Selected exact missing proof
- missingProof[0] Legal entity, jurisdiction, company number, and accountable operator
- missingProof[2] Proof that either same-name website belongs to the Telegram channel
- missingProof[7] BingX referral or affiliate disclosure
Source-preserved safest action
Use only the current public @cryptoinnercircle route for observation, do not send USDT or connect an exchange until legal, wallet, terms, referral, and API evidence is supplied, and independently paper-test timestamped calls.
Attribution limit: The record contains same-name properties, lookalike handles, unlinked sites, or alias uncertainty that prevents a single current control chain from being established. The audit does not merge those identities, accuse them of coordination, or infer ownership from name similarity. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Same-name, cross-link, or alias collision unresolved
CryptoSignaly route note
CryptoSignaly’s unavailable domain cannot currently arbitrate between @CryptoSignaly_Official, @CryptoSignalyOfficial, and @Kelvior. Similar spelling and indexed footer copy provide leads, not a verified present control chain or permission to attribute the same-address company.
Observed route anchors
- @CryptoSignaly_Official Telegram channel
- @Kelvior Telegram admin contact
- @CryptoSignalyOfficial Telegram contact shown in indexed website copy
Gates or collision markers
- cryptosignaly.com domain was unavailable and clientHold
- similar handles are not cross-confirmed by a functioning website
- same-address company record lacks a provider link
Frozen platform context
Public and VIP Telegram crypto signals, leveraged trade instructions, Cornix-linked automation references, and a pseudonymous managed-investment solicitation.
Conflict context retained from the dossier
- The legal operator is unresolved; a Companies House company at the displayed Glasgow address cannot be attributed to CryptoSignaly without a connecting primary source.
- The domain was clientHold and unavailable on 2026-07-10 despite indexed pages presenting an operating service.
- The website footer, public Telegram channel, and sales posts use @CryptoSignalyOfficial, @CryptoSignaly_Official, and @Kelvior without a currently functioning domain that cross-confirms control.
- Provider claims conflict between 75%+ and 95% accuracy and between 4-7, 11-15, and 7-20+ signals per day.
- Managed-plan posts quote both 20% and 28% of profits.
- Subscription copy says no refunds after digital delivery, while managed-plan copy promises a full refund if a loss occurs without enforceable terms.
- Indexed site copy claims more than 11 years of experience, while the current domain record begins on 2026-02-12 and no continuity evidence was found.
Selected exact route risks
- risk[0] The managed-money offer asks users to deal with a pseudonymous Telegram admin without a disclosed custodian, legal merchant, withdrawal process, or jurisdiction.
- risk[1] An unavailable domain and non-working website email route reduce the ability to verify official accounts, terms, support, and payment destination.
- risk[5] Multiple similar Telegram handles create impersonation and payment-redirection risk.
Selected exact missing proof
- missingProof[0] Restored provider-controlled domain with working cross-links to every official Telegram, email, and payment route.
- missingProof[1] Legal entity, registration number, physical jurisdiction, governing law, responsible officers, and merchant identity.
- missingProof[2] Legal identity and role evidence for @Kelvior and any analysts or fund managers.
Source-preserved safest action
Do not send subscription payments, managed funds, wallet assets, or exchange API keys while the domain, legal merchant, custody terms, and account-control chain remain unresolved; require those items and a timestamped loss-inclusive record before considering any further step.
Attribution limit: The record contains same-name properties, lookalike handles, unlinked sites, or alias uncertainty that prevents a single current control chain from being established. The audit does not merge those identities, accuse them of coordination, or infer ownership from name similarity. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Site or app primary route current
Dash 2 Trade route note
Dash 2 Trade presents a website-led analytics and auto-trading application. Its provider route is current, but a working app route does not authenticate every historical team statement or establish the safety of a later exchange connection.
Observed route anchors
- dash2trade.com website
- Dash 2 Trade web application
- provider-published exchange API guide
Gates or collision markers
- application account precedes any connected exchange route
- current registry standing and responsible officers remain unconfirmed
Frozen platform context
Web analytics and auto-trading application with market-event signals, strategy backtests, DCA and grid bots, trade bundles, webhooks, and exchange API connections.
Conflict context retained from the dossier
- The product signals page frames signals as market events rather than trade setups, while the terms define signals as third-party buy or sell recommendations and marketing promotes copying bots.
- The subscription page offers monthly Professional access but does not show the exact public monthly price.
- Current product pages do not name the team, while a 2022 provider-linked article names two people whose present roles are unconfirmed.
- The terms assert a Marshall Islands registration, but the official entity search was unavailable for current registry verification on the research date.
- Backtest and historically profitable language appears alongside broad disclaimers that results are hypothetical and not guarantees of future performance.
Selected exact route risks
- risk[0] Trading-enabled exchange API keys remain stored until the user removes the connection; compromise, configuration error, platform failure, exchange outage, or bot defects can generate unwanted orders even when withdrawals are disabled.
- risk[4] Current registry standing, responsible officers, API-key encryption and custody controls, and incident response procedures are not visible.
Selected exact missing proof
- missingProof[0] Current Marshall Islands registry extract and good-standing evidence for Dash 2 Trade Ltd.
- missingProof[1] Current directors, responsible officers, beneficial controller, and named product or security leadership.
- missingProof[3] API-key encryption, storage location, employee access controls, breach response, deletion verification, and security audit evidence.
Source-preserved safest action
Begin with the free tier and paper observation; if testing exchange execution, use a new low-balance subaccount with withdrawals disabled, IP whitelisting, and only the minimum trading permissions after confirming the exact checkout price, renewal, no-refund rule, and key-deletion process.
Attribution limit: The frozen packet contains a current provider-controlled website or application route that is primary for access. That route attribution does not verify every operator, connected account, support contact, safety control, user acceptance decision, or performance claim. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Site and messaging route mutually attributable
Learn2Trade route note
The website and provider-published Telegram channel are mutually attributable for Learn2Trade’s current offer. The current UK broker promotion is an additional access branch and does not turn a Telegram cross-link into broker suitability, operator registration, or performance proof.
Observed route anchors
- learn2.trade website
- @learn2tradectypto Telegram channel
- provider-linked Focus Markets offer
Gates or collision markers
- site and Telegram pricing differ
- broker-affiliate access is a later counterparty step
- operator registration remains unresolved
Frozen platform context
Website, Telegram, broker-affiliate access routes, and L2T Algo
Conflict context retained from the dossier
- The crypto pricing page starts at GBP 39 monthly while a current official Telegram post says from GBP 35 monthly.
- General signal terms exclude discount-code purchases, education, and later purchases from the 30-day refund, while the algo page promises every tier a full no-questions refund within 30 days.
- Site disclosures say crypto promotions are not intended for UK consumers, while a current Telegram post advertises a UK-exclusive Focus Markets route.
- Published accuracy figures vary between 76%, 79%, and 82% without a common downloadable calculation set.
Selected exact route risks
- risk[0] Broker-funded access creates an affiliate incentive and requires capital to be placed with a third party.
- risk[2] Telegram impersonation is material because access and support are routed through messaging accounts.
Selected exact missing proof
- missingProof[0] Current official company registry extract and registration number
- missingProof[1] One controlling price and billing schedule for each product
- missingProof[2] One controlling refund policy reconciled with product-page promises
Source-preserved safest action
Confirm the final cart, renewal, refund eligibility, operator identity, and broker-affiliate conditions in writing, then paper-trade a complete loss-inclusive period before paying, depositing with a broker, or granting any automation access.
Attribution limit: A current provider website and a messaging route cross-support the same access chain strongly enough to attribute the route to the named provider in this snapshot. Mutual attribution is not legal-operator verification, safety certification, endorsement, account acceptance, or performance proof. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Same-name, cross-link, or alias collision unresolved
Raven Trading Pro route note
Current first-party pages use Raven Signals Pro, while Raven Trading Pro appears in third-party coverage. The audit preserves Raven Trading Pro versus Raven Signals Pro as unresolved alias evidence and leaves the separate raven-trading.com business outside the route.
Observed route anchors
- ravensignalspro.com website
- @ravensignalspro Telegram channel
- @ravensignalspro_stats Telegram channel
Gates or collision markers
- assigned Raven Trading Pro label is not confirmed as an owned alias
- current first-party branding is Raven Signals Pro
- separate raven-trading.com business is unlinked
Frozen platform context
Website-led crypto and forex signal subscriptions delivered through private Telegram channels, with optional Cornix-compatible automation and an Apex research offer.
Conflict context retained from the dossier
- Current first-party routes use Raven Signals Pro, while the assigned Raven Trading Pro label appears in third-party coverage and was not confirmed as an owned alias.
- The services page lists combined Crypto and Forex at $129 monthly, while July 2026 Telegram promotion says Raven VIP includes both at $99 monthly.
- The FAQ labels $399 as Lifetime, while the services page labels $399 as the yearly combined plan and separately lists Apex lifetime at $2,397.
- The homepage describes 8-14 signals monthly, while the services page describes 2-4 signals daily.
- Homepage language includes near-guaranteed conviction, while the terms disclaim guarantees and state that trading can lose all invested capital.
- A separate raven-trading.com business presents institutional trading services; no evidence found links that business or Raven Trading Limited to Raven Signals Pro.
Selected exact route risks
- risk[0] The billing merchant and legal counterparty are not identified, limiting recourse for access, renewal, or refund disputes.
- risk[2] Conflicting aliases, prices, and Telegram support routes increase impersonation and wrong-destination payment risk.
Selected exact missing proof
- missingProof[0] Legal merchant name, registration number, address, jurisdiction, and governing law.
- missingProof[1] Primary-source confirmation that Raven Trading Pro and Raven Signals Pro are the same controlled service.
Source-preserved safest action
Confirm the legal merchant, alias ownership, payable price, renewal, and refund terms in writing; observe signals manually without capital before considering access, and do not provide exchange API credentials or make an irreversible crypto payment until those points and the result methodology are documented.
Attribution limit: The record contains same-name properties, lookalike handles, unlinked sites, or alias uncertainty that prevents a single current control chain from being established. The audit does not merge those identities, accuse them of coordination, or infer ownership from name similarity. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.
Messaging or bot route; counterparty chain unresolved
Wolf of Trading route note
Wolf’s public Telegram funnel continues through a WEEX referral, deposit requirement, UID handoff, and @WEEXElite_WOLFOFTRADING_bot. Those steps prove an observed route, not who controls every endpoint or whether the route will accept, protect, or continue serving a particular account.
Observed route anchors
- @wolfoftrading Telegram channel
- @wolfoftradingteam Telegram contact
- @WEEXElite_WOLFOFTRADING_bot Telegram bot
- WEEX registration route
Gates or collision markers
- USD 100 exchange deposit precedes access
- WEEX UID is sent through a Telegram bot
- legal operator, bot controller, and data-retention chain remain unresolved
Frozen platform context
Telegram and WEEX-linked access bot
Conflict context retained from the dossier
- The July 9 funnel says no KYC and works in the US, while WEEX terms exclude US users and reserve identity-verification rights.
- WEEX affiliate terms prohibit targeting restricted jurisdictions or circumventing KYC, which conflicts with the funnel wording.
- VIP is described as free even though access requires a minimum USD 100 exchange deposit through a referral route.
Selected exact route risks
- risk[0] Deposit-gated referral access creates a commercial incentive and exchange-custody exposure.
- risk[1] Sending a WEEX UID to a Telegram bot links exchange identity data to an unresolved operator.
- risk[2] Jurisdiction and KYC conflicts could lead to rejected onboarding, account restriction, or inaccessible funds.
Selected exact missing proof
- missingProof[0] Legal operator, registration, jurisdiction, and named principals
- missingProof[1] Contractual access duration, suspension, cancellation, and refund terms
- missingProof[2] Proof that the advertised route complies with WEEX jurisdiction and KYC rules
Source-preserved safest action
Do not deposit or send an exchange UID from the Telegram funnel until WEEX independently confirms eligibility and the provider supplies its operator identity, access contract, refund terms, and complete loss-inclusive record; paper-trade first.
Attribution limit: Telegram is the primary observed access surface and the path continues through a contact, bot, referral, deposit, or identifier step whose legal counterparty and control chain remain unresolved. Availability of the path does not prove operator identity, safe handling, durable access, or results. The route note records what can be assigned to this provider record as of 2026-07-10; it does not merge unproven identities or convert a reachable channel into a verified operator, safe destination, endorsed service, accepted account, or proven result.