Menese’s SNS Bid Makes Source-Code Access the Decentralization Test

Menese Protocol is proposing to turn its cross-chain DeFi application into an Internet Computer Service Nervous System (SNS) DAO. The planned decentralization swap would seek a minimum of 100,000 ICP, a maximum of 500,000 ICP, and at least 200 participants. The team says the funds would support launchpad and exchange listings, marketing, infrastructure, and—at the maximum raise—protocol liquidity rather than salaries.

The announcement presents Menese as a live product rather than a pre-launch experiment. The team says it has 16 production canisters, nearly 1,000 retail users, integrations with three ecosystem projects and an outside enterprise, and a fixed supply of 100 million MENES. It also says existing holders and stakers would carry over one-to-one, with the SNS governing the wallet backend, cross-chain pools, frontend, ledger, sale and staking canister, and treasury.

That proposed control transfer is the important technical and governance story. ICP documentation describes an SNS as the sole controller of an application’s canisters after launch: upgrades and treasury spending become governance proposals, while the NNS must approve the SNS creation proposal. If the swap fails to meet its minimum, contributions are refunded and control returns to the configured fallback controllers.

Menese’s token plan allocates 20 million MENES to the SNS sale, but the team says roughly half would be sold in the swap and roughly half would remain in the genesis treasury for a future exchange listing. It says treasury tokens would carry no voting power and that only staked neurons would vote. These details will matter because the NNS evaluates not only the fundraising target, but also voting power, vesting, treasury control, product evidence, and the proposed roadmap.

The central unresolved issue is verifiability. In the announcement, Menese says it intends to open-source the protocol after the SNS launch, while offering code access to qualified external reviewers before then. The team frames withholding the full codebase as a business-protection measure. By contrast, current ICP developer guidance recommends that source code be open-sourced with reproducible build instructions before the decentralization swap, so participants can verify what they are governing and inspect upgrades before voting.

This creates a clear threshold for the eventual NNS proposal: Menese must demonstrate not only that it has a working cross-chain product, but that the proposed DAO can independently verify and control the software holding user value. The announcement is therefore best read as an intent to enter that review process, not as evidence that the SNS has been approved or launched. Final parameters, the canister list, and verification instructions are still expected with the NNS proposal.

The project’s operational and traction figures remain claims made by Menese in the forum thread and are not independently verified here. The same caution applies to its planned listings, token economics, and stated user and integration numbers. For builders and token holders, the next meaningful artifact is the proposal package: source repositories, reproducible build instructions, configuration, security evidence, and the exact canisters placed under SNS control.