Thanks again for the constructive feedback. I understand your point, and I agree that the best way forward is to keep developing the platform and let the work speak for itself over time.

Regarding registrations, The Campaign Finder is still in a private testing phase, so the number of registered users is currently small. I don't want to present that as a meaningful adoption statistic yet. My priority right now is making sure the core features work reliably before opening it more widely.

Yes, I plan to make it available to the wider Bitcointalk community once the testing phase is complete. The main campaign-finder service will remain free for campaign hunters and participants.

There are ongoing costs for hosting, development, maintenance, and other services. The plan is to keep the public campaign-finder side free and sustain the project through a separate manager-side system that provides campaign management and automation features. Managers can use those features through Campaign Week Credits, which is intended to cover the ongoing costs while keeping the participant side free.

I'm still testing the manager system privately with real campaign workflows, so I want to make sure it is reliable before opening that part to the community.

And noted about highlighting posts. I understand your point, and I'll keep my future replies focused on the discussion rather than highlighting my own posts.

Thanks again for the feedback. I appreciate it, and I'll keep the thread focused on the project and its development.

---

💡 HAVE AN IDEA FOR THE CAMPAIGN FINDER?

The Campaign Finder is being developed with the Bitcointalk community in mind.

Instead of guessing which features users want most, I want the community to have a direct way to suggest ideas, discuss them and show which improvements are actually useful.

That's why I have added a new:

Feature Requests & Roadmap

This section allows the community to help shape the future development of The Campaign Finder.

---

🔎 HOW IT WORKS

The process is simple:

1. Someone suggests a feature

A user can submit an idea for something they would like to see added or improved.

For example:

• Telegram campaign notifications
• More detailed campaign reports
• Additional participant tools
• New campaign filters
• Better manager statistics
• Mobile improvements
• New campaign-management features
• New campaign discovery tools

2. The community discusses the idea

Other users can read the request and join the discussion through comments.

This helps explain why a feature would be useful and how it could work.

3. The community votes

Users can upvote feature requests they would like to see.

This gives me a much clearer picture of which features are attracting community interest.

4. The request becomes part of the roadmap

Feature requests can move through different development stages depending on their status.

For example:

• New Idea
• Under Consideration
• Planned
• In Development
• Testing
• Released
• Not Planned

This means users can follow the progress of ideas after they are submitted.

---

🌍 EVERYONE CAN BROWSE THE FEATURE REQUESTS

The Feature Requests page is public.

You do not need an account just to browse the community ideas.

Anyone can see:

• Feature requests
• Descriptions
• Vote counts
• Comments
• Categories
• Development status
• Public roadmap
• Released features

This allows the entire community to see what people are requesting and what is currently being worked on.

---

👍 HOW VOTING WORKS

The voting system is designed to keep the community signal clean.

Everyone can see the vote count.

However, to actually cast an upvote, the user must have a:

Registered + Verified Campaign Finder account

This prevents anonymous vote manipulation while still allowing everyone to see which ideas are receiving support.

Each verified user can vote once for a feature.

They can also remove their vote later.

Example:

Automatic Telegram Notifications

👍 42 Votes
💬 8 Comments

Status: Planned

[👍 Upvote]

If you have already voted:

👍 Voted 43

---

💬 COMMUNITY COMMENTS

Comments are publicly visible.

Anyone can read the discussion.

However, only registered and verified users can post comments.

This helps keep the discussion useful while reducing anonymous spam.

A guest visitor can simply read the discussion.

A registered but unverified account will be asked to verify the account before commenting.

---

➕ SUBMIT YOUR OWN FEATURE IDEA

Want something added to The Campaign Finder?

You can submit your own feature request.

To create a new feature request, you need a:

Registered + Verified Campaign Finder account

The submission form allows you to provide:

• Feature title
• Description
• Why you think it would be useful
• Feature category

For example:

Feature: Telegram Campaign Notifications

Description: Send participants a notification when their campaign progress changes.

Why useful: Participants would not need to repeatedly check the dashboard to see whether their activity has been updated.

Other community members can then vote and discuss the idea.

---

📊 WHY THIS IS IMPORTANT

The goal is not simply to collect a large list of feature requests.

The goal is to understand what the community actually needs.

For example, imagine three requests:

Feature A — 45 votes
Feature B — 31 votes
Feature C — 8 votes

That gives us a useful indication of where community interest is concentrated.

However, votes alone do not automatically decide what gets built.

Development decisions can also depend on:

• Technical complexity
• Security
• Hosting requirements
• Existing architecture
• Development time
• Whether the feature benefits a large number of users
• Whether the requested feature fits the overall direction of The Campaign Finder

The voting system is therefore a community demand signal, not an automatic development ranking.

---

🛣️ PUBLIC DEVELOPMENT ROADMAP

The Feature Requests section also acts as a public roadmap.

Users can see which ideas are:

Under Consideration

Ideas currently being reviewed.

Planned

Features that have been selected for future development.

In Development

Features currently being built.

Testing

Features being tested before wider release.

Released

Features that are already available on The Campaign Finder.

This provides more transparency about where the platform is heading.

---

📌 EXAMPLE ROADMAP

PLANNED

• Feature A
• Feature B

IN DEVELOPMENT

• Feature C

TESTING

• Feature D

RELEASED

• My Campaigns Dashboard
• Participant progress tracking
• Campaign activity tracking

The roadmap will continue to change as development progresses.

---

🎯 BUILT AROUND THE COMMUNITY

The Campaign Finder is still growing.

There are many possible improvements that could be added in the future.

Rather than deciding everything internally, I want to give users a direct way to tell me:

"This is what we actually need."

If a feature is useful to campaign managers, participants or campaign hunters, the Feature Requests system gives the community a place to explain it and show their support.

---

🔐 ACCOUNT REQUIREMENTS

To keep the system clean:

Anyone can:

• Browse feature requests
• Read descriptions
• See vote counts
• Read comments
• View the roadmap

Verified registered users can:

• Upvote features
• Remove their vote
• Submit new feature requests
• Post comments

Unverified accounts:

Can browse everything, but must verify their account before voting, commenting or submitting a feature.

---

🌐 TRY THE FEATURE REQUESTS PAGE

Visit:

Feature Requests & Roadmap

Browse the current ideas and see what the community is asking for.

Have an idea that could improve The Campaign Finder?

Submit it and let the community decide how useful it is.

---

🙏 HELP BUILD THE NEXT VERSION

The Campaign Finder is being built step by step.

Your feedback, ideas and real-world experience can directly influence what gets developed next.

Have an idea? Submit it.

Like an idea? Vote for it.

Have something useful to add? Join the discussion.

Together, this can help turn The Campaign Finder into a tool that is shaped by the needs of the Bitcointalk community.