Quorum | Rug-Proof launchpad on Solana @QuorumBuild

Quorum doesn't make holders wait blind for 6-9 months. Two checkpoints publish progress publicly: Day 60: Is the project at 10% of its raise goal? ($10K of $100K) Day 120: Is it at 40%? ($40K of $100K) These don't trigger refunds — they're informational. Green means on track. Red means at risk. Every holder can see exactly where a project stands. No surprises at the final evaluation.

"Just don't let one wallet buy too much" sounds simple. Enforcing it on-chain isn't. Here's the actual check inside the contribute() instruction: require!( new_holder_tokens <= max_tokens_per_holder, QuorumError::ExceedsHolderLimit ); max_tokens_per_holder = TOKEN_SUPPLY * 0.1% This isn't a frontend warning you can bypass with a direct RPC call. It's enforced in the program itself. No wallet — including the dev's — can ever hold more than 0.1% during the vesting window.

Most launchpads lock the liquidity pool. Quorum locks the people. When funding opens on Day 15, the dev and every holder get locked simultaneously for 6-9 months. Not just the dev. Not just the pool. Everyone, at the same time. Why simultaneous matters: if only the dev were locked, holders could panic-sell and crash the token before it has a chance to prove itself. If only holders were locked, the dev could exit early. Simultaneous lock = no one has an advantage. The only winning move is building something worth holding.

Why does Quorum start with 30 days of $0-at-stake voting? Because Sybil attacks on a free vote are pointless. There's nothing to extract. Phase 1 is pure signal: any wallet votes on a project's utility. No tokens move. No risk. Just genuine interest, measured publicly. If a project can't get real community backing here, it never reaches the funding phase. The filter happens before money is ever at risk.

Current state of Quorum — June 2026: ✅ Rust/Anchor program — deployed on devnet ✅ Next.js frontend — complete ✅ Whitepaper — EN + ES ✅ Landing + waitlist — quorumbuild.xyz ✅ Solana Foundation grant — applied ✅ Automated test suite — in progress ⬜ Frontend connected to devnet — in progress ⬜ End-to-end demo with real wallets — next ⬜ Security audit — pending funding ⬜ Mainnet — pending audit We're documenting every step here. Not when it's polished. As it happens. If you're building something serious on Solana and tired of watching rugs happen — this account is for you. Follow along. 👇 quorumbuild.xyz

In May 2026 we deployed the Quorum program to Solana devnet. 8 on-chain instructions. Every protocol rule enforced at the program level. Not in the frontend. Not in the backend. In the Rust code that runs on-chain. The program: → initialize_platform → create_project → cast_social_vote → open_economic_phase → contribute (with 0.1% cap enforcement) → register_dev_activity → finalize_funding → refund You can verify the deployment right now: explorer.solana.com/address/DVxHFq… This is not a whitepaper promise. It's deployed code.

We spent weeks on protocol design before writing a single line of Rust. The result: 4 rules that make rug pulls structurally irrational — not just hard. RULE 1: Community validates first (30 days, $0 at risk) → Real signal before real money RULE 2: 0.1% max per wallet — enforced on-chain → Dev can't concentrate. Ever. → Same rule for everyone, including the founder RULE 3: Bilateral vesting 6-9 months → Dev AND holders locked simultaneously → The only rational move is to build RULE 4: 99% auto-refund if project fails → No request. No intermediary. → The program executes it. Each rule exists because we've seen what happens without it.

Before building Quorum, we mapped every rug pull mechanism we'd seen. They all share the same root cause: incentive misalignment at the design layer. The dev can exit before the community has any on-chain recourse. Current launchpads tried to fix this with: → Vetting processes (centralized, bypassable) → Terms of service (not enforceable on-chain) → Locked liquidity (only for the pool, not the dev) None of these are structural. All of them can be worked around. We needed something that couldn't be worked around — because it's the program itself. That's when we started designing the protocol.

Thread: Why we're building Quorum. And why we almost didn't. Our team has 12+ years in software development. The last 4 building web3 projects for others on Solana and EVM chains. In that time we watched the same pattern repeat: → Project launches with real promise → Community forms around it → Dev exits with the money → Community gets nothing We got burned too. Not as victims — as builders who saw it happen to projects we were close to. The question we kept asking: Why does the infrastructure make this easy? That question became Quorum.

Good challenge — and you're right that costless voting is weak signal. Here's how Quorum handles it: Phase 1 (social) is intentionally $0. It's not the enforcement layer. It's the filter layer. The enforcement happens in Phase 2: → Dev is capped at 0.1% by the program Same rule. No exceptions. → Dev + all holders locked simultaneously for 6-9 months when funding opens → If project fails: 99% auto-refund on-chain No request. No admin. The program does it. Slashing rogue devs sounds good — but a dev with 0.1% max has almost nothing to slash. The real deterrent is 9 months of locked capital with no exit. That's structural, not hopeful. Verify the devnet deployment: explorer.solana.com/address/DVxHFq…

What if a rug pull was structurally impossible — not by policy, but by code? That's what we're building. Quorum is a token launchpad on Solana where: → Community validates before money moves → Dev is capped at 0.1% — same as everyone → Dev + holders locked simultaneously for 6-9mo → 99% auto-refund if project fails on-chain No admin override. No exceptions. The rules are the program. MVP deployed on Solana devnet. Verify it yourself: DVxHFqsi2zgxvMLGjmtEBBPJ8o4dFBVWtdSHt77sMMrk This thread documents everything we build. From zero to mainnet. In public. #QuorumBuild #Solana #BuildInPublic

Another wave of rugs hitting Solana this week. This is exactly why we’re building Quorum: 30 days social consensus + 9 months economic proof. Safer launches > faster launches. Would you support slower but much more legitimate projects? Poll: - Yes - No

We’re rebuilding trust in Solana launches. Quorum is a rug-proof launchpad. No more rugs. Only projects that survive scrutiny.

Most launchpads on Solana help you launch fast. We do the opposite. We make you prove your project is real first. If it survives Quorum → it’s built to last. Building the anti-rug infrastructure for Solana.

Exactly. The challenge isn't getting people to see Quorum. The challenge is helping the right people understand why it exists in the first place. A strong narrative in the hands of people who genuinely understand it is far more valuable than broad exposure with no context. That's the kind of visibility we're interested in building.

98% of projects on Solana die before month 3. It’s not bad luck. It’s lack of real skin in the game. #QuorumBuild #AntiRug #Solana

Appreciate that. And I agree — building the system is only half the challenge. Making sure the right people discover and understand it is the other half. We're being intentional about growth at this stage, but aligned creators and genuine advocates are definitely something we're thinking about. The goal isn't just more visibility. It's visibility with the right audience.

Quorum comes from the idea of consensus. Not hype. Not speculation. Consensus. In most of crypto, projects launch first and ask for trust later. We wanted to flip that. The name reflects the idea that projects should earn legitimacy through community scrutiny, commitment, and time before they're fully accepted by the market. That's the core philosophy behind Quorum.

Follow if you believe in projects that last. #QuorumBuild #RugProof #SolanaBuilders

If you’re building something serious on Solana (not 3-day memecoins), we want to know you.

"Most people come to Solana to get rich quick. We came after getting burned." After 4 years building web3 projects for third parties and +12 years of experience as developer team, we decided to launch our own project at the end of 2025. What we found in all this time was the harsh reality: rugs, difficult funding, and projects dying in weeks. That + our fix desire, forced us to pivot. This is how Quorum was born.