A short update on the SNS for Sonic

I’ll suggest again that a much better path to the NNS would be requiring teams to deploy these on application subnets and control them before being approved by the SNS. That way the token is operational and teams can set them up as desired. Once they want to do a decentralization sale, the NNS can check that they are using vetted wasms and have submitted control to the SNS system.

This would also give the teams some chance to demonstrate how they run a dao and what the community can expect of them.

If the sale fails then control can return to the team.

How can we build vetted tokenomics worthy of community fund investment if your token isn’t generated until the sale where people are supposed to invest in demonstrated value?

Perhaps I’m missing something in how it works…perhaps you can already bring your own token…but it seems that generating a token for swap is part of the current process.


Many thanks for your feedback, @skilesare! I completely agree that the Internet Computer should provide various methods for launching a DAO. That is why I was thrilled when CigDao was introduced as an alternative community driven DAO framework at the last Global R&D event.

Your suggested path, that is, to first launch and then raise funds, is definitely a viable option.

The design intent behind combining the launch and token swap within the SNS framework was to ensure decentralization of the DAO from the start where the launch decision is triggered by another DAO, the NNS. From my perspective, this is an equally valid approach.

I hope we can see different DAO frameworks coexisting on the IC, each one tailored to a specific use case.


For sure…and I know SNS is meant to evolve. Having the conversation for a cig or axon to SNS jump may be worth having so the tech is ready when that situation occurs.

1 Like

Very interesting thread, and in short it seems the traditional SNS approach is too complex, and too expensive for a small firm or startup with limited funds.

Question to those reading this thread, who has not used the SNS and raised funds for an Internet Computer project?

I do remember the folks at TAGGR had something built in-house, who else has gone this route, and what were the results? I think we would all like to know real stories from real teams.

I have not built a project on ICP (yet), raised funds, tried to get a grant, or tried to do an SNS sale. With that said, I’m guessing if a small project came along that:

  • Has consistent team of developers working on the project from the beginning.
  • Has a strong online presence across social media channels.
  • Has a strong and active community who was constantly engaged in the project and was engaged by team members.
  • Has vetted team members with a proven history through education, development, or work experience.
  • Has been open source from the start.
  • Wasn’t asking for more than 10%-20% from the community fund.
  • Wasn’t looking to manage user funds.

It probably won’t be THAT difficult to convince the community to approve the SNS without an audit. That’s strictly my opinion and a guess.

But, if you’re going to be handling user funds potentially in the multi-million dollar range, change the majority of the core development team a few months prior, only open source when the community pushes for it, are in the middle of changing the core architecture of your product, etc., then the community is probably going to be a little more demanding and critical when looking to approve an SNS. Obviously I can’t speak for everyone in this community, but that’s the feeling I get the more I hang around.


I would like to emphasize that the necessity and depth of a security audit can significantly vary based on the type of dapp. For instance, in the case of a DEX, potential bugs can directly affect financial transactions, necessitating a thorough level of scrutiny. On the other hand, for example a dapp hosting a blog, which has lower financial risk, might not require such intense examination.

1 Like