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
Quorum is not for everyone.
If you want to launch a token
tonight and cash out next week —
this is not your platform.
Quorum is for the founder who:
→ Has a real product or a real idea
that needs 6-9 months to prove itself
→ Wants investors who believe in the
project, not just the price chart
→ Is willing to be locked alongside
their community for the full vesting
period — same rules, no exceptions
→ Understands that a failed launch
with 800 real holders is more
valuable than a successful rug
with 10,000 wallets
If that's you — Quorum was built
for you specifically.
If you're building something real
and you launch on https://t.co/ZXiAl42VuW, here's
what happens:
Day 1: Token goes live
Day 2: Early buyers dump
Day 3: You're defending yourself
on Twitter
The platform made its fee.
You're on your own.
Quorum is built for the founder
who doesn't want that story.
Your token doesn't go live until
the community has had 30 days to
validate it. Your funding doesn't
move until real people with real
wallets decide your project is
worth backing.
If they're right, you graduate.
If they're wrong, they get 99% back.
Either way, no one gets rugged.
Graduation Day on Quorum:
→ $100K+ raised, 1,000+ holders confirmed
→ Vesting lifts for everyone simultaneously
→ Token becomes freely tradeable
→ Liquidity moves to Raydium
→ The 0.1% cap that protected the project
during vesting is no longer needed —
the community is already real,
already large
This is the moment the entire protocol
was built for: a token with actual people
behind it, not a launch that lived for
48 hours and died.
The hard part wasn't getting here.
It was making it impossible to fake
getting here.
Failure on Quorum isn't zero.
99% of contributed capital returns
automatically. But here's what often
gets missed:
The project spent 6-9 months building
a real community. Public validation.
On-chain history. People who showed
up and believed in it.
That doesn't disappear when the funding
target isn't met.
A founder can relaunch with that same
community. Seek private funding with
proof of demand. Or simply know, with
real data, that the idea needs to change.
Failing here still leaves you with more
than most launchpads give you on success.
Here's the detail that surprises
people most.
The dev is not exempt from the
0.1% cap.
Same wallet limit. Same vesting lock.
Same rules as any random holder who
contributed $10.
There is no special "founder allocation"
bypassing the constraint. The program
doesn't even have a code path that
would let it.
If the dev wants more than 0.1%, the
only option is buying it on the open
market — publicly, transparently,
at market price.
That's not a policy. That's the protocol.
"9 months feels long" — fair reaction.
Here's the math behind it.
A dev running a fake-holder attack
(1,000 wallets, self-funded) needs
$100K of real capital locked for the
full vesting period to fake graduation.
At 3 months, that capital cost is low.
The attack is cheap.
At 9 months, that same capital could've
made 2-5x elsewhere in crypto. The
opportunity cost makes the attack
irrational for most bad actors.
The length isn't arbitrary. It's the
point where faking it costs more than
building it for real.
This is just Phase 1.
In 15 days, the economic phase opens.
In 180 days, graduation is possible
if the goals are met.
In 284 days, the protocol auto-fails
and refunds if they're not.
No human intervention at any step.
Quorum is live on devnet.
Mainnet coming soon.
Follow @QuorumBuild for updates.
Every parameter is enforced by code,
not by a team:
→ 0.1% max per holder
→ 1,000 minimum holders to graduate
→ $100,000 minimum raise
→ 9 months bilateral vesting
→ 99% auto-refund if it fails
The dev has the same 0.1% limit
as any random contributor.
What if the dev just... disappears?
Quorum tracks it, automatically:
30 days inactive → public alert shown
on the project page
60 days inactive → dev wallet locked.
Can't claim tokens at vesting end even
if the project later succeeds
90 days inactive → holder vote activates:
continue under community custody, or
trigger early refund
No one has to notice and raise a flag.
The protocol watches the clock for you.
A project fails. What happens to your money?
On most platforms: nothing. You're out
of luck, or you're filing a support ticket
into the void.
On Quorum: the program executes it.
refund() runs the moment the failed state
triggers. 99% of your contribution returns
to your wallet — no request form, no admin
approval, no waiting on a team that may
have already moved on.
The code doesn't need your permission
to do the right thing. It just does it.
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.