My name is Steve McGrath. I'm from Quebec City, Canada. I used to build WordPress/My Starter Blog websites for internet marketing back in the day, along with many types of software professionally.

These days, I mostly build things for my own use.

My mcgrath.ca domain has been around since 2000. I originally used it for family email, and around 2008 it became my personal blog. This year, I decided to use it for something quite different: a giveaway using cryptocurrency as the prizes, with a real-life giving-back twist.

Sounds simple enough, right? :)

So how did “I mostly build things for myself” turn into building an entire community participation platform? Good question. I certainly wasn't planning to build one. :)

Sometimes a project becomes much bigger than you ever intended.

So how did a simple crypto giveaway eventually become MISPMC?

It Started With a Giveaway

The idea was simple: create a free giveaway using crypto as the prizes and try to do some good along the way.

Treasure Club grew from my Worthless and UFD giveaway project.

I had to install phpList to keep track of the people who joined. Then I built my own system around its database to determine who was eligible and randomly pick the winners.

Very few people joined at first.

I also didn't really want Treasure Club to look or feel like a mailing list.

If I saw “Join our mailing list”, I knew what I'd probably wonder:

“If I join, am I going to get bombarded with emails?”

That wasn't what I wanted Treasure Club to become.

The goal was participation, giveaways and giving back—not filling people's inboxes.

That's when I started working on my own solution to replace phpList.

At first, the plan was still pretty simple.

Keep the members.

Verify them.

Determine who's eligible.

Pick the winners.

How difficult could that be? :)

But while I was working on the replacement, I still had current members in phpList.

Before migrating them to the new Treasure Club, I needed them to update their information.

So I finally needed phpList to do something rather obvious for mailing-list software...

Send an email. :)

What could possibly go wrong?

The Mailing List I Wasn't Using as a Mailing List

When I tried to send the campaign, I discovered that my phpList campaign setup wasn't actually working.

I had never tested that part because sending campaigns hadn't been the reason I installed phpList in the first place.

And there was another problem I had already discovered through the giveaways.

I could email potential winners and the emails reached them, but in at least a few cases, they couldn't simply reply successfully.

My hosting provider's spam-filtering software flagged their replies as spam.

Neither they nor I could lower the threshold enough to “unspam” those replies.

The winners had to contact me using another email address.

That wasn't the experience I wanted.

So I came up with another solution.

Instead of depending on email replies—and potentially running into spam filters on my hosting or other hosts—the winner could receive a secure confirmation link from Treasure Club.

Click the link. Accept the prize inside Treasure Club.

That problem eventually helped shape the prize-confirmation system we use today.

By then, continuing to build around phpList made less and less sense.

I was already working on my own replacement, so these problems gave me even more reason to keep going.

The replacement still sounded simple enough:

Email.

Alias.

Wallet.

Verification.

Eligibility.

Pick winners.

Surely that would be enough. Right? :)

Then Busy Bee Arrived

Well...

Another important lesson actually came during the phpList phase.

I nicknamed one participant Busy Bee.

There were bursts where many new members appeared within only a few minutes.

Was it abuse?

Maybe.

Could I prove it?

No.

My gut was telling me something wasn't right.

Deep down, I knew there could be legitimate explanations even before asking ChatGPT.

Students at the same school, people sharing a connection, exchange students, friends joining together, or people responding to the same promotion can all produce activity that looks suspicious.

So I decided to give them the benefit of the doubt.

Or, as I would naturally say it in French:

« J'ai donné une chance au coureur. »

That distinction became important.

I didn't want a system that simply said:

“This looks unusual. Ban it.”

I wanted one that could record signals, provide context and allow a human to make the final decision.

That experience helped shape MISPMC's approach to Trust, activity history, wallet information, administrative review and anti-abuse tools.

In a strange way, Busy Bee helped design part of MISPMC before MISPMC even had a name. :)

Did Busy Bee ever win a prize?

I honestly don't know.

But I still honored the giveaways and transferred the prizes to the winners.

At first, I simply transferred the prize to the wallet provided by the winner.

Strangely, once I started asking potential winners to reply to my email with a random verification code before receiving their prize, I started seeing fewer new members.

Was there a connection?

Maybe.

Could I prove it?

No.

And that's exactly the point.

But what happens when you start solving one problem after another?

Then I Started Asking Too Many Questions

Once I started building the replacement, one question kept leading to another.

