Introducing DaoDex: The Governance-Based Token Fair Launch Protocol

Developers Showcase
1

Memecoins were built primarily around speculation. Their value often depended on attention, hype, and the hope that someone else would buy later—not on productive assets, useful products, or meaningful participation.

DaoDex introduces a different model.

DaoDex is a governance-based token fair launch protocol for DAOs building real products and creating real value.

When users support a DAO through DaoDex, they do not simply receive another speculative token. Their allocation begins as a governance stake, giving them a role in the organization behind the token.

Stakeholders can participate in decisions involving:

  • DAO treasury spending
  • Product and operational development
  • Governance parameters
  • Capital raises and token issuance
  • Application-canister control
  • Leadership and recurring payments
  • Other proposals submitted to the DAO

A successful launch provisions dedicated governance, token-ledger, forum, and exchange infrastructure for the DAO. The project’s linked application canisters are transferred to governance, connecting the token to the product and organization it represents.

This is the evolution DaoDex is working toward:

From speculation to participation.
From token holders to governance stakeholders.
From memecoins to DAOs building real-value products.

The memecoin era showed how quickly communities can form around tokens. DaoDex gives those communities the infrastructure to fund, govern, and grow something meaningful together.

Explore DaoDex:
https://daodex.io

Read the whitepaper:
https://daodex.io/whitepaper.html

2

It’s a do that’s inside a dao to build dao Brilliant Mortimer.

3

im thinking of making a dexdao

or a daosns? or a snsdexdao?

4

Congrats on shipping this. I read the whitepaper properly before replying, and it’s a more careful document than most launches get; the limitations section in particular is more honest than what usually appears at this stage.

You messaged me a few months back asking whether there was a way to contribute to OhShii, and I told you the contributor path would open once we moved to a DAO structure. You went and built your own instead. That was the better instinct.

There’s real convergence between the two approaches: per-project isolated canisters, governance stake before liquidity, treasury custody over founder custody, and square-root voting on both sides. There are a few places where we made different calls, though.

For refunds, on OhShii, if an LGE doesn’t reach its target, refunds are contract-enforced. Reading §4.2, yours routes to PreLaunch and the founder chooses whether to accept an underfunded raise or refund. That puts a discretionary step between a failed raise and the contributor’s capital.

The same applies to wallet caps. Yours are optional and founder-configured, and §8.5 is upfront that they’re disclosures rather than protocol-level concentration guarantees. Ours are enforced directly by the protocol.

Sybil resistance is the one I’d flag most strongly, and only because we hit this problem ourselves. Square-root voting is only concave if identities are scarce. Split a position across N principals and N·sqrt(s/N) = sqrt(N·s). Splitting doesn’t just evade the curve, it turns it superlinear, so the mechanism ends up penalizing exactly the holders who don’t bother splitting. §8.5 acknowledges that II doesn’t give you one-human-one-account. We spent months working through this before landing on something workable, and I’d genuinely rather you not have to repeat that search.

We also made a different choice around time as a governance input. Your ladder matures globally from governance creation and is the same for every holder. Ours multiplies stake by lock duration, so voting power is tied to commitment rather than being determined only by size.

And then there’s the protocol layer itself. Your whitepaper does a good job documenting the controller topology for every launched DAO, but it doesn’t state who controls daospot_backend. That’s one of the reasons we chose to put the protocol layer itself under a DAO.

The VWAP-based secondary pricing and the replay-protection work are good additions as well.

Happy to compare notes properly. I’ll follow up privately with a couple of things that don’t really belong in a launch thread.

5

Thank you for taking your time to Note few Issues in the protocol design.

  1. I had DaoDex before we met, i felt yours will be better so wanted to help out. If you notices its previous name was “daospot”

I am the Sole Controller of daospot_backend. Its a Factory, it have no direct or indirect control over any DAO.

As soon as it provisions a DAO it removes itself from the controller list

I will push the source code to open source, so communities can see and audit the code.

The Only Way to stop sybil is by getting involve with Government Documents. ID, Driver’s License.

Which will complicate Data Protection Laws.

For now i just want to keep things simple

@Ravenith