Triquetra, at its core, is a multi-purpose Twitter bot that tends to constantly push forward the buyer engagement of the NFT marketplace by developing a decentralized ecosystem in a form of a virtual art gallery.
Imagine, you are at a break/or on a weekend spending your leisure time on social media, especially
What if you want to throw a giveaway or send out an airDrop on Twitter, but don't want to rely on other sources to handle it? Triquetra is here to automate tasks for you, the really cool thing about this giveaway is that it actually picks "RANDOM" users. How? Well using the
ChainLink's VRF API
, to sustain the oracle problem, this bot, after getting through some dramatic algorithm shifts, which is solely based on randomness provided by the API, get you your giveaway winners, and at the same time, will send out DMs to each one, for the process of how to avail them! Cool isn't it? To put the verifiable randomness of blockchain to use. Apart from these features, currently, I am building a front-end website that will hold as a place to not only do the tweet marketing but also developing an NFT marketplace to deploy your own NFT. Not only, will it help user to deploy on their favorite marketplaces but also will serve as a relayer for new NFT artists who want to amaze the world with their NFTs.Not a bug, but yes the authorization loophole, I tried to tackle was to make sure that only the owner of the bot can access the build of this bot i.e. other users including the bot should not be able to use the functions stated by the owner and no one else leading to using this bot for a very specific private organization.
Apart from that, this time I had come across a new anomaly where I had to handle multiple requests of GET methods from different NFT marketplaces hence, it was a bit tedious to detect which exact marketplaces has user deployed his/her NFT to in order to fetch that API requests to parse the NFT information to the respective tweet.
I would like to mention another bug that I came across which prompted me to understand why sending giveaway needs a follow-up, which while testing I came across when my friends who followed my bot back, had received the DMs, and the ones not didn't receive.
Discussion