If people have accounts, shouldn't they have profiles?

If they participate, shouldn't useful participation be recognized?

If somebody creates something useful, shouldn't other members be able to use it?

What if someone creates a great image, template or resource?

Why not make it a Community Asset?

What if one member has a problem and another member already knows the solution?

Why not help them help each other?

That's how Community Assets and Community Help entered the picture.

And that's also where one rule became important to me.

What does “helping” actually mean?

“Google It” Isn't Community Help

Someone asking a question is looking for actual help.

Simply answering “Google it” or “ask AI” isn't much of an answer.

Ironically, a good answer might absolutely explain how to use Google or an AI tool to solve the problem.

A member might show them what to search for, how to phrase the question, or how to use the results.

The difference is simple: did they actually help the person move forward?

That's what Community Help is supposed to encourage.

But while I was thinking about how members could help each other, I realized I was doing something similar during development.

I was getting help from ChatGPT and Grok too.

Except sometimes, what I really needed wasn't help agreeing with me.

How did ChatGPT challenge me when I got a great idea?

I Asked ChatGPT to Disagree With Me

I used ChatGPT throughout much of the development of MISPMC, along with Grok for some ideas and second opinions.

But I didn't only want ChatGPT saying:

“Great idea, Steve!”

That wouldn't help very much. :)

So I started using Truth Mode and Red Team, two prompting techniques I learned from a YouTube video at exactly the right time.

I want to give credit to Sabrina Ramonov for her video “Secret codes for ChatGPT & Claude.”

Watch Sabrina Ramonov's video on YouTube.

Truth Mode meant: don't tell me what I want to hear. Tell me what I need to hear.

Red Team went a step further:

Try to break the idea.

How could someone abuse this?

What happens if a bad actor finds a loophole?

Could someone manipulate invitations, points, Trust or draws?

What happens when somebody deletes their account?

What privacy requirements should I be aware of around the world?

Are there already other products similar to MISPMC?

If there are, what makes MISPMC different?

What am I forgetting?

Sometimes one innocent little idea opened a rather large can of worms. :)

But those discussions helped expose weaknesses, unintended consequences and edge cases before some of them reached real members.

Eventually, I found myself using another test too.

One that had absolutely nothing to do with crypto.

Would this make sense to your hair salon?

The Hair Salon Test

MISPMC isn't supposed to replace someone's website.

A hair salon can keep its website.

A restaurant can keep its website.

A local shop can keep its website.

MISPMC adds the community layer beside it.

So while designing features, we kept coming back to a fictional local hair salon.

Would this feature actually help them?

Would the owner understand it?

Would the clients use it?

Would it create more work than value for everyone?

That last question became especially important.

Because I already have a job.

And I definitely don't need a second one. :)

So how can I manage Treasure Club and MISPMC while keeping my job?

I Don't Need a Second Job :)

For weeks, I built much of MISPMC early in the morning, after work and on weekends.

Most mornings, I worked on it before starting my regular job at 7:30.

Weekends became development time too, while still keeping some social time with my friends... and I thank them for their patience. :P

Yes, less than usual during the last few weeks. :)

But the goal was to have a stable Treasure Club available as soon as possible.

I enjoyed building it, but one thing became very clear:

I don't need another full-time job. :)

That was one reason I hesitated about having free and commercial editions of MISPMC at all.

Did I really want to turn something I built for Treasure Club into another business?

More importantly, could MISPMC eventually operate without requiring me to personally support every project using it?

My previous discussions with ChatGPT helped me make that decision.

MISPMC would need to be designed so that projects could operate it themselves, automation could handle as much as reasonably possible, and local technical people could eventually help those who needed more support.

That made the idea much more realistic without turning MISPMC into my second job.

But there was still another question.

Would there actually be enough potential communities to make free and commercial editions worthwhile?

That's when I started looking at crypto.

And the numbers were a little crazy.

What if only a tiny number of all those new daily crypto projects wanted a real community to help spread the word about their coins?

What If Only a Tiny Number?

As of this writing, CoinMarketCap tracks more than 62 million cryptocurrencies and tokens.

And that number keeps growing, although how CoinMarketCap tracks them could change over time.

Its data has shown periods where more than 100,000 new tokens can appear in a single day.

Don't take my word for it. :)

CoinMarketCap — Cryptocurrencies Tracked.

By the time you're reading this, that daily number could be higher—or lower. Crypto has a funny way of changing things quickly.

