UPCOMING NNS PROPOSAL: list $TENDY in the nns

Governance
1

THE PROPOSAL:

The proposal will include adding the canister ID

72uqs-pqaaa-aaaak-aes7a-cai
DIP20

To the NNS and allowing users to send, receive and hold TENDY Token.

There will be no addition of a DAO or any token sale.

Tendys (canister: 72uqs-pqaaa-aaaak-aes7a-cai standard: DIP20) aims to create an arbitrage ecosystem through the establishment of multiple liquidity pools and the cultivation of a strong, trustworthy community. It is also a chicken tender. Tendys will prioritize transparency, liquidity, and community-driven initiatives to ensure long-term growth and sustainability.

Introduction to Tendy

TENDY is a DIP20 standard token, with a max supply of 88,000. The development team has not yet black-holed the canister as there are improvements and maybe even potential additions of icrc1 functions to the code coming soon.

TENDY TOKEN is designed as a tool to let traders aribitrage through out our token pools.

TENDY is a token designed to provide investors with a seamless, secure, and rewarding experience.
Currently, there are active swap pools with locked liquidity of SNS1, ICYPEES, ckBTC and ICP.
There are user controlled pools of TENDY with CHAT, ICL, SNS1, ICYPEES & ICP, OGY, DKP

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”.

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 (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.

We now also have fledgling liquidity pools on Sonic.ooo

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

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

Token Standards amidst new updates to the IC: Currently $TENDY is a dip20 standard token. We have been in discussion with numerous projects on the ic whom have requested ICRC1/2 interfaces and or functions to be added to the token. Our dev team is working on a solution. There are currently two threads up on this forum where I have posed questions and received some guidance on migrating a DIP20 to ICRC1/2. We may choose to develop a Wrap which one can utilize to bring DIP20 into the icrc1/2 world of functionality. In our opinion it would be a disservice to the IC to deprecate tokens which are not current with the ICRC1 standard. If anybody has any thoughts about this it would be much appreciated.

1 Like
2

We look forward to a lively discussion and will push our proposal in the coming days.

3

Thank you very much for the information, I would like to know more about the utility of the token… I don’t quite understand what utility it is outside of a coin that is in pools… thank you!

5

As for utility of the token itself there is an active staking spool on ICPSWAP (ICPSwap) where you can stake your $TENDYs and earn $SPICY.

Their real utility is the ability to swap for other good IC projects without having to utilize your Icp. Also, because of their low supply and deflationary economics because of the locked liquidity pools, the tendys themselves seem to have a high elasticity with price action in an uptrend.

2 Likes
6

In order to help clarify some things here is our new landing page

https://h4we6-zyaaa-aaaap-qbj7a-cai.icp0.io/

7

I’m bumping this thread because I would like to go live with our proposal soon.

8

We are combining these two proposals

9

Introduction to Tendy & the Peeco system and the implementation of a native token wallet within the nns

TENDY is a DIP20 standard token, with a max supply of 88,000.

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.

10

Proposal is live!

11

I don’t really seem to get the purpose of this proposal.

It’s not a proposal for any feature changes, there’s no code. Neither is it a proposal for any standards to be adopted by developers.

What’s the purpose? A proposal that simply states “X should be build”, doesn’t really mean anything without any clarity of who will be building it and how it should be build, or upon which standards it will be build.

Standards like the ICRC1 and ICRC2 are designed with the community and accepted with proposal as standards for all developers to make things interoperable between different services on the IC.

The proposal seems to expect a wallet to be build that doesn’t only support this standard but also other non standardized standards like EXT, DIP20 etc which goes against the whole idea of standardization by the working groups. On related note, the DIP20 standard was defined by Psychedelic which has left the IC a while back, the standard is no longer maintained. It also has quite a few missing details that won’t be addressed as a result, I don’t see how this standard belongs within the NNS.

I personally spent a lot of time writing interoperability layers between all the different token standards, this is a lot of extra work and hacky at best due to small differences between standards not being compatible with one another.

Also just to be clear, as of this moment there is no official adopted NFT standard yet. This is currently still work in progress within the working groups.

Multiple developers are working on improving existing wallets and creating new wallets while trying to standardize how wallets interact with services in working groups. Additionally tokens are migrating from different standards to the ICRC standards to make things interoperable.

If new standards emerge for the interoperability between wallets and services, those will result in proposals and adoption by the community.

All of these standards will ultimately lead to more functionality within and outside of the NNS built upon these standards but it takes time.

I don’t see how this proposal would make a difference here, it doesn’t change anything for us as dapp developers.

As for listing $Tendy within the NNS, that seems like a complete separate issue that should be it’s own proposal. I don’t really understand why it was combined with this proposal either. Now there’s no way to vote in favor of one thing while voting against the other.

I don’t really understand why an ICRC token can’t be created for $Tendy (and a swap canister for existing dip tokens) and then a proposal made to have it listed within the NNS dapp. This seems like a reasonable thing to build and deploy from developer perspective within a timespan of less than a week, probably days considering an ICRC canister implementation is readily available.

As for listing within the NNS dapp, currently this seems to be limited to DAO tokens since the governance of DAO is the primary purpose of the NNS. I personally don’t think that at this moment, the NNS purpose extends beyond that scope as general token wallet.

Full disclosure: I’m currently developing an open source wallet myself and work on supporting multiple token standards.

2 Likes
12

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.

13

From security perspective delegating the users NNS identity to 3rd party wallets hosted on different canisters seems like a bad idea.

From a developer perspective, adding functionality isn’t as simple as just copying another open source wallet into the NNS codebase. It needs to be adapted, maintained and audited. This goes at the cost of developments and maintenance of core NNS functionality.

If you do want to recover tokens out of your NNS wallet that are built with token standards that aren’t standardized there are other ways to do it besides adding all these standards within the NNS and going around the goals set by working groups to standardize these like we can see already on other blockchains.

But overall, I don’t see how this proposal actually makes anything happen since there aren’t any technical details within the proposal nor does it clearify who is actually supposed to implement it.

If this proposal is asking to spend the ICP fund on development towards wallets and open standards, that’s already happening but takes time.

14

I think you might be missing the point of this proposal. TENDY team is prepared to help generate the code nesscary that will be pushed in the second proposal. This sort of tool needs to be implemented especially if there is any hope on users adopting ckETH. Currently, the ic has the ability to host assets across many standards, and many users have assets linked to their IIs that are unusable. This is a way to expand the growth of the II/NNS without the nns needed to specifically ENDORSE a project. When ckETH etc arrives, it would behoove the ic to allow users to hold harrypotterobamachan tokens within the nns or else where is the appeal to migrate to the network?

15

I would consider voting in favor of a proposal to allow users to manually add additional ICRC1 tokens to their NNS wallet, that seems reasonable to me.

But considering that the NNS isn’t a wallet and there are no official standards yet to connect between wallets and dapps (working groups are working on these). Users can’t do anything with these non DAO tokens, they can’t for example connect the NNS to a dex to trade them. Making wallet functionality within the NNS not that useful.

There is no finalized NFT standard yet either, so I don’t see how that could be added to the NNS yet either. (I can imagine some DAO might want to e.g. airdrop NFTs to token holders).

As for adding other tokens standards that aren’t community standards, as I said earlier it makes no sense to add these.

16

They could send or receive no?

17

As for only icrc1,

What about all the projects and tokens that were built on other standards?
Their must be some mechanism to bring those projects into the “new” ic

18

Yes they could update their token canister to also support ICRC1 or if they can’t update the token canister (e.g. blackholed) they can create a new token canister and a swap canister.