AIRDROP! Клеймер токенов $PUMP за Scroll Origins NFT + бонус за транзакции в сети Scroll до сентября . Скрипт - https://github.com/ildarzf/ScrollPump_claim
👍2

Channel
@ildar_scripts
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
140subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001513296803 |
|---|---|
| Type | Channel |
| Username | @ildar_scripts |
| Description | Скрипты для упрощения работы Я на гитхабе https://github.com/ildarzf |
| Created | Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ildar_scripts |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 22:17 | 140 | no change |
| 7 Aug 2026, 10:21 | 140 | first reading |
20 posts held, back to 20 July 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 11 September 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
115 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 48.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 56 | 48.7% | |
| ❤ | 39 | 33.9% | |
| 🥰 | 8 | 6.96% | |
| 🔥 | 7 | 6.09% | |
| 🤩 | 3 | 2.61% | |
| 🐳 | 1 | 0.87% | |
| 🤓 | 1 | 0.87% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 115reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 20 July 2023 to 11 September 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
AIRDROP! Клеймер токенов $PUMP за Scroll Origins NFT + бонус за транзакции в сети Scroll до сентября . Скрипт - https://github.com/ildarzf/ScrollPump_claim
👍2
Скрипт по бриджу на Relay.link. github - https://github.com/ildarzf/Relay
❤7
Спасибо за помощь!
❤10
Минтит случайный нфт на каждый аккаунт из списка и заносит в базу как выполненное задание. Набиваем дни и контракты. +24 НФТ +24 Контракта +24 Дня Скрипт: https://github.com/ildarzf/zksync_nft2me_tasks Спасибо каналу Клондайк 📓 BLOCKNOTE за список фри НТФ
❤13🔥1
Внес обновления в скрипт . Добавил сеть фантом. Немного контрактов важных для меня (Stargate бридж уж очень много апрувов. Проверьте свои ) и намного больше рандомизации (порядок сетей, контрактов, токенов)
❤3
Так часто начали ломать протоколы. Пришлось искать решение по массовому снятию апрува с контрактов в разных сетях (Ethereum, Bsc, Avalanche, Polygon, Arbitrum, Optimism, zkSync, Scroll, Base) Форкнул скрипт от vladweat. Добавлена рандомизация, задержки исполнения, контроль газа и несколько сетей. Фиксы по коду . Скрипт тут - github.
🥰8
Снимаем защиту sheild c Argent X в случае утери доступа к почте. 1. Переходим на сайт https://starkscan.co/. 2. В строке поиска вводим адрес кошелька. 3. Переходим в раздел Read/Write Contract. 4. На вкладке Write и конектим Argent X с которого нужно снять sheild. 5. В списке ниже ищем функцию trigger_Escape_Guardian. 6. Вводим в поле значение 0 в параметр new_guardian: core::felt252 field. 7. Жмем кнопку Write и п…
👍6
Скрипт для проверки запроса на отзыв 2Fa c кошельков Braavos и Argent X. Буду запускать каждый день до дропа. Подробное описание на Гитхабе
👍5
Как поменять приватник в Braavos Продолжаем изучать невероятные возможности абстракции аккаунтов в Старкнете. Статья о новых способах защиты и скама аккаунтов Braavos. По ссылке технические детали и небольшое расследование угона аккаунтов. Плез, если будите шарить пост, шарьте пост в телеге, а не ссылку на телеграф, очень хочу набрать 1000 сабов к новому году 🤩 https://telegra.ph/Kak-pomenyat-privatnik-v-Braavos…
👍7
https://teletype.in/@ildar_abiy/starknet_sliv
👍6
ФОРК скрипта по zksync Era от https://t.me/sybilwave Добавил анализ выполнения задач. Создается база данных SQL в которую сохраняются все ключи из файла accounts.txt и описания выполненных заданий. Набираем легко количество активных дней Логика. Один запуск (запускаем main_tasks_zksync.py) одно случайное задание для каждого кошелька (список заданий в редактируем в файле main_tasks_zksync.py). Успешно завершенная зад…
🤩3👍2
Обновил скрипт - https://github.com/ildarzf/starknet Добавил модули взаимодействия с контрактами Unframed, Flex и StarkStars NFT
👍7
Showing the 12 most recent of 20 posts we hold for @ildar_scripts. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Scripts from ILDAR ABIY” (@ildar_scripts), 140 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ildar_scripts.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.