Obviously, creating a token doesn't automatically make it a serious project.

Far from it.

But even with that enormous number, MISPMC wouldn't need thousands of projects.

What if ten serious projects wanted to build active communities?

What if later it became twenty?

Or fifty?

A tiny number could already make the idea interesting.

And here's the part I really liked:

They wouldn't necessarily have to pay me.

The Community Edition is intended to be free.

A crypto project could use it to bring people together, encourage participation, create and share Community Assets, answer questions and help spread the word about its coin.

Would using MISPMC prove that a crypto project is serious or trustworthy?

Absolutely not.

Software can't guarantee that.

But a project that keeps communicating, creating and showing signs of an active community gives people more information to judge the project for themselves.

And that reminded me of something I'd heard many years ago.

Something about businesses that kept advertising during difficult economic times.

Was my memory right, or was my Corporate Cap making things up? :)

The Corporate Cap

Don't worry.

I promise not to wear it for too long. :)

I remembered hearing something interesting during the recession years.

Companies that continued advertising during difficult economic times often did better afterward than companies that significantly reduced or stopped advertising.

But was I remembering that correctly?

So I checked.

Research covering past recessions supports the general idea that companies maintaining or increasing advertising can perform better afterward than companies that substantially cut it.

Does that mean advertising magically saves a business?

Of course not.

There are no guarantees.

But the basic idea stayed with me:

When times are difficult, disappearing may not be the best way to remind people you're still alive.

And suddenly I wasn't thinking about the recession anymore.

I was thinking about today's rather flat crypto market—unless you DCA (Dollar Cost Average), like I did. :)

Could the same basic idea apply to a crypto project during a down or bear market?

We're Still Here

Crypto has down and up markets, just like stocks, real estate and other markets.

As of this writing, crypto is generally in a bear market.

Interest drops.

Prices fall.

Some projects become very quiet and wait for the next bull run.

And that environment influenced MISPMC too.

If crypto had been in the middle of a strong bull run, I might never have thought as much about helping projects and communities keep spreading the word when interest is lower.

Community Assets might not have become what they are today.

But what happens if a project and its community keep showing signs of life?

Someone creates an image.

Someone else creates another.

A member shares a Wolfy, UFD or Worthless Community Asset on social media.

Another person sees it.

Maybe they become curious.

Maybe they visit Treasure Club.

The message is simple:

We're still here.

Does staying visible guarantee that a coin will succeed?

Of course not.

If I could guarantee crypto success, I'd probably be writing this—but not from my apartment. :)

But continuing to create, communicate and spread the word may help show that a project and its community haven't simply disappeared.

That's one reason Community Assets became much more interesting to me.

But then my Corporate Cap whispered something else.

Why should this idea stop at crypto?

What About the Little Shop Down the Street?

Forget millions of crypto tokens for a moment.

Think about one little bakery.

Or a coffee shop.

Or our now-famous hair salon. :)

A small business may not have a huge advertising budget.

But it may already have something very valuable:

Loyal customers who genuinely like it.

What if those customers had a community beside the business's existing website?

Maybe they suggest ideas.

Maybe they vote in a poll for the next flavor, product or service.

Maybe they answer questions.

Maybe they create or share useful Community Assets.

Maybe they invite a friend who would genuinely enjoy the business.

And maybe the owner occasionally wants to say thank you.

That's where Community Draws could become interesting.

A bakery could give away a dozen donuts.

A coffee shop could give away coffee.

A hair salon could give away a haircut.

Another business could choose whatever makes sense for its own community.

The goal isn't to turn loyal customers into an unpaid advertising department.

It's to give people who already like something a place to participate if they want to.

And if their participation also helps spread the word about a business they already like?

Well...

My Corporate Cap seems pretty happy about that. :)

But a small business with a small advertising budget may have another obvious question:

How much is all of this going to cost me?

Free Really Does Mean Free

MISPMC Community Edition is intended to be a genuinely useful free edition.

Not a useless demo where every interesting feature is locked away.

A small business, crypto project, nonprofit or other community should be able to start without needing a software budget.

So naturally someone might ask:

What's the catch?

There really isn't one.

If the Community Edition provides everything a project needs, it can simply keep using the Community Edition. No strings attached.

There may be optional ways to support the project, but using them isn't required.

But what if the project grows and eventually wants more?

