The problem Cleopatra solves

Cleopatra, at its core, is a multi-purpose Twitter bot that can constantly push forward the user engagement of a decentralized ecosystem.

Imagine, you are at a break/or on a weekend spending your leisure time on social media, especially

Twitter

, looking for some trends and good times, and suddenly you recall, you forgot to check the

CoinMarketCap

of your crypto and don't want to grab or your laptop or go to the website! Cleopatra to the rescue. All you have to do is mention the bot and ask for the price feed change, it will grab the tweet spontaneously and use a DApp to fetch the latest price feed, in this case, ChainLink API.

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? Cleopatra 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, the bot is also designed to provide all these details apart from normal chatting exclusively via DMs, just in case you don't want to let the world know you hold XYZ crypto. My goal here is to provide a reliable, interactive, user-friendly space to communicate with a decentralized world. My future plan here is to actually include more features such that be it

MATIC

or

LINK

token, it is available and open to almost all the cryptos and even beyond.

Challenges I ran into

1. It is actually my first ever attempt to create a bot service, so the very first challenge I faced was to understand and get some hands-on experiences before building the project.
2. Next Challenge was to integrate the ChainLink APIs which still was comparatively an easier portion to get through whereas the same cannot be said for parsing the price feed deployment process of DApp on the test net.
3. Finally the last but not least challenge I ran into was to find a tangible way to put the VRF concept to a use case, and that's when I came across this giveaway idea to implement.

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