# Upcoming onicai SNS Decentralization Swap

**URL:** <https://forum.dfinity.org/t/upcoming-onicai-sns-decentralization-swap/61361>\
**Category:** Showcase\
**Tags:** sns, DeAI\
**Created:** [December 11, 2025, 9:58pm UTC](https://forum.dfinity.org/t/upcoming-onicai-sns-decentralization-swap/61361 "2025-12-11T21:58:03Z")\
**Posts on this page:** 1\
**Showing post:** 65

<div class="post-metadata">

**Author:** ![Lorimer](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lorimer/32/17601_2.png) [@Lorimer](https://forum.dfinity.org/u/Lorimer)\
**Post date:** [January 11, 2026, 5:14pm UTC](https://forum.dfinity.org/t/upcoming-onicai-sns-decentralization-swap/61361/65 "2026-01-11T17:14:14Z")

</div>

Created a separate thread about SNS frontend verifiability →

> [@SNS Frontend Verifiability](https://forum.dfinity.org/t/sns-frontend-verifiability/62469):
>
> Can I ask why SNS projects are encouraged to utilise the standard asset canister for hosting the frontend assets? Why are SNSs not encourage to bundle their frontend assets into canister WASM so that the SNS DAO can verify the build before deploying frontend changes? The verification workflow for the standard asset canister (which doesn’t bundle assets in the WASM) is unnecessarily complicated. I don’t think I’ve ever seen an example of this used for SNS communities to verify frontend change…

---

_[View the full topic](https://forum.dfinity.org/t/upcoming-onicai-sns-decentralization-swap/61361)._