That's where the Growth Edition and Professional Edition could provide another path.

And I don't want those editions to break the bank either.

The current working target is approximately $50–60 CAD per project per year for the Growth Edition.

For the Professional Edition, approximately $100–120 CAD per project per year.

Per year. Not per month.

Those targets can still evolve before the commercial editions are released.

But affordability is part of the idea.

Software designed partly for small communities isn't very useful if small communities can't afford it.

And money isn't the only resource a community may already have without realizing it.

Sometimes its greatest resource may be the people themselves.

What happens to decades of knowledge when someone retires?

What About Retirees?

People retire from their jobs.

They don't retire from everything they've learned.

So where does all that knowledge and experience go?

A retired graphic designer might help review or create Community Assets.

A retired mechanic might answer a question.

A retired teacher, accountant, programmer, tradesperson or business owner may know something another member needs.

They might moderate.

They might answer questions.

They might help someone solve one problem.

Nobody needs to turn retirement into another full-time job. :)

But some retirees may enjoy having another place to participate, meet people and contribute something useful when they feel like it.

And maybe helping others adds a little value to their own lives too.

After all...

Does getting older suddenly make all that knowledge Worthless?

I own enough Worthless to know the answer to that one. :)

Maybe some of that experience can become Goodness instead.

Which brings me right back to where this whole journey started.

How did Worthless become part of an idea about giving back?

From Worthless to Goodness

Treasure Club grew from my Worthless and UFD giveaway project.

From the start, the idea became bigger than simply giving away crypto.

I liked the irony. :)

Could participation help a community?

Could members help each other?

Could the project eventually help nonprofits like Enfant Soleil and other causes too?

Could it help fund research into diseases like diabetes, myasthenia gravis, cancer and others?

Could something called Worthless actually help create some Goodness?

A coin called Worthless helping do something worthwhile.

And maybe, in our own small way, we could also show that crypto isn't only about scams and rug pulls.

Later came Wolfy, the coin I created myself and the face of Treasure Club.

With Wolfy, giving back became part of the idea from the beginning—including helping nonprofits and supporting research into more diseases over time.

Those ideas eventually became part of Treasure Club—and MISPMC became one of the tools for making them possible.

But software ideas are easy when you're the only person testing them.

What happens when real members finally get their hands on it?

From Database Records to a Real Community

The original job was basically:

Replace the part of phpList I was using and keep Pick Winners working.

Instead, MISPMC gained profiles, verification, wallets, roles, Trust, points, invitations and Community Draws.

Then came Community Help.

Community Assets.

Moderation.

Administration.

And, yes...

another table in the database.

Then another one.

And probably another test to go with it. :)

But many of the most important decisions weren't theoretical.

Treasure Club became the first real MISPMC community.

Real members registered in ways I hadn't predicted.

They submitted Community Assets.

They exposed edge cases.

They made me rethink assumptions.

They showed me where the interface could be improved.

In other words:

They used the software like real people instead of like the guy who wrote it.

Who knew? :)

So when did MISPMC finally stop being only a development project?

When did real members finally get their hands on it?

ChatGPT Kept Me Focused on 1.0 :)

By this point, I had another problem.

Ideas. Lots of ideas.

I probably had millions of ideas for new modules and improvements.

Okay... maybe not millions.

Hundreds? Absolutely. :)

And every new idea had a funny habit of creating three more.

Fortunately, ChatGPT kept reminding me:

“Not for 1.0.”

We kept a growing list of ideas and improvements for later while staying focused on what Treasure Club actually needed to launch.

Sometimes I'd come up with another great idea before or after my shower.

And ChatGPT would basically say:

“Did you take your shower, Steve?” :)

Followed shortly afterward by:

“Good idea... but later.” :)

That helped me keep moving instead of turning version 1.0 into version 27 before anybody could use it.

And reaching the soft launch didn't stop the ideas either.

Members started creating Community Assets.

I started sharing them on social media.

Then came another idea:

What about a “Share on X” button?

This time, the idea didn't stay on the future list.

Share on X was added.

I eventually used it to share a member's Community Asset and used the creator's invitation credit instead of mine.

That felt right.

If their Asset helped bring someone new to Treasure Club, they should get the credit for it.

So reaching 1.0 wasn't about running out of ideas.

It was about having someone—or in this case, something—keep telling me:

“Good idea... but later.”

So when did all that finally become stable enough for real members?

September 24, 2026

