Draft nns proposal: implement a native wallet within the nns for storage, sending and receive of tokens and nfts across various standards on the internet computer

DRAFT NNS PROPOSAL: IMPLEMENT A NATIVE WALLET WITHIN THE NNS FOR STORAGE, SENDING AND RECEIVE OF TOKENS AND NFTS ACROSS VARIOUS STANDARDS ON THE INTERNET COMPUTER.

Proposal Overview:
the development of a basic wallet function that enables users to hold, send, and receive wallets across various token standards on the Internet Computer (IC) within a subset of the NNS. This wallet would not appear on the NNS page, but as a subsection within the NNS. Users would have to import their own canister ids.
This will in our opinion: A) allow users who solely utilize the NNS to interact with projects across the IC B) bring wallet functionality to the NNS that currently users must utilize a number of different services to achieve and C) eliminate the need for every project whom wants to legitimize from pushing superfluous proposal’s to be listed on the NNS.

As the IC ecosystem continues to grow, it is crucial to address the need for a user-friendly wallet function that supports multiple standards, allowing users to manage their digital assets efficiently

We propose the development of a basic wallet function that integrates various wallet standards on the Internet Computer. The key features of this wallet function include:.
Multi-Standard Support:
The wallet will be designed to support multiple wallet standards, such as ICP, ckBTC $ eventually ckEthereum, and others, ensuring compatibility with different tokens and assets. The ic standards that should be available on the nns are: DIP20, EXT, ICRC1 etc.
The most important is that no token on the ic becomes depreciated, this native wallet should mimic those in popular dexs an and enable a user to import a canister id and standard, and the nns should interact with the ledger to call the token. Storage of an imported token can be supplemented by the ability to send and receive, this will bring confidence to user that they can rely on the nns as their main wallet.

Utilizing the NNS as Secure and Private Storage: The Internet Identity and NNS provide a level of security and privacy that is extremely attractive. Allowing users to store, send and receive NFTs and Tokens DIRECTLY with the NNS is extremely attractive to the user base. This additional wallet functionality will not compete with other services, but will allow users to store send and receive tokens and nfts without needing to approve the internet identity to a dapp but rather just with their princple id.

User-Friendly Interface: The wallet function will provide an intuitive and user-friendly interface accessible through web and mobile applications. It will feature a streamlined design that simplifies the process of wallet creation, management, and asset transfers.

Interoperability:
The wallet function will facilitate seamless interoperability between different dApps and protocols within the IC ecosystem. It will support common standards like Internet Identity (II), token standards (dip20, ext, icrc1, icrc2, etc), and interoperability frameworks (like ICP-ETH bridge) to enable easy transfer of assets. With the eventuality of ETHEREUM Integration, this will help new adopters to the ic ecosystem utilize a trusted wallet with their newly minted chain key Ethereum.

CODE: tbd I will post below or maybe an dex would like to donate some wallet code

1 Like

I fully support this idea. It’s something that I have been thinking about since I use IC.
Having a save place to store tokens and NFTs without relying on 3rd party apps would be great.

I would even go beyond that:
It’s always a bit annoying having to log in with a wallet after you already logged in with II to pay for something on Dapps.
It would be cool if we had a chance to create multiple wallets in the NNS that we can use to pay directly.
Inside a Dapp you then just approve a subwallet from the NNS that has your tokens and some “liquid ICP”.

I think this would make alot of Apps less tedious to use and enhances the IC experience for beginners.

To elaborate,
This wallet concept would not entail dao functionality.

Here’s the basic draft of our proposal

TENDY hopes to bridge the gap of “meme tokens” and “utility” tokens by providing liquidity and unique arbitrage opportunities for users of the Internet Computer, Colloquially referred to as the “Tendyverse”.

We (tendy) propose the development of a basic wallet function that integrates various wallet standards on the Internet Computer. The key features of this wallet function include:.

  • Multi-Standard Support: The wallet will be designed to support multiple wallet standards, such as ICP, ckBTC $ eventually ckEthereum, and others, ensuring compatibility with different tokens and assets. The ic standards that should be available on the nns are: DIP20, EXT, ICRC1 etc.
  • The most important is that no token on the ic becomes depreciated, this native wallet should mimic those in popular dexs an and enable a user to import a canister id and standard, and the nns should interact with the ledger to call the token. Storage of an imported token can be supplemented by the ability to send and receive, this will bring confidence to user that they can rely on the nns as their main wallet,
  • User-Friendly Interface: The wallet function will provide an intuitive and user-friendly interface accessible through web and mobile applications. It will feature a streamlined design that simplifies the process of wallet creation, management, and asset transfers.
  • NATURAL EXTENSION OF THE NNS: this wallet should appear in the drop-down menu of the left hand side of the nns, and when it opens mimic same style of user interface for all tokens.
  • Utilizing the NNS as Secure and Private Storage: The Internet Identity and NNS provide a level of security and privacy that is extremely attractive. Allowing users to store, send and receive NFTs and Tokens DIRECTLY with the NNS is extremely attractive to the user base. This additional wallet functionality will not compete with other services, but will allow users to store send and receive tokens and nfts without needing to approve the internet identity to a dapp but rather just with their princple id.
  • Interoperability: The wallet function will facilitate seamless interoperability between different dApps and protocols within the IC ecosystem. It will support common standards like Internet Identity (II), token standards (dip20, ext, icrc1, icrc2, etc), and interoperability frameworks (like ICP-ETH bridge) to enable easy transfer of assets. With the eventuality of ETHEREUM Integration, this will help new adopters to the ic ecosystem utilize a trusted wallet with their newly minted chain key Ethereum

