Crypto Battle Buddy

Company: Crypto Battle Buddy

Self-reported basis: The entire analysis is based on a single project description submitted by the author to the OpenAI 2026 hackathon on Devpost. No external verification, revenue, customer data or traction evidence is available.

What it appears to be: A behavioral discipline tool for crypto investors that helps users track adherence to their own pre-defined trading plans, using threshold-based triggers and visual feedback.

What changed: The project was submitted as a hackathon entry; no indication of prior development or commercial activity.

Single most important open question: Is there any evidence of user adoption or engagement beyond the author’s own use case?

The description states that Crypto Battle Buddy is a platform designed to help crypto investors remain anchored to their own predefined strategy. It uses threshold-based plans for individual crypto assets, and evaluates live market prices against those plans.

• The app monitors fresh market conditions.
• It evaluates whether thresholds are inactive, approaching, actionable, executed, or missed.
• Users must deliberately ARM (activate) an asset before recording any action.
• It includes two visual discipline indicators:
  • Current-temperature circle: reflects current relationship to plan and market.
  • Lifetime circle: shows long-term behavioral patterns from recorded actions.
• The system does not prescribe recovery trades; it provides factual feedback based on user’s own plan.

Inference: The app is built as a mobile application using Flutter and Dart, with integrations for live price feeds from CoinGecko, Coinbase, Binance, and Kraken.

Not evidenced: No information about actual product functionality beyond the author's description, no screenshots, no user interface details, no data on how thresholds are implemented or how feedback is delivered.

The project’s positioning is centered around behavioral discipline in crypto investing.

• The core principle is: “The mentor does not rescue the user. It makes the truth difficult to ignore.”
• Mission: Help users build lasting discipline by turning planned decisions and actions into accountability.
• Vision: Create a behavioral operating system for long-term crypto investors.
• The platform aims to reduce emotional trading, encourage deliberate decision-making, and help users recognize harmful patterns.

Inference: The author positions the tool as a self-help or coaching mechanism rather than a trading assistant or portfolio manager.

Not evidenced: No evidence of how this differs from existing tools or whether it has been tested with real users beyond the author’s own use case.

The description states that Crypto Battle Buddy is intended for long-term crypto investors, specifically those who want to:

• Trade less emotionally
• Make deliberate decisions
• Recognize harmful behavioral patterns
• Remain accountable to their own strategy

Inference: The target customer is likely a self-directed, disciplined investor who already has a trading plan but struggles with emotional adherence.

Not evidenced: No information about user personas, demographics, or whether the tool targets beginner or advanced traders.

The description does not provide any details on pricing, monetization, or business model.

• The app is described as a personal discipline tool.
• It includes features like threshold plans, ARM controls, and visual feedback.
• No mention of subscriptions, in-app purchases, or paid features.

Inference: If the product is commercialized, it may be free-to-use with optional premium features or a freemium model.

Not evidenced: No pricing structure, revenue streams, or monetization strategy are described.

The author states that the app was built using:

• Flutter and Dart
• Live price integrations from CoinGecko, Coinbase, Binance, Kraken
• User-authored threshold plans
• Per-asset ARM state
• Persisted threshold-step state
• Recorded execution and missed-action events
• Current-cycle and lifetime discipline calculations
• Factual report and export infrastructure

Inference: The app is a mobile application with backend integration for live crypto data.

Not evidenced: No information on scalability, security, or deployment architecture. No mention of cloud services, API usage limits, or data privacy.

The project was submitted as part of the OpenAI 2026 hackathon. The author is the sole team member.

• No evidence of user adoption.
• No evidence of revenue or customer base.
• No mention of product iterations, feedback loops, or usage metrics.
• No indication that the tool has been used beyond the author’s own personal use case.

Inference: The project is in early development and likely not yet released to users.

Not evidenced: No data on user engagement, retention, or product-market fit.

The description does not mention any competitors or similar tools.

• No comparison with existing discipline or behavioral tracking tools.
• No indication of how the app differentiates from other crypto tools or platforms.
• No evidence of market analysis or competitive positioning.

Inference: The tool may be a niche solution for disciplined traders, but its place in the broader crypto ecosystem is unclear.

Not evidenced: No information on existing tools, market size, or competitive landscape.

• Single founder project: Only one team member (Eric Heffner) is listed.
• No traction or user data: The tool has not been tested with users beyond the author.
• Unproven market demand: No evidence of a real need or market for this specific solution.
• Limited scope: The app appears to be a personal tool, not scalable for mass adoption.
• Unclear monetization: No business model is described.

Inference: The project may lack commercial viability without further development and user testing.

Not evidenced: No evidence of risk mitigation strategies or scalability plans.

1. What specific behavioral patterns are you trying to correct, and how do you know they’re problematic?
2. Have you tested this tool with other users beyond yourself?
3. How do you plan to scale the product beyond a single-user personal tool?
4. What is your roadmap for monetization or commercialization?
5. Are there any existing tools that already solve this problem, and how does yours differ?