On the morning of September 24, before starting my regular job, I finished the final checks.

Then I soft-launched Treasure Club on MISPMC 1.0 to my existing phpList members.

Every reasonable effort was made to reach those existing members and give them the opportunity to move to the new Treasure Club.

Not everyone validated their email and completed the move.

That meant the number of Eligible members shown in my daily Treasure Club updates dropped when we moved to the new system.

Were some of those old accounts connected to the unusual activity I had seen during the Busy Bee days?

Maybe.

Could I prove it?

No. :)

What I did know was that the new Treasure Club started with members who had completed the new verification process.

That was the moment MISPMC stopped being only a development project.

Real people were using it.

And almost immediately, reality started improving the software.

Changes followed from situations created by actual members.

New Assets started appearing.

Things I hadn't anticipated started showing up.

And ideas that looked good during development finally had to survive the real world. :)

That's exactly what I wanted Treasure Club to become.

It isn't simply the first MISPMC community.

It's the proving ground.

The soft launch gave me time to watch, test, improve and make sure the foundation was stable.

And now?

The soft launch is over.

As of today, Treasure Club is officially open for members. :)

So where do Treasure Club and MISPMC go from here?

The Seven-Step Plan

I actually have a plan. :)

Treasure Club is Step 1.

Yes.

Apparently replacing the part of phpList I was using required a seven-step plan. :)

Step 1 — Treasure Club

Make Treasure Club stable and more user-friendly, grow the community, continue the giveaways, and use it as the first real-world proving ground for MISPMC.

And start adding some of those post-1.0 ideas that ChatGPT kept stopping me from adding so I would stay focused long enough to actually deliver 1.0. :)

“Good idea... but later.”

Well, some of those ideas can finally become “later.” :)

Step 2 — Prove the Network

Treasure Club proves MISPMC with one real community.

The next step is proving that the Network and Project structure works properly with multiple Projects.

And one of the most useful parts of that structure is:

One login to rule them all. :)

A member shouldn't need a different account and password for every Project inside the same MISPMC Network.

But having one login doesn't mean automatically joining every Project in that Network.

Members choose which Projects they want to join and, by Project, whether they want to be visible to other members.

Think about a franchise with many locations.

A member might join the main office Project for company-wide draws and offers.

But that same member might regularly visit Location 10 and Location 24 in Town A, so they join those Projects for local offers, draws and community activities.

Later, they start visiting Location 67 in Town B and decide to join that Project too.

Same account. Same login. Four Projects they chose to join.

They don't need to join all the other franchise locations just because they're part of the same Network.

The same idea could work for a local shopping mall, where participating stores have their own Projects, or a town/local business network, where independent businesses maintain their own communities.

And my initial Steve's Crypto Journey could have separate Projects for different crypto communities.

For my own testing, I already own many different crypto coins, so I can use some of those projects—Toshi, Turbo, SPX6900 and others—as additional communities to help prove the Network and help spread the word about those coins too.

I'm not interested in creating empty Projects just for the sake of saying MISPMC has more Projects.

They should have a real purpose and, hopefully, real participation.

The goal is to make sure each Project remains properly separated while sharing the underlying MISPMC platform and account system.

Thus, a member who owns Toshi could choose to join both the Treasure Club and Toshi Projects, using the same MISPMC account.

That doesn't mean those crypto projects are affiliated with or officially involved with MISPMC.

They're simply projects whose coins I already own and can use as real-world examples for testing.

If one login can give members access to the Projects they choose across a Network, how many different kinds of communities could MISPMC eventually support?

Step 3 — MISPMC Community Edition

Once the Network architecture has been proven, prepare the free Community Edition so other people and projects can create communities of their own without needing a software budget.

Before that broader release, I also need to remove any remaining hard-coded language so adding more languages later will be possible without rebuilding everything.

English and French are the beginning.

They don't have to be the end—even if I don't understand the next language. That's the power of community.

Step 4 — Growth Edition and Professional Edition

Build the optional commercial editions for projects that eventually need more, while keeping the annual pricing affordable.

The Community Edition should remain genuinely useful for projects that don't need the paid editions.

Step 5 — Connect Communities

As more independent communities use MISPMC, the platform could eventually become a hub for discovering willing communities.

A Project might find another community interested in collaborating, sharing knowledge, creating something together or helping spread the word.

Participation would be voluntary.