This proposal will enable the native wallet, and $TENDY (canister: 72uqs-pqaaa-aaaak-aes7a-cai standard: DIP20) will be the first token visible.

Below is some information about tendys.

DAPPS & canisters:

Tendy.zone

https://6pquh-zqaaa-aaaap-abgaq-cai.icp0.io (in development)

CURRENT LISTINGS:

$TENDY is listed on ICPSWAP & SONIC swap, with functionality enabled on DSCVR to receive, send and hold.
We are listed on ICPCOINS.com 4 (sns proposal #54)

We are in negotiations with Seachan for a gated board for our token holders.

TENDY team is in close contact with other projects around the internet computer and strives to be available to our users on as many platforms as possible.

Multiple Liquidity Pools:

Tendys will support the creation of multiple liquidity pools to enhance liquidity and facilitate smooth trading experiences for investors. These liquidity pools will be established in collaboration with reputable decentralized exchanges, ensuring a secure and seamless environment for trading Tendys and other compatible cryptocurrencies. These pools also offer users potential arbitrage opportunities, and holding TENDY tokens opens up a world of trading within the Tendyverse.

Burning Liquidity Pool NFTs:

To foster trust and demonstrate our commitment to the community’s well-being, Tendys will adopt a unique approach. The team has blackholed and burned certain liquidity pool NFTs, eliminating the possibility of rug pulls or sudden liquidity drainage. These “burned” lp pools can be viewed here:
t5t44-naaaa-aaaah-qcutq-cai.raw.ic0.app
NFTgeek - Analytics tool for IC NFTs 1
NFT analytics tool. IC NFT minting and transactions data, holders, listings, trends, floor price chart - all in realtime.

The numbers go as follows:
66 ICP / 6930 TENDY
10,000 ICYPEES / 2000 TENDY
1 DKP / 809 TENDY
.00052 ckBTC/ 52 TENDY
Have been locked into liquidity thus far.

This equals slightly more than 10% of all TENDYS in existence being locked into lp.

Community Development and Engagement:

At the core of Tendys’ success lies a strong, engaged community. The dev team is active on Twitter, and the public Telegram: @icTendies Telegram: Contact @icTendies 2

Tendys was born out of the desire to provide a seamless and comprehensive user experience. The development team are not funded by dfinity and have received no grants thus far. All burned lp has been directly out of dev teams pockets.

An example of high quality community produced art is the Tendy song which was created by Nigerian artist stenzory. Despite no promise of rewards, the artist used his own funds, time, and energy to create a beautiful song: Headliner

This nns proposal will benefit the entire IC defi ecosystem.

This will also allow users to import and hold send and receive their own tokens, thus negating the need for every induvidual project to have to go through an nns sale to be held within the nns.

Hi @Newtolearn

I wanted to quickly highlight that there is the Identity and Wallet Standards working group that is currently working on wallet standards.

In particular, there are already two draft standards that together form a coherent, easy to use and interoperable wallet architecture:

  • ICRC-21 which generalizes transaction approval consent messages and specifies the interactions of the wallet with the user.
  • ICRC-25 which specifies the interaction between a dapp and a wallet in order to request transactions from the wallet.

When / if these standards get accepted by the community, they will form the basis of a freely interoperable wallet ecosystem on the IC, allowing much easier asset management and making wallet interactions much easier for developers too (for both dapp and wallet developers).

Both of those standards mentioned above are currently in the process of being finalized.

I invite you to join the working group (next session on September 5) and to provide feedback on these proposed standards.

3 Likes

That sounds great! The beauty of this proposal

(Internet Computer Loading)

Is that it’s a two part plan! This current proposal is just to approve the concept with a motion vote, and holds no code. As standards become finalized, the working group could produce the code that will be eventually pushed to implement the multi standard wallet. I do believe current solutions exist though, as both ICPSWAP and ICDex have native wallets.

You can find my response here: UPCOMING NNS PROPOSAL: list $TENDY in the nns - #11 by sea-snake

TL;DR
I don’t really seem to understand the purpose of this proposal and why it had to be combined with the token listing proposal.

I replied with this:

I appreciate your opinion, but bringing this sort of functionality to the nns seems appropriate. Currently a lot of IC users have various nft and token airdrops that are controlled by their nns wallet ids but cannot be accessed. Also, there are a number of projects whom are pushing nns proposals.

The creation of a token wallet WITHEN the nns will allow users three benefits

*access to all tokens via the security of the nns,

  • older projects do not have to fear depreciation because their tokens can always be held sent and received in the nns
  • when ckETH arrives, this newly created wallet will be a perfect place to store the hundreds of ckALTCOINS that eventually move into the ic

As for the code:
There are a number of available codes that can interact with the ledger and allow users to access tokens they own via canister import. This isn’t reinventing the wheel, but combining services that are already available third party to the nns itself.

As for TENDY:
We are not asking to be implemented within the main nns, just as the first token in a list that will include all the current tokens, and others that users import into a newly created drop-down wallet.

Edit: see my response in above thread.