BTC — ETH — ICP — SOL — LIVE · updates every 60s
LedgerLifeICP · BITCOIN · DEFI · WEB3
← LedgerLife Canister Lab

Menese opens private payment tools to developers with ICP integration

By Maria Irene · 2 Nov 2026

Menese Protocol is making its privacy-focused payment technology available to developers, allowing applications to integrate private balances and payments through a software development kit (SDK).

The project says developers can add the functionality using a few lines of code, giving users the option to hold balances and make payments without exposing transaction details through publicly viewable blockchain records.

The announcement comes as concerns over financial privacy continue to feature in discussions about blockchain adoption. While public blockchains offer transparent transaction records, this visibility can also allow people to trace wallet activity, examine balances and follow the movement of funds between addresses.

Menese aims to address this through its privacy infrastructure, with Private ICP already live on the Internet Computer (ICP) network.

According to the project, its system allows users to move ICP into a private balance and make transfers without publicly revealing the transaction amount, sender or recipient. Its developer documentation describes a system in which cryptographic proofs are generated in the user’s browser and verified on-chain.

The Menese Privacy SDK is designed to help developers incorporate these functions into existing applications, including private payment and checkout options.

The project has also indicated that private Bitcoin (BTC) and USD Coin (USDC) support is planned, although launch dates have not been announced.

Menese has made its code publicly available on GitHub and included an AI skill file to assist developers using AI coding tools to integrate the technology.

The initiative highlights a growing area of blockchain development focused on balancing transaction verification with financial privacy. However, the practical level of privacy and security depends on the underlying implementation, and developers and users will need to assess the technical documentation before adopting the system.