A community decides for itself whether it wants to participate or work with another community.

Could independent communities become more useful by finding each other?

Step 6 — Make It Easy to Run

Automate installation and updates for the Community Edition, and automate licensing and upgrades for the commercial editions as much as possible.

The goal is simple: once MISPMC is installed, keeping it up to date shouldn't become another technical project.

MISPMC shouldn't become my second job—and Project owners shouldn't need me standing beside them to operate or maintain it.

The goal is for Projects to manage their own communities while MISPMC handles as much of the repetitive work as reasonably possible.

MISPMC itself can also be used to support Project and Network Admins.

Admins could use the community to ask questions, find solutions and learn from other people running MISPMC Projects and Networks.

And if a Project owner isn't very technical, they could use a local person with basic web-hosting skills to handle the technical side.

In a best-case installation, my goal is for the basic technical setup to take less than an hour: create the database and email accounts, install MISPMC and get it running.

Configuring the actual Network and Projects to fit a community could take longer—and that's perfectly normal.

The important part is that someone shouldn't have to pay a technician for five hours just because installing MISPMC is complicated.

Ideally, a technician who already understands basic web hosting should be able to get the software running quickly.

After that, automated updates should help keep it running without repeatedly calling that technician.

And they shouldn't have to depend on me personally to do it.

The goal is for an Admin to eventually be able to ask:

“Could MISPMC actually be easier to run without Steve than with Steve? :)”

Step 7 — Open It to Other Developers

Eventually, MISPMC shouldn't depend entirely on me being able to do everything.

Other developers could contribute ideas, improvements, modules and integrations.

That could let MISPMC grow in directions I would never have the time—or maybe even the knowledge—to build myself.

Because if the community can help build the community, why shouldn't developers be able to help build MISPMC too?

Recommendations

I mentioned earlier that there are optional ways to help support Treasure Club and MISPMC.

One of them is Recommendations in Community Assets.

These aren't random products I found because they have affiliate programs.

They're products and services I actually use—or have used—for Treasure Club.

Some of those recommendations contain affiliate links.

If a member decides to buy something through one of those links, I may receive a commission at no additional cost to them.

But buying anything is absolutely optional.

A member involved with one or several crypto projects may discover a tool that could help them create content or spread the word about their own projects.

Someone involved in a completely different type of project might find a use for one too.

If they were going to buy it anyway and choose to use my link, the commission can help support Treasure Club and MISPMC.

My Corporate Cap approves. :)

But money and software aren't what make a community work.

What happens when members start helping build the community themselves?

The Community Helps Build the Community

MISPMC started because I needed something better for Treasure Club.

But somewhere along the way, an important idea became obvious:

I shouldn't have to create everything myself.

A member can create a Community Asset.

Another member can use it to help spread the word.

Someone can ask a question.

Another member may already know the answer.

Someone with years of experience can help moderate or review contributions.

And sometimes a member may suggest an idea I never considered.

That's the part I find exciting.

The people using a community can also help make that community more useful.

Not because they have to. Because they want to.

MISPMC simply gives them some of the tools to do it.

And if that works?

Maybe Treasure Club won't be the most interesting thing MISPMC creates.

Maybe the most interesting part will be seeing what each community does with it.

But we're still only at version 1.0.

So where does the journey go from here?

We're Only at 1.0

After everything you've just read, it's easy to forget one small detail.

MISPMC is only at version 1.0.

There are still plenty of ideas waiting on that famous post-1.0 list. :)

Some will probably become small improvements.

Some may become entirely new modules—and there are already many of those on my to-do list.

And some ideas may never happen at all.

That's okay.

I don't want MISPMC to grow simply by adding features.

I want it to grow because those features are actually useful to the communities using it and the Project Admins running them.

Treasure Club will continue being the proving ground. Two of its coins already have monthly draws planned for the next nine years, so I'm definitely not planning for the short term. :)

Other Projects and Networks can eventually teach me things Treasure Club never could.

And other members, administrators and developers may see possibilities I haven't even thought about yet.

That's why 1.0 isn't the destination.

It's simply the point where MISPMC became real.

This whole thing started because I needed a better way to run a crypto giveaway.

Somehow, I ended up building a community participation platform designed to help people participate, help each other and spread the word about the Projects they care about. :)

So what's next?

I guess we'll have to build it—and find out together.

Keywords: MISPMC,crypto,ChatGPT, hair salon, origin, story