Why OhShii

Most token launches ask their community for the same thing: trust the founder. Trust that they won’t change the rules, drain the pool, or disappear. OhShii is built on a different premise — that a community shouldn’t have to take any of that on faith.

OhShii Launcher turns a token into a community-governed DAO from day zero, and steps out of the way once the launch is done. Everything that matters — the ledger, the treasury, the liquidity pool, the right to upgrade the code — ends up controlled by token holders, not by us. And you don’t have to take our word for that either: it’s verifiable on-chain.

Start here, then dive into the Overview for how it works, or the developer docs for the mechanics.

The problem with launching alone

When a project launches a token by itself, one team usually holds the keys: they control the ledger, the treasury, the upgrade authority, and the liquidity. The token’s holders are then dependent on that team’s ongoing effort and good behaviour — to keep the lights on, to not rug, to honour what they promised.

That dependency is exactly what makes serious participants hesitant. It’s not that founders are untrustworthy; it’s that having to trust them at all is the weak point. Remove the dependency and you remove the fear.

What about a managed launch service?

The common middle option is a turnkey launch service — don’t go it alone, let a tool deploy and run everything for you. But “handles everything” resolves to one of two end states, and the weak point above (having to trust someone) shapes both. Either the service keeps the controllers after the sale — in which case the dependency wasn’t removed, it just moved from you to the operator, and the question that cuts through any pitch is after launch, who holds the controllers? Or the canisters are made immutable — which some communities genuinely prefer, because no operator can ever change anything; but that same freeze also locks out you and the community, so a launch-day bug is permanent and the DAO can never evolve or correct it. OhShii is a third path between the two: at completion control transfers to the community (OhShii is removed from the controllers — verifiable on-chain) and upgrade authority is held by the DAO, so changes stay possible but only by community vote — neither an operator backdoor nor a frozen, un-fixable contract. (“Handles everything” usually means deployment; OhShii also ships the protection a bare launch tends to skip — refund-on-failure, a real governance layer, elevated thresholds with an overridable guardian veto, DAO-governed vesting, and controller/treasury safety routing — see Governance & Capture Resistance and Voting.)

Decentralization from day zero

Every OhShii campaign is born with its own governance canister. The treasury, proposals, and voting are powered by the campaign token from the very first moment — not bolted on later.

When a launch completes, finalization removes OhShii from the campaign’s controllers. From that point:

The governance canister controls itself, and holds upgrade authority over the token ledger and index.
The liquidity position is transferred to the governance canister — the community owns it.
OhShii cannot modify, upgrade, pause, or interfere with the DAO. There is no central operator with a back door.

This is the difference between being told a project is decentralized and decentralization that actually happened.

Don’t trust — verify

The authoritative description of OhShii is the code and the reproducible WASM hash of the deployed canisters, not these docs. Anyone can check that the deployed governance canister matches the published source, and anyone can read a campaign’s controllers on-chain to confirm that OhShii has stepped back. The autonomy isn’t a marketing claim — it’s a fact you can independently confirm.

What the community gets

Real autonomy at completion. Token holders govern the treasury, the pool, and the code through proposals. No one else does.
A voice from day one — even while your tokens vest. Every OhShii launch vests both creator and contributor allocations through the campaign’s own DAO (there’s no instant dump, and not even OhShii can touch a completed campaign’s vesting). And vesting here isn’t a silent waiting period: because voting power comes from locks, your activated vesting allocation gives you a say in the DAO from the moment the launch completes — you help govern from the start, instead of waiting for your tokens to unlock before you get a vote.
Quadratic voting, paired with human identity. Voting power grows with the square root of locked tokens times lock duration, and is capped per identity — so influence can’t simply be bought in a straight line. Crucially, voting is gated behind proof-of-personhood (World ID or DecideID), so that quadratic curve can’t be gamed by splitting one wallet into many.
Guardian protection and high thresholds. Sensitive actions face elevated quorum, supermajority, and minimum-voter requirements, with a guardian veto and a hard-to-reach override — designed so that no single party can quietly push something through.
Refund protection. If a launch doesn’t complete, contributed ICP is returned from the campaign’s held sub-accounts rather than released to anyone.

What founders get

You get a full DAO stack instantly, without building governance, a ledger, an index, and pool integration yourself — and without keeping the keys to all of it. You can launch a new token through an LGE, deploy a standalone token for any dapp, or import an already-deployed token and give it governance without a new sale.

And because the decentralization is genuine and verifiable, you attract the participants who normally stay away — the ones who’ve been rugged before and now check the controllers before they contribute. Handing real ownership to your community isn’t a cost here; it’s the thing that makes people trust the launch.

OhShii also ships a built-in lock layer. Locking through the OhShii Locker turns a holder’s commitment into two ready-made, publicly-queryable signals at once: Voting Power for governance, and Lock Points — a simple amount-×-time score that is not voting power and that OhShii itself gates nothing on. Any dapp can read Lock Points to run its own loyalty or lock-incentive program — membership tiers, beta access, feature gating — without building lock infrastructure of its own, and projects can layer their own custom point formulas on top. It’s an engagement signal, not a yield: when you unlock you get back exactly the tokens you locked. Shipping governance power and a dapp-readable lock metric from a single primitive is something OhShii gives you out of the box today.

OhShii and SNS

OhShii and the SNS (Service Nervous System) solve the same problem — turning a token into a community-governed DAO — with different trade-offs.

SNS is DFINITY’s standard framework, and its strengths are real: native integration with the NNS, battle-tested tooling, NNS-level oversight, and a dissolve-delay model that rewards long-term commitment. If you want the most established, NNS-backed path, SNS is a strong choice and we’d point you to it.

Not every project needs that full framework. For a team that wants a real on-chain DAO with less ceremony and less to configure, OhShii is a leaner route to the same destination — and one where resistance to a hostile takeover is on by default, baked into the design rather than a set of parameters you have to tune exactly right.

OhShii makes different choices, optimized specifically for resistance to governance capture:

Voting power that isn’t linear in stake. In a stake-weighted system, accumulating tokens accumulates control roughly proportionally. OhShii dampens that with quadratic voting and a per-identity cap, breaking the simple “buy enough to win every vote” path on several axes at once.
Proof-of-personhood at the voting gate. Identity verification is what makes quadratic voting actually whale-resistant rather than Sybil-farmable — the two features only work as a pair, and OhShii ships both.
Layered guardian and threshold defenses against rushed or hostile proposals.
Autonomy from day zero, without a separate decentralization-sale process to reach it.

Why this matters: a capital-driven takeover always needs the same two things — voting weight that is cheap, and weight it can acquire fast (usually when the token is trading low). OhShii’s design removes both. The per-identity cap and the square-root curve mean a big bag buys far less than its size, under a ceiling no bankroll clears — so the weight isn’t cheap; and voting power is earned by locking for time, so decisive control can’t be assembled on short notice — so it isn’t fast. Because these live in the design rather than in thresholds an operator can lower, that protection is the default here, not a parameter someone has to set correctly.

A note on honesty: none of this makes a takeover impossible. What it does is raise the cost and remove the easiest route. We’d rather tell you that plainly than overclaim. For the full mechanics — voting power, the Normal/Critical model, guardian veto and override — see Voting and ONS vs SONS; for the capture-resistance design analyzed end to end, see Governance & Capture Resistance.

Start here

Overview — what OhShii is and how a launch works, in plain language.
Voting — how voting power and verification work for you.
For Developers — architecture, governance, and the full technical docs.