CoinRadar

Company: CoinRadar

Self-reported basis: The description is entirely self-reported and unverified, based on a Devpost submission for the OpenAI 2026 hackathon. No independent evidence of revenue, customers, or traction exists.

What it appears to be: A crypto monitoring tool that uses bots to detect patterns and connections in token deployments and trading behavior, aiming to surface insights that humans might miss. It is positioned as a "signalcraft" tool that goes beyond standard safety checks.

What changed: The project evolved from a simple bot merge into a broader philosophy of detecting invisible signals in crypto markets — moving from "check this token" to "here's a connection you didn't know existed."

Most important open question: Is there a real market need for such a tool, and does the author have the technical and commercial capability to build it at scale?

The description states that CoinRadar is a bot-based system designed to monitor crypto tokens and detect patterns or connections that are not immediately obvious. It builds on the idea of "signalcraft" — identifying insights from noise, rather than just performing standard checks like liquidity or mint authority.

It was built using json, node.js, and postgresql, and is intended for deployment on Telegram, where it delivers intelligence directly to users.

Inference: The tool appears to be a prototype or early-stage product, likely built as part of a hackathon. It is not described as having any production-ready features or commercial use cases beyond the author’s own experimentation.

The description states that CoinRadar was born from frustration with existing crypto tools — which tell users what a token is doing but not why it matters. The tool aims to go deeper, asking questions like:

• Has this deployer burned people before?
• Is this whale backing other tokens too?

This reflects a shift in positioning: from standard safety checks to pattern detection and insight generation.

The name “CoinRadar” is said to reflect the philosophy of “crafting signal out of noise,” suggesting an emphasis on detecting hidden or overlooked signals rather than just reporting data.

Inference: The author sees CoinRadar as part of a broader "Signalcraft" approach — not just automating tasks, but surfacing previously invisible connections. However, no evidence is provided that this approach has been validated in practice or adopted by users.

The description states that the tool is built for crypto traders and analysts who are looking for deeper insights than what standard tools offer. It is positioned to deliver intelligence where users already spend time — Telegram, which has 900M+ users.

It targets those who manually investigate tokens, one tab at a time, and want to automate or enhance that process with pattern recognition.

Inference: The ICP (Ideal Customer Profile) appears to be experienced crypto traders or analysts who are already using Telegram for communication and want more advanced monitoring capabilities. However, no evidence of actual users or customer feedback is provided.

No business model or pricing information is provided in the description.

Inference: The project is described as a prototype or hackathon submission, with no indication of monetization strategy, pricing tiers, or revenue streams. It is unclear whether it will be offered as a freemium service, subscription, or one-time tool.

The project was built using:

• json
• node.js
• postgresql

It is intended for deployment on Telegram, suggesting integration with Telegram’s API and possibly bot architecture.

Inference: The technical stack suggests a lightweight, early-stage prototype. No evidence of scalability, performance metrics, or enterprise-grade infrastructure is provided. The delivery mechanism (Telegram) implies a focus on user accessibility rather than traditional SaaS platforms.

The description states that the project was submitted to the OpenAI 2026 hackathon, indicating it is likely in an early stage of development.

It was built by a single team member, Geoffry Yohanna.

There is no evidence of:

• Revenue
• Customers
• User adoption
• Product-market fit
• Any traction beyond the author’s own use case

Inference: The project is at a very early stage — likely a prototype or proof-of-concept. No signs of product maturity, user engagement, or commercial viability are evident.

The description states that existing crypto tools focus on what a token is doing but not why it matters. It also mentions that safety bots check basic boxes (liquidity, mint authority) but stop before deeper insights begin.

It does not name specific competitors, nor does it describe how CoinRadar differentiates from them in terms of features or execution.

Inference: The author sees a gap in the market for tools that go beyond standard checks. However, no competitive analysis or differentiation strategy is provided. It’s unclear whether similar tools already exist or if this is a novel idea.

• No evidence of traction or revenue: The project is described as a hackathon submission with no commercial use.
• Single founder: The team size is listed as 1, which may limit execution capability.
• Unproven market need: No customer feedback, user data, or adoption metrics are provided.
• Early-stage prototype: No indication of scalability, performance, or long-term viability.
• No pricing or monetization strategy: Unclear how the tool will be monetized or whether it will ever reach a paid model.

1. What specific problems are you solving for users, and how do you know they exist?
2. Have you tested this idea with any real traders or analysts? If so, what feedback did you get?
3. How do you plan to scale beyond a single developer and a hackathon prototype?
4. What is your roadmap for monetization and product development?
5. Are there existing tools in the market that already solve similar problems?