# BSV Radar

<figure><img src="/files/pXqXusvnQU9xUy6HjebA" alt=""><figcaption></figcaption></figure>

### Project Overview

* **Project Name:** BSV Radar
* **Geographic Reach:** Global
* **Industry:** Blockchain / Web3 Community Tools
* **Website:** <https://bsvradar.com>
* **BSV Integration:** Live for micropayment tipping, with broader BSV feature expansion planned

### Executive Summary

BSV Radar is a community directory and professional network for the BSV ecosystem. It helps users discover active apps, helps builders find collaborators, and gives the ecosystem a credible public reference point that counters the perception of inactivity.

### Business Challenge

**Industry Problem:**

The BSV ecosystem includes applications across identity, gaming, micropayments, timestamping, and enterprise tooling. Yet discoverability remained weak. New users struggled to find active products, and builders often worked in isolation.

**Market Context:**

Outside the community, BSV was often perceived as inactive. Inside the community, users lacked a clear way to find where to spend and use BSV, while developers lacked shared best practices around UX, onboarding, and marketing.

**Specific Problem:**

BSV Radar addresses the absence of a central, searchable, community-driven directory for the ecosystem. It combines app discovery, social proof, and professional networking in one place.

**Limitations of Traditional Systems:**

* Forum posts, social threads, and static lists did not support structured search or ongoing curation.
* Informal channels did not provide credible validation, reputation signals, or durable ecosystem visibility.
* Builders needed more than listings — they needed shared infrastructure for onboarding, discovery, and collaboration.
* Many users expect internet content to be free, so any monetisation model had to let them experience value before paying.

### Why BSV Blockchain?

**Key Selection Criteria:**

* Stable protocol — provides a dependable foundation for a long-lived public ecosystem resource.
* Low fees and high throughput — make direct tipping and future pay-per-feature mechanics practical.
* SPV support — enables lightweight verification without requiring users to run full nodes.
* UTXO-based architecture — supports a lawful, privacy-preserving data model suitable for long-term trust.

**BSV Features Utilised:**

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Micropayments</td><td valign="top">Enables direct tipping and creates a path toward practical pay-per-feature monetisation</td></tr><tr><td valign="top">Stable Protocol</td><td valign="top">Provides a reliable base for a persistent community directory and networking platform</td></tr><tr><td valign="top">SPV</td><td valign="top">Supports lightweight verification and improves accessibility for client-side use cases</td></tr><tr><td valign="top">Identity Infrastructure</td><td valign="top">Supports Sigma Identity for passwordless, blockchain-anchored authentication</td></tr><tr><td valign="top">Future Extensibility</td><td valign="top">Creates a foundation for later use of smart contracts, tokenisation, data storage, and overlay networks</td></tr></tbody></table>

### Solution Architecture

**System Overview:**

BSV Radar operates as a community-curated application directory combined with a professional network for the BSV ecosystem. It brings together app-store style discovery, community reviews, reputation signals, and profile-based networking.

**Key Technical Components:**

* App discovery across categories, newest, trending, top-rated, most-reviewed, and alphabetical views.
* Detailed app listings with project links, contextual descriptions, and information on BSV features used.
* User profiles showing reputation, activity history, organisational memberships, and skills.
* Review and reputation systems, including one upvote per user and contributor XP for approved submissions.
* Authentication through Google and GitHub, with Sigma Identity integration for BSV-native passwordless login.
* Additional community modules including jobs, classifieds, blog content, tipping, and a graveyard of defunct projects.
* Onboarding flows, guidance for first-time users, and Quests that connect structured learning paths to relevant apps and tools.

### Implementation Process

**Deployment Status:**

BSV Radar was built and deployed within one month. The platform is live and continues to expand as a public discovery and collaboration hub for the BSV ecosystem.

**Current Adoption:**

* The platform was created by a solo builder known as Crumbs, whose design-led approach focused on usability and low friction.
* Early work focused on manually seeding listings to overcome the empty-marketplace problem and make the directory useful from day one.
* BSV Radar is seeking investment to expand into a more comprehensive hub for app discovery, events, and hackathon infrastructure.

### Outcomes & Business Impact

**Quantitative Impact:**

* 140 live apps and tools catalogued, and growing.
* 261 defunct apps preserved in the graveyard section.
* 116 registered users on the platform.
* 16 organisations listed.
* 16 ecosystem categories covered.

**Qualitative Benefits:**

* Improved discoverability — users and builders can now find BSV applications through one searchable destination.
* Stronger ecosystem visibility — the platform counters the narrative that BSV is inactive by showing both current and historical activity.
* Better collaboration — user profiles and reputation systems help developers, designers, marketers, and investors find each other.
* Reduced builder isolation — contributors can identify parallel efforts and share knowledge on onboarding, UX, and marketing.

### Challenges & Mitigations

**Key Challenges:**

* Critical mass — a directory is only useful once it contains enough quality listings to feel active.
* Submission friction — detailed listings are valuable, but long submission flows deter contributors.
* BSV acquisition barriers — some potential users still find it difficult to obtain BSV.
* Monetisation expectations — many users expect discovery tools to be free before they are willing to pay.

**How BSV Helped:**

* Low-cost transactions made tipping and future usage-based monetisation models realistic.
* Stable protocol support gave the platform a dependable base for long-term ecosystem infrastructure.
* Native identity and verification capabilities created a path toward stronger trust and richer community features.

**Lessons Learned:**

* Community platforms need visible activity early — nobody wants to join an empty directory.
* Let users experience value before introducing heavier monetisation or access controls.

### Future Vision

**Scaling Plans:**

* Expand Quests as guided, gamified learning paths for beginners, developers new to blockchain, cross-chain developers, and existing BSV builders.
* Grow developer monetisation tools that help listed apps acquire paying users.
* Add hackathon infrastructure and event registration capabilities through ecosystem partnerships.
* Build stronger collaboration tools for developers, designers, marketers, and investors.

**BSV Roadmap:**

* Deepen use of BSV-native identity and payment flows as the platform matures.
* Explore additional BSV capabilities including smart contracts, tokenisation, data storage, and overlay networks.

### About BSV Radar

BSV Radar is building the discovery and collaboration layer for the BSV ecosystem. Its goal is to become the definitive, up-to-date hub for anyone exploring, using, or building on BSV.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://bsv-case-studies.bsvblockchain.org/web-3-community/bsv-radar.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
