[CONCEPT / DISCUSSION] A 24-Day Gamified Community Vault — Seeking Feedback & Fe

[Kostelooscoin]

Hey everyone,

I'm dropping this idea here because Bitcointalk is still one of the few places where people actually read, think, and appreciate old-school crypto experiments instead of just instantly crying "scam" at anything new.

I’ve been sketching out a concept for a monthly on-chain puzzle/game called the Community Vault, but before building or launching anything, I want to be completely upfront: I know the biggest wall this project will hit is trust. In today's market, nobody is going to send sats to a vault controlled by a random anonymous user without assuming it's a honeypot.

The goal of this post is to lay out how the mechanics should work and see if this is actually viable, or if the space is just too paranoid for pure community experiments anymore.
The Core Concept

The idea is a 24-day puzzle challenge:

    The Vault: A public Bitcoin address, starting at 0 BTC, funded strictly by the players who want to join (no free riders—you pay your entry, you're in the game).

    The Hunt: For 24 days, one word drops per day to build a 24-word seed phrase (e.g., following a chain of clues starting from elevator all the way to awkward).

    The Anti-Sniper Mechanism: The public puzzle leads to a decoy seed. Only verified contributors (those who provided proof of their entry transaction) get the real key to sweep the vault on Day 24.

The Real Problem: How Do I Prove Good Faith?

This is where I need your feedback. If I just launch this out of nowhere, everyone is going to assume I'll rug-pull the first month's pool.

To make something like this credible and transparent, what’s the best approach?

    Multisig / Timelocks: Is there a clean technical way to lock the funds so the organizer can't touch them unilaterally?

    Micro-Stakes for Testing: Starting with tiny entry caps (like literally pocket change) just to test the gamification loop without heavy risk.

    Community Oversight: Does a concept like this inherently need a trusted forum member or escrow system to vouch for it?

I’m not here to shill anything or ask for funds right now—I just want to test the waters. Is a social experiment like this completely dead on arrival because of current market toxicity, or is there a way to structure it transparently so people would actually play?

Roast the idea or give me your constructive thoughts—all feedback is welcome.

[Cinexa]

Respect for asking before launching, but the trust problem isn't mainly people are paranoid, it's baked into the design.

If you know the real 24 words seed you are sweeping your vault out whenever you feel like. Dummy public puzzle doesn't help. And if every checked out player will receive the same real seed on day 24 - well, then it's a fee sniping free-for-all, not anti-sniper one.

And for the love of god don't run the game dripping BIP39 words, teach bad habits, people will be picking the wrong tool for community share.

If you want to have less DOA version: you can put the time lock on the coins so no one, not even you can spend it till day 24, not give out the seed at all, choose the verifiable winner by commit-reveal on entry txids etc and pay to that address, or do the same with multisig with known high merit people and dust stakes only; put your sats in first on the same terms.

Interesting social mechanic - wrong cryptographic tool. Though singleAnon seed controlled vault will be perceived as honeypot even in best of intentions case.

[Kostelooscoin]

Spot on. You just hit the exact architectural flaws of the first draft, and I really appreciate you breaking it down instead of just dismissing it.

    The trust/custody paradox: You're 100% right. If an individual holds the keys to distribute them later, it's just a centralized honeypot with extra steps.

    Teaching bad security habits: Letting people handle raw BIP39 words outside of an air-gapped wallet is indeed a terrible precedent. I didn't think about the phishing aspect of training users to type seed words into random interfaces.

Your suggestions actually open up much better technical paths. A timelock combined with a commit-reveal scheme (or a transparent multisig setup with known community members) completely changes the threat model.

If the funds are time-locked on-chain so no one (including the creator) can touch them until Day 24, and the winner is determined by an on-chain mechanism rather than manually handing out a seed phrase, the trust issue shifts from "trust me bro" to "verify the code/script".

Definitely going back to the drawing board to fix the mechanics before even thinking about code. Thanks for the breakdown.