TTC Protocol launches public bug bounty on HackenProof

Hacken Ecosystem
2 Minutes Read

We are proud to announce the launch of a bug bounty program for TTC Protocol.

TTC Protocol is a decentralized and token incentivized social networking protocol that aims to provide a brand new social experience for users all over the world. It is one of the largest social networking ecosystems on the blockchain, with over 23 million users. TTC Protocol provides a simple-to-integrate and fully-customizable blockchain-based SDK for existing communities, which acknowledges users’ contribution to the community and rewards them.

By providing a brand new social experience, TTC Protocol a highly rewarding and dynamic user experience to all participants.

Social network services deal with a massive number of users and their private moments. Hence, it is very natural for TTC Protocol to set “security” as one of the top priorities. TTC Protocol understands that there is no such thing as a perfectly secured environment and constantly challenge themselves to improve its security standard. Hosting a public bug bounty program is a great way to do just that! We are looking forward to spotting and fixing security vulnerabilities of TTC Protocol in order to create a safe and secure environment for everyone.  

TTC Protocol will award hackers up to $5,000 for critical security vulnerabilities. You can read more about the program here

Please join us in welcoming TTC Protocol to the family of public bug bounty programs on the HackenProof platform!

About TTC Protocol:

The TTC Protocol connects every participant in the TTC ecosystem by establishing common guidelines for different DAPPs. TTC is the circulating currency, incentivizing all participants in the ecosystem of the TTC Protocol. Network users on social platforms are rewarded for generating, distributing, and interacting with content, and interacting with other users. The TTC Protocol returns the commercial value in the attention economy to those same users who generated that value. For more information, please visit:

Read more on HackenProof Blog