From the Team

WINk
2 min readDec 2, 2021

--

2nd December 2021

We are happy to have a community that’s involved with our growth and development of WINK over the years and showing support in many ways we can imagine. The furore surrounding our recent 400 million $WIN notice in which the community has been questioning, if it was a mistake made by someone and if we used it as an excuse not to burn, will be addressed.

The 400 million $WIN was transferred by our investment division without our knowledge, assuming that by moving a TRC 20 token to a TRC 10 address will render the tokens out from market circulation. We understand the frustration of the community due to the non-conventional method of removing tokens out of circulation and have escalated the issue. We love our community and want to work hand in hand with you, for you.

We do not share this sort of information but for clarification, we want to point out that we do not benefit from making excuses. Our article on December development and team expansion stands true. To ease everyone’s concerns, we have reached out to the TRON team to recover the 400 million and have conducted a proper burn. This will be for our Q4 2021 burn.

Here is the burn hash:
206ccb0c7e94b70d51d44b6b28e2d08bbaebba843f657dbd3ab99aef2e643f00

WIN burn amount: 400,000,000 WIN

This is us being transparent and we would really like to focus our efforts on bettering our projects. That being said, we do not appreciate the spreading of fear, uncertainty, senseless allegations against the team, and doubt over the team’s dedication to make WINk a success and hope that the community will continue to show its utmost support.

Team WINk

WINk Community Information:

Website: https://www.wink.org
Telegram: https://wnk.to/wink_tg
Twitter: https://wnk.to/tweet
Media and Enquiries: hi@wink.org
YouTube: https://wnk.to/yt

--

--

WINk
WINk

Written by WINk

Worlds greatest gaming DApps; WINk on #Tron. Using blockchain for wealth redistribution is possible by $WIN. Join us on Telegram: http://wnk.to/wink_tg.

No responses yet