Core developer @ OhShii Labs
A community-governed DAO on the Internet Computer, built on proof of personhood, Sybil resistance, and governance that is expensive to capture.
OhShii started as a launch framework and that is still most of what it does today, but the framework is the foundation, not the goal. The goal is a DAO owned by its community that uses its own governance and treasury to get useful things built on the Internet Computer. Everything below is the machinery for that: a DAO that decides where its own resources go has to be hard to capture first.
OhShii Launcher bootstraps a DAO and the community that governs it. Voting weight is quadratic and capped per identity, behind a proof of personhood gate (World ID, DecideID). Without Sybil resistance, quadratic voting is weaker than linear: an attacker splits one wallet into many and beats the square root.
Contributions stay in escrow for the length of the campaign. If it fails everyone is refunded automatically, and nobody has to decide to pay it back. If it succeeds, control passes to the campaign's own governance canister and OhShii is dropped as a controller. No human step, no way to undo it.
Allocation is capped too, not just influence: how many tokens one identity can take out of a campaign is bounded by tier, set by verification status and OHSHII voting power. More capital raises the ceiling but never removes it, and a wallet that stops voting on ONS proposals drops to a lower one until it votes again. Allocated tokens arrive in a vesting lock that already votes in the campaign DAO while it is still vesting, so governance starts at distribution instead of after it.
The code upgrades by vote. A new version of a DAO's canister is proposed on-chain as a wasm. Before voting, anyone can rebuild it from source and check the hash against what was uploaded, so the vote is cast on verified bytes instead of on a changelog. If it passes, the canister upgrades itself. No admin key, no multisig, no team that can ship an update, nothing to compromise: the only route from source to production runs through a vote. This is how OhShii's own governance works, and how every DAO launched on it works.
Capture resistance. A capital driven takeover always looks the same: acquire decisive voting weight cheaply while the token trades low, then vote the treasury out. The damped voting curve above is the first obstacle. Behind it, thresholds follow a two axis Normal / Critical model, and grandfathering stops a rule change from reaching a vote already in flight. None of it makes a takeover impossible, it makes it slow, expensive and visible.
A token that already exists can become a DAO. No launch required. OhShii deploys a governance canister for it, and from then on the community runs voting, locks and proposals from the interface, with no dependency on OhShii or ONS. Hand your dapp's canisters to it and holders vote on how the dapp evolves. Hand over the ledger, archive and index canisters too and they govern the token itself.
Not a replacement for the SNS, and not a fork of it. OhShii is an independent implementation, written from scratch in Rust. The SNS is DFINITY's own framework and it is genuinely battle tested: years of real launches behind it, NNS-level oversight, and tooling hardened by production use. OhShii is not a lighter SNS. It is a different design with different trade-offs, and the two diverge structurally rather than by configuration.
| SNS | OhShii | |
|---|---|---|
| To start | An NNS neuron, and an NNS proposal where the community votes on your tokenomics and can reject them | No proposal and no external vote on whether a project may proceed; eligibility is objective and enforced in code |
| Canisters deployed | Six, automatically: Governance, Root, Swap, Ledger, Index and Archive | One. A single SONS governance canister per DAO carries proposals, voting, treasury, locks and vesting; the token keeps its own standard ledger and index |
| Canister control | Passes through NNS Root, then SNS Root becomes sole controller | The DAO's governance canister answers to itself |
| Launch | Eleven stages, with minimum participant counts and participation floors to get right the first time | An LGE, refunded automatically if it does not complete |
| Voting | Stake weighted, with dissolve delay and age bonuses, so control tracks tokens closely | Quadratic behind a personhood gate, so influence does not track capital in a straight line |
A project that wants the NNS-backed framework should use the SNS. OhShii exists for smaller projects that want an on-chain DAO without that ceremony.
OhShii Locker handles locking and vesting for ONS, SONS entities, imported DAO governance canisters and third party tokens alike, as a one time unlock on a chosen date or a linear vesting plan. Every operation is immutable and verifiable on chain.
Explorer / Atlas is wallet and token analytics for the IC, and the deliberate exception to everything above. They read the chain through external servers, because doing that indexing inside canisters costs more than a purely statistical tool is worth. So they stay outside the DAO's control, as OhShii community applications rather than DAO ones. They hold no funds and carry no core logic. Custody and governance are on-chain and DAO-governed, statistics are not.
Cross-Chain Gateway brings Bitcoin and Solana into the ICP ecosystem, with no custodians and no traditional bridges. Bitcoin is minted as ckBTC through DFINITY's native chain-key minter and redeemed back to native BTC by burning it.
The Solana side is not ours. Chain-key Solana does not exist natively on the Internet Computer yet, and Solana works here because Menese Protocol built it: their chain-key execution layer signs and broadcasts Solana transactions from an IC subnet, with no off-chain relayers. We integrate their SDK. The hard part is theirs.
Languages
Internet Computer
Stable memory schema evolution and upgrade safety, inter-canister call and commit-point discipline, threshold signature and chain-key integrations, Candid interface evolution.
Governance & anti-abuse design
Proof of personhood gating, Sybil resistant quadratic voting, liquid democracy and vote delegation, capture resistant threshold design, in-canister rate limiting, proof-of-work challenges and cycle-drain defence.
Frontend
Infrastructure & tooling
Cross-chain
One of my GitHub profiles, and the one the OhShii work lives on. The repositories are private, so what shows up publicly is mostly what I file on other people's projects: bug and security reports on public Internet Computer repositories.
My open issues on DFINITY's MULTI/DEX