We need a performer with experience working with the Twitter(X) API. We have paid for the Basic plan.
Quick execution, the performer must be constantly in touch during the work.
Task (the logic of work is described as if it were done manually)
1. Our bot receives the token address from 3 sources in TG. A message comes to our bot, from which the token address is extracted from the text. (it is also possible to manually add the token address for tracking. a screenshot is added showing how this stage should look in the bot)
For example, we received the address DD5FhLwDArfzbLdfXhGoRbAHpaQZRnkvp5msuxGhpump
Next, we go to search on Twitter https://x.com/search?q=token_address&src=typed_query&f=live
If there are 10 (this can be changed in the settings. by default, it is 10) unique (unique means one message is counted from one user, if one user wrote 5 messages with the search address, we count only 1) or more messages with this address in the search - we send a message to our TG in the following format
=============
Token address DD5FhLwDArfzbLdfXhGoRbAHpaQZRnkvp5msuxGhpump (given as an example)
https://x.com/search?q=token_address&src=typed_query&f=live
https://dexscreener.com/solana/token_address
https://bullx.io/terminal?chainId=1399811149&address=token_address
Number of messages: ___ (number of unique messages at the time of checking).
User nicknames who wrote about this token in x: nick1, nick2 etc.
===========
Then we automatically remove this address from monitoring.
If the search gives us less than 10 messages for this address, we return this address to the table (database) and return to check in 5 minutes. If after 5 minutes the number of messages in the search results has not changed - we return this address to the table and will check again but already after 10 minutes. If we checked the address a second time and the number of messages increased but still did not reach 10 - we return this address to the table and return to search in 5 minutes.
Every 5 minutes we check Twitter for the necessary address. When this address collects 10 messages, we stop monitoring it.
During the day, 250-500 addresses will be monitored online. The bot works 24/7.
We need to create a blacklist where we will manually add token addresses that should not be tracked anymore (this is to prevent a large number of tracking requests from accumulating over 2-3 days).
The bot has the ability to call the entire list of tokens added to the table with the command /listtokens
In the bot, tokens can be deleted from the table with the command /blacklist + token address.
In the settings, we can change 1) the number of messages for checking (by default it is set to 10). 2) the interval between checks (by default it is set to 5 minutes). 3) the result does not change for (by default it is set to 10 minutes)
We have a limit of 10,000 requests per month in our plan on X. If we reach this limit - the bot must inform us that we need to renew the payment for the plan.
We already have a bot template (which is already installed on our service) - we will provide a link to the bot for testing
This task was done - https://freelancehunt.com/project/monitoring-poshuku-twitter-x-kozhni-hv/1402238.html
but unfortunately the performer could not finish it. There was a problem with collecting 10 unique messages.
You can either finish this bot or write your own from scratch, whichever is more convenient for the performer.
The work will be considered completed after the installation (configuration) of the bot on our server and our verification of its functionality.
