Identity & Background
Known attributes linked to the subject profile.
| Field | Value |
|---|---|
| Verified Name | N/A |
| Handles |
|
| Email Addresses | N/A |
| Locations | N/A |
| Verification Status | medium |
| Source Ids | SRC-001 · SRC-002 · SRC-003 · SRC-004 · SRC-005 |
Median of materially divergent LLM scores. Positive signals include long-term operational utility and no direct evidence of fraud. Risk is elevated by unresolved identity, unverified investor claims, and explicit normalization of behavior associated with significant retail financial harm.
Known attributes linked to the subject profile.
| Field | Value |
|---|---|
| Verified Name | N/A |
| Handles |
|
| Email Addresses | N/A |
| Locations | N/A |
| Verification Status | medium |
| Source Ids | SRC-001 · SRC-002 · SRC-003 · SRC-004 · SRC-005 |
Model-level score reasoning and risk dimensions.
Complete claims table with expandable corroboration notes.
| Claim | Source | Confidence | Status |
|---|---|---|---|
| Developer and operator of CryptoWhaleBot / WhaleBot ecosystem. | Telegram bot and channel listings | high | verified |
| Angel investor in crypto projects. | Self-description and CryptoRank profile | low |
unverified
Expanded evidence Verification evidence: No primary disclosures, deal announcements, or portfolio company confirmations located. Notes: Claim repeated by aggregators; treated as self-reported. Flagged by: Claude, GPT Source IDs: SRC-008 |
| Entered crypto in 2016 and remained active through multiple market cycles. | Podcast self-report | medium |
unverified
Expanded evidence Verification evidence: Corroborated indirectly by bot history and long-standing X account, but remains self-reported. Notes: No independent timestamped proof beyond circumstantial alignment. Flagged by: GPT Source IDs: SRC-011 |
Chronology with full event text and annotations.
Third-party analytics indicate the @Icebergy account joined Twitter/X in January 2011.
Notes: Direct X verification not possible in this environment.
Sources: TwitterScore · Sorsa
Medium post documents Discord and bot updates and provides contact handles.
Sources: Medium
Source IDs: SRC-007
Icebergy publicly validated the semantic defense that the BALD deployer did not 'sell' but merely removed two-sided liquidity after a ~$20M liquidity pull caused a ~90% crash.
Notes: Sparked backlash and comparisons to gaslighting rhetoric used in prior major crypto scandals.
Sources: Unchained
Source IDs: SRC-010
Telegram listings show ongoing operation with substantial user metrics.
Sources: Telegram
High-impact concerns surfaced by at least one model.
No legal name, jurisdiction, education, or corporate registration information is available across all reviewed sources.
Sources: X · Telegram · Aggregators
Publicly endorsed a semantic defense minimizing a high-profile rug pull that caused severe retail losses.
Sources: Unchained
Source IDs: SRC-010
Angel investor status is self-reported and repeated by aggregators without primary corroboration.
Sources: CryptoRank
Source IDs: SRC-008
Recurring motifs across time, claims, and operations.
Maintained a functional crypto utility product across multiple market cycles.
Frequency: Continuous
Portfolio-level outcomes and operational trajectory.
2018-05 to ongoing
Telegram-based crypto market tracking and alert bot, later expanded to multiple platforms.
Outcome: Ongoing, widely used utility product.
Sources: Telegram · Medium · whalebot.io
Where narratives conflict and what is unresolved.
Overall risk score approximately 46, indicating moderate risk.
Source: Claude/Grok synthesis
Overall risk score approximately 28, indicating low-to-moderate risk.
Source: GPT synthesis
Resolution: Median score used per instructions. · Confidence: high
Synthesis highlights from all available model outputs.
Unlike many pseudonymous accounts, Icebergy is linked to a long-running, widely used crypto bot.
Importance: high
Public minimization of a major rug pull represents the most severe negative finding.
Importance: critical
What remains unknown and what needs corroboration.
Why uncertain: No disclosures across any reviewed sources.
What was searched: Social platforms, aggregators, podcasts.
Why uncertain: No wallets publicly linked.
What was searched: Project sites, profiles, media.
Data-quality and uncertainty indicators from the distillation step.
Collected references/links from all source-like fields in the distilled payload.
Raw distilled payload is attached to avoid information loss or truncation.
[
{
"platform": "ethos.network",
"score": 1689,
"score_type": "credibility",
"reviews_positive": null,
"reviews_negative": null,
"reviews_neutral": null,
"notable_review_texts": [],
"vouch_count": null,
"vouch_eth_staked": null,
"slash_count": null,
"url": "https://app.ethos.network/profile/x/Icebergy",
"source_id": "SRC-009"
}
]
{
"subject_name": "Icebergy",
"type": "person",
"overall_score": 37,
"research_sources": "Claude, GPT, Grok, Gemini",
"research_date": "2026-02-23",
"source_registry": [
{
"source_id": "SRC-001",
"url": "https://x.com/Icebergy",
"title": "icebergy ❄️ (@Icebergy) / Posts / X",
"publisher": "X",
"accessed_date": "2026-02-23"
},
{
"source_id": "SRC-002",
"url": "https://app.sorsa.io/profile/Icebergy",
"title": "Sorsa profile: @Icebergy",
"publisher": "Sorsa",
"accessed_date": "2026-02-23"
},
{
"source_id": "SRC-003",
"url": "https://twitterscore.io/twitter/Icebergy/",
"title": "TwitterScore profile: icebergy ❄️ (@Icebergy)",
"publisher": "TwitterScore.io",
"accessed_date": "2026-02-23"
},
{
"source_id": "SRC-004",
"url": "https://t.me/cryptowhalebot",
"title": "@cryptowhalebot Telegram bot",
"publisher": "Telegram",
"accessed_date": "2026-02-23"
},
{
"source_id": "SRC-005",
"url": "https://t.me/WhaleBotAlerts",
"title": "WhaleBot Alerts Telegram channel",
"publisher": "Telegram",
"accessed_date": "2026-02-23"
},
{
"source_id": "SRC-006",
"url": "https://whalebot.io/",
"title": "Crypto Whale Bot",
"publisher": "whalebot.io",
"accessed_date": "2026-02-23"
},
{
"source_id": "SRC-007",
"url": "https://medium.com/@Whalereports/crypto-whale-bot-discord-update-6d6e665b5e36",
"title": "Crypto Whale Bot — Discord Update",
"publisher": "Medium",
"accessed_date": "2026-02-23"
},
{
"source_id": "SRC-008",
"url": "https://cryptorank.io/funds/icebergy",
"title": "icebergy - Investment Fund Review",
"publisher": "CryptoRank.io",
"accessed_date": "2026-02-23"
},
{
"source_id": "SRC-009",
"url": "https://app.ethos.network/profile/x/Icebergy",
"title": "icebergy ❄️ | Ethos credibility profile – 1689 (Established)",
"publisher": "Ethos Network",
"accessed_date": "2026-02-23"
},
{
"source_id": "SRC-010",
"url": "https://unchainedcrypto.com/bald-token-falls-90-amid-rug-pull-allegations/",
"title": "BALD Token Falls 90% Amid Rug Pull Allegations",
"publisher": "Unchained",
"accessed_date": "2026-02-23"
},
{
"source_id": "SRC-011",
"url": "https://blockworks.co/podcast/empire/d08f9f0a-0f7e-11ee-885e-f32815103dfb",
"title": "Empire Podcast: How to Discover Crypto's Next Narrative Using Onchain Activity | Icebergy",
"publisher": "Blockworks",
"accessed_date": "2026-02-23"
}
],
"third_party_reputation_scores": [
{
"platform": "ethos.network",
"score": 1689,
"score_type": "credibility",
"reviews_positive": null,
"reviews_negative": null,
"reviews_neutral": null,
"notable_review_texts": [],
"vouch_count": null,
"vouch_eth_staked": null,
"slash_count": null,
"url": "https://app.ethos.network/profile/x/Icebergy",
"source_id": "SRC-009"
}
],
"identity": {
"verified_name": "",
"handles": [
"@Icebergy (X)",
"@icebergy (Telegram)",
"@cryptowhalebot (Telegram bot)",
"@WhaleBotAlerts (Telegram channel)"
],
"email_addresses": [],
"locations": [],
"verification_status": "medium",
"source_ids": [
"SRC-001",
"SRC-002",
"SRC-003",
"SRC-004",
"SRC-005"
]
},
"credentials_and_claims": [
{
"claim": "Developer and operator of CryptoWhaleBot / WhaleBot ecosystem.",
"source": "Telegram bot and channel listings",
"verified": true,
"verification_evidence": "Telegram pages explicitly list 'Dev @icebergy'.",
"verification_status": "verified",
"confidence": "high",
"found_by": [
"Claude",
"GPT",
"Grok",
"Gemini"
],
"notes": "Sustained multi-year operation with large user base.",
"source_ids": [
"SRC-004",
"SRC-005"
]
},
{
"claim": "Angel investor in crypto projects.",
"source": "Self-description and CryptoRank profile",
"verified": false,
"verification_evidence": "No primary disclosures, deal announcements, or portfolio company confirmations located.",
"verification_status": "unverified",
"confidence": "low",
"found_by": [
"Claude",
"GPT"
],
"notes": "Claim repeated by aggregators; treated as self-reported.",
"source_ids": [
"SRC-008"
]
},
{
"claim": "Entered crypto in 2016 and remained active through multiple market cycles.",
"source": "Podcast self-report",
"verified": false,
"verification_evidence": "Corroborated indirectly by bot history and long-standing X account, but remains self-reported.",
"verification_status": "unverified",
"confidence": "medium",
"found_by": [
"GPT"
],
"notes": "No independent timestamped proof beyond circumstantial alignment.",
"source_ids": [
"SRC-011"
]
}
],
"project_history": [
{
"name": "CryptoWhaleBot / WhaleBot",
"period": "2018-05 to ongoing",
"description": "Telegram-based crypto market tracking and alert bot, later expanded to multiple platforms.",
"funding": "Unknown",
"outcome": "Ongoing, widely used utility product.",
"tvl_or_metrics": "20,882 monthly bot users; 159,630 Telegram channel subscribers at time of access.",
"team_members": [
"Icebergy (pseudonymous)"
],
"controversies": [],
"sources": [
"Telegram",
"Medium",
"whalebot.io"
],
"confidence": "high",
"source_ids": [
"SRC-004",
"SRC-005",
"SRC-006",
"SRC-007"
]
}
],
"timeline": [
{
"date": "2011-01",
"title": "X account creation",
"description": "Third-party analytics indicate the @Icebergy account joined Twitter/X in January 2011.",
"sources": [
"TwitterScore",
"Sorsa"
],
"tone": "neutral",
"verified": false,
"notes": "Direct X verification not possible in this environment.",
"source_ids": [
"SRC-002",
"SRC-003"
]
},
{
"date": "2018-05",
"title": "CryptoWhaleBot public update",
"description": "Medium post documents Discord and bot updates and provides contact handles.",
"sources": [
"Medium"
],
"tone": "neutral",
"verified": true,
"notes": "",
"source_ids": [
"SRC-007"
]
},
{
"date": "2023-07",
"title": "BALD token rug pull discourse",
"description": "Icebergy publicly validated the semantic defense that the BALD deployer did not 'sell' but merely removed two-sided liquidity after a ~$20M liquidity pull caused a ~90% crash.",
"sources": [
"Unchained"
],
"tone": "critical",
"verified": true,
"notes": "Sparked backlash and comparisons to gaslighting rhetoric used in prior major crypto scandals.",
"source_ids": [
"SRC-010"
]
},
{
"date": "2026-02",
"title": "Active operation confirmed",
"description": "Telegram listings show ongoing operation with substantial user metrics.",
"sources": [
"Telegram"
],
"tone": "positive",
"verified": true,
"notes": "",
"source_ids": [
"SRC-004",
"SRC-005"
]
}
],
"red_flags": [
{
"title": "Complete pseudonymity with no verifiable legal identity",
"description": "No legal name, jurisdiction, education, or corporate registration information is available across all reviewed sources.",
"severity": "medium",
"confidence": "high",
"supporting_evidence": [
"Absence of legal identifiers on all platforms.",
"Reliance on handles and aggregators only."
],
"counter_evidence": [],
"found_by": [
"Claude",
"GPT",
"Grok",
"Gemini"
],
"sources": [
"X",
"Telegram",
"Aggregators"
],
"source_ids": [
"SRC-001",
"SRC-002",
"SRC-004",
"SRC-005"
]
},
{
"title": "Normalization of malicious on-chain behavior (BALD incident)",
"description": "Publicly endorsed a semantic defense minimizing a high-profile rug pull that caused severe retail losses.",
"severity": "high",
"confidence": "high",
"supporting_evidence": [
"Quoted and affirmed deployer defense post-rug pull.",
"Documented journalist criticism."
],
"counter_evidence": [
"No evidence Icebergy participated financially or operationally in the rug pull."
],
"found_by": [
"Grok",
"Gemini"
],
"sources": [
"Unchained"
],
"source_ids": [
"SRC-010"
]
},
{
"title": "Unsubstantiated angel investor claims",
"description": "Angel investor status is self-reported and repeated by aggregators without primary corroboration.",
"severity": "low",
"confidence": "medium",
"supporting_evidence": [
"Lack of deal announcements or confirmations."
],
"counter_evidence": [
"Presence in investor directories and podcast appearances."
],
"found_by": [
"Claude",
"GPT"
],
"sources": [
"CryptoRank"
],
"source_ids": [
"SRC-008"
]
}
],
"behavioral_patterns": [
{
"title": "Long-term operational continuity",
"description": "Maintained a functional crypto utility product across multiple market cycles.",
"examples": [
"2018 Medium update.",
"2026 active Telegram metrics."
],
"frequency": "Continuous",
"confidence": "high",
"sources": [
"Medium",
"Telegram"
],
"source_ids": [
"SRC-007",
"SRC-004",
"SRC-005"
]
}
],
"contradictions_and_disputes": [
{
"claim_1": "Overall risk score approximately 46, indicating moderate risk.",
"claim_2": "Overall risk score approximately 28, indicating low-to-moderate risk.",
"source_1": "Claude/Grok synthesis",
"source_2": "GPT synthesis",
"resolution": "Median score used per instructions.",
"confidence": "high",
"source_ids": []
}
],
"evidence_gaps": [
{
"question": "What is the subject’s legal identity and jurisdiction?",
"why_uncertain": "No disclosures across any reviewed sources.",
"searched": "Social platforms, aggregators, podcasts.",
"source_ids": []
},
{
"question": "Are there attributable on-chain wallets controlled by Icebergy?",
"why_uncertain": "No wallets publicly linked.",
"searched": "Project sites, profiles, media.",
"source_ids": []
}
],
"key_insights": [
{
"title": "Sustained delivery of a real utility product",
"description": "Unlike many pseudonymous accounts, Icebergy is linked to a long-running, widely used crypto bot.",
"importance": "high",
"evidence": [
"Telegram usage metrics.",
"Multi-year documentation."
],
"source_ids": [
"SRC-004",
"SRC-005",
"SRC-007"
]
},
{
"title": "Ethical risk signal from BALD commentary",
"description": "Public minimization of a major rug pull represents the most severe negative finding.",
"importance": "critical",
"evidence": [
"Journalistic coverage and backlash."
],
"source_ids": [
"SRC-010"
]
}
],
"risk_assessment": {
"overall_score": 37,
"score_reasoning": "Median of materially divergent LLM scores. Positive signals include long-term operational utility and no direct evidence of fraud. Risk is elevated by unresolved identity, unverified investor claims, and explicit normalization of behavior associated with significant retail financial harm.",
"criminal_risk": "none found",
"financial_risk": "medium",
"reputational_risk": "medium",
"verification_risk": "moderate; identity and investment claims weakly verifiable",
"source_ids": [
"SRC-004",
"SRC-005",
"SRC-009",
"SRC-010"
]
},
"confidence_notes": {
"data_completeness": "High for public activity and projects; low for real-world identity and finances.",
"source_verification": "Mixed; strong for platform-native data, weaker for aggregator-reported claims.",
"identity_confidence": "Medium",
"timeline_confidence": "Medium-High",
"conflicting_findings": "Primary disagreement centered on overall risk severity.",
"limitations": "No access to private records, corporate filings, or cryptographic identity attestations."
}
}