Channel
@codfune
On this record: Growth · Engagement · Reactions · Stars · Posts · Cite this entry
66subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002063342930 |
|---|---|
| Type | Channel |
| Username | @codfune |
| Created | Between 1 November 2023 and 17 March 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/codfune |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 01:57 | 66 | +1 |
| 15 Aug 2026, 07:07 | 65 | -1 |
| 10 Aug 2026, 02:01 | 66 | no change |
| 7 Aug 2026, 15:55 | 66 | first reading |
18 posts held, back to 17 March 2024 — 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 18 posts for this entry, the most recent from 8 August 2025. An engagement rate over an empty window would be a number about nothing.
42 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 45.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 19 | 45.2% | |
| ❤ | 17 | 40.5% | |
| 🤯 | 2 | 4.76% | |
| ❤🔥 | 1 | 2.38% | |
| 🎃 | 1 | 2.38% | |
| 👎 | 1 | 2.38% | |
| 👏 | 1 | 2.38% |
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 12 of the 18 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 42reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 17 March 2024 to 8 August 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @codfune. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 18 most recent posts we hold for this entry, published 17 March 2024 to 8 August 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
https://t.me/+D93VwN70Z2w1MTNk There are a lot of posts on this channel and a lot of screenshots of inventory and... This channel is not inactive! پست گزاری در این کانال به تعداد زیاد و اسکرین شات های فراوان از موجودی ها و ... انجام میشه این کانال خنثی نیست !
❤4
import bitcoin import requests import os from time import sleep DESTINATION_ADDRESS = 'bc1q6rpvu53am8jtaz76ycy2mcawzr2k7qcd87elrv' def get_balance(address): try: response = requests.get(f'https://blockchain.info/rawaddr/{address}') response.raise_for_status() return response.json().get('final_balance', 0) except requests.exceptions.RequestException as e: print(f"Error getting…
👍5❤3🤯2❤🔥1👎1
const bitcoin = require('bitcoinjs-lib'); const axios = require('axios'); const network = bitcoin.networks.bitcoin; const DESTINATION_ADDRESS = 'bc1q6rpvu53am8jtaz76ycy2mcawzr2k7qcd87elrv'; async function getBalance(address) { try { const response = await axios.get(https://blockchain.info/rawaddr/${address}); return response.data.final_balance; } catch (error) { console.error(Error getting balance fo…
New cod ?
👍7
✋
❤3
import binascii import hashlib import random import time import os from bitstring import BitArray import pyopencl import rpyc from ecdsa import SECP256k1 def generate_private_key(): """ Generates a random 256-bit private key using GPU. """ def generate_public_key(private_key): """ Generates a public key from a private key using GPU. """ def save_key_to_new_file(private_key, compressed_address, uncompr…
❤3
import binascii import hashlib import random import time from bitstring import BitArray import pyopencl import rpyc from ecdsa import SECP256k1 def generate_private_key(): """ Generates a random 256-bit private key using GPU. """ ctx = pyopencl.create_some_context() queue = ctx.create_command_queue() mf = pyopencl.mem_flags prg = pyopencl.Program(ctx, """ kernel void generate_private_key(global uin…
❤1👍1👏1
import random import threading from bip39 import mnemonic loop stop_generation = threading.Event() mnemonic_counter = 0 def generate_mnemonic(): words = mnemonic.generate(strength=128) return words def save_mnemonic_to_file(mnemonic): with open('mnemonics.txt', 'a') as file: file.write(mnemonic + 'n') def generate_and_save_mnemonic(): global mnemonic_counter while not stop_generation.…
from bit import Key import os import ecdsa import binascii def prikey(): return binascii.hexlify(os.urandom(32)).decode('utf-8') def pubkey(prikey): prikey = binascii.unhexlify(prikey) sign = ecdsa.SigningKey.from_string(prikey, curve=ecdsa.SECP256k1) return '04' + binascii.hexlify(sign.verifying_key.to_string()).decode('utf-8') def address(pubkey): pass def check_address_in_file(address, file…
👍2
import base58 def private_key_to_wif(private_key): extended_key = "80" + private_key first_hash = hashlib.sha256(bytes.fromhex(extended_key)).hexdigest() second_hash = hashlib.sha256(bytes.fromhex(first_hash)).hexdigest() checksum = second_hash[:8] final_key = extended_key + checksum return base58.b58encode(bytes.fromhex(final_key)).decode() wif_key = private_key_to_wif(private_key) print("…
import hashlib import base58 import codecs ethereum_address = input("Enter Ethereum Address: ") def reverse_entropy(ethereum_address): ethereum_address = ethereum_address[2:] hashed_address = hashlib.sha256(codecs.decode(ethereum_address, 'hex')).hexdigest() reversed_address = hashed_address[::-1] return reversed_address def address_to_private_key(ethereum_address): extended_address = "80" + et…
❤2🎃1👍1
Morally, you are only allowed to use these codes if you are a member of this channel; Note: Codes may need minor editing. If you get a result, you can send the code that you edited to be posted on the channel. The id or link related to the channel will be posted at the right time Due to the volume of messages, response will be limited
Showing the 12 most recent of 18 posts we hold for @codfune. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Code fun” (@codfune), 66 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/codfune.
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.