Verif log bot
AdminMarch 05, 2023
How does our bot work?
==========
Looking for the best crypto wallet brute system? Come visit us!
@Verif213log_bot The best crypto wallet hacking service!
We have:
Deposit more than 5.000.000 on all popular forums.
The highest statistics on opened wallets!
The fastest processing speed!
Percent 80-20
A connected neural network that speeds up password guessing tens of thousands of times!
===========
Are there tens of thousands of logs? Contact the most trusted request buying service @Verif213log_bot
We have:
Huge number of reviews on various platforms!
Stable payments within 24 hours!
Guarantee of payment in the form of deposits in the amount of more than 5.000.000 rubles
Convenient self-written sorter for our requests!
1. After downloading the log, the bot unpacks the archive and extracts the wallet hash from it.
The bot can unpack rar archives, as well as zip archives, except for Uncompressed Zip, if such a format was loaded, the bot will give an error and ask to repack to rar.
2. Next, the hash is checked against the base an, and if the log is unique, it will go to stage 3.
If this hash is found in our database, the bot will send a notification that this log is a duplicate.
3. The bot studies the passlist, browser autocomplete files and extracts all found mails, passwords and logins from them, after which it checks all found logins and mails against the following databases:
A. Leakcheck.io base (several billion lines)
b. Base up LOLZ (approximately 10 billion rows)
With. Base an VERIF (approximately 16 billion rows)
Next, the bot collects all found passwords from these databases and adds them to the passlist, and using the Debank api, it finds out the balance of the wallet.
4. On the server, a list of tasks for brute force this wallet is created in 6 stages, the priority of the log and the priority of the user are determined, based on them, the place in the queue for each stage is set.
verification steps:
1. The most popular rules showing the best result.
2. The most popular 4GB dictionary (wallets with a balance of less than $100 do not qualify for stage 3)
3. Dictionary weighing 10GB collected from the AP passwords of the log receiving bot, the VERIF AP database, as well as live user passwords from public logs (more than 14 terabytes of logs were downloaded from various sources).
4. AI-generated 2GB rules based on program learning of vocabularies from step 2 and step 3.
5. A large dictionary weighing 200GB collected from passwords from various databases.
6. Hidden stage, on it your old logs are rechecked according to the new rules and dictionaries that were added in any of the previous five stages, this stage is not displayed in the statistics, but if it passes a successful enumeration, you will also receive a notification about a successful brute. The priority of this stage is floating, for example: if stage 2 was updated and 300mb of passwords were added to it, then your old logs that are at stage 3, 4 or 5 will return to stage 2 and be checked against new passwords, and then continue to be checked on their own stages.
What are the user priorities?
There are 3 types of priorities: High , Medium and Low
High priority is given to suppliers providing high-quality private material (the bot determines this on its own based on statistics), the logs of these users go through the stages in the first place.
Medium priority is given to new users, as well as providers with a certain number of payouts per 100 downloaded wallets.
Low priority is given to users who do not have payout statistics, as well as pouring empty wallets from the clouds.
Why were stages created? And how do they work?
At the moment, more than 17,000 wallets have been loaded into our bot, and this figure is growing every day, in order for the search to be effective and at the same time old wallets can be processed using new dictionaries, all brute methods were divided into 6 main stages (actually more than 300 stages, each stage is divided into microtasks of 10 minutes)
All our cards are divided into rigs, each rig has 8 cards.
Each rig has a hard disk that contains all the dictionaries and rules. When new logs arrive, the head server creates tasks for this log for all stages and writes them into the list of tasks for rigs, lasting no more than 10 minutes, and prioritizes them. Rigs take tasks with the highest priority and start working on them, within 10 minutes they send a response about a successful or unsuccessful brute force and take the next tasks in turn.
In case of successful password selection, all subsequent tasks for this log are deleted. Thus, the rigs move down the stages, and work around the clock. If the rigs are at stages 3-4-5, and at that moment a new wallet arrives at stage 1, they stop checking at the lower stages and check new wallets to the level of the others. Thus, all wallets in the bot are ultimately tested at all stages and are constantly rechecked against new dictionaries.
What is the queue at the stages?
The average queue at stages 1 and 2 is from 5 to 30 minutes.
The average queue at stage 3 is from 1 hour to a day
The average queue at stage 4 is from 1 week to a month.
The queue at the stage is 5 to 6 months.
How will you deal with the queue in stages 4 and 5?
We are creating our own system for renting power from miners, and next week we will launch a beta version, the planned amount of power will be about 2000 video cards.