I tried to kick out "User" Filip Pavletic, but is not in the group any more (has left the group or has been kicked out by an Admin).
Signed The Join Captcha Bot

Channel
@BitCoinDatabaseOwnership
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
5subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001319419102 |
|---|---|
| Type | Channel |
| Username | @BitCoinDatabaseOwnership |
| Description | BitCoin database ownership https://t.me/BitCoinDatabaseOwnership BitCoin Issuier https://t.me/+Nenfav_eBLU2MWM0 21 Millions Coins News https://t.me/+wD7NFtOKHE5mZDE0 Bitcoin File Format https://t.me/+EcfT8AJX6wJiMmZk |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BitCoinDatabaseOwnership |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 23:48 | 5 | no change |
| 6 Aug 2026, 23:51 | 5 | first reading |
20 posts held, back to 6 October 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 20 posts for this entry, the most recent from 9 April 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
I tried to kick out "User" Filip Pavletic, but is not in the group any more (has left the group or has been kicked out by an Admin).
Signed The Join Captcha Bot
The user @xtrrz failed to resolve the captcha. The "user" was kicked out.
Signed The Join Captcha Bot
The user @EvaR1984 failed to resolve the captcha. The "user" was kicked out.
Signed The Join Captcha Bot
I tried to kick out "User" @emptycup00, but is not in the group any more (has left the group or has been kicked out by an Admin).
Signed The Join Captcha Bot
The user @BlockchainProof failed to resolve the captcha. The "user" was kicked out.
Signed The Join Captcha Bot
Photo, posted without a caption
Signed Ramon Quesada.🇻🇪
La intransferibilidad de los derechos de los mineros se basa en el principio de que los primeros mineros, incluido el Dr. Wright, obtuvieron derechos estrictamente vinculados a su participación en la expansión de la base de datos de Bitcoin, sin obtener la propiedad o el control sobre ella. Los derechos de los mineros se limitan a su papel operativo dentro del protocolo original de Nakamoto, lo que significa que no p…
Signed Ramon Quesada.🇻🇪
Si bien el código abierto permite contribuciones y adaptaciones, no permite que una parte altere unilateralmente la naturaleza fundamental del sistema y aún así afirme que es el mismo. La esencia del sistema, su inmutabilidad, fue una parte integral de la oferta pública realizada por Satoshi. Como tal, aquellos que buscan modificar el protocolo de Bitcoin sin adherirse al diseño original están actuando fuera de sus …
Signed Ramon Quesada.🇻🇪
Aunque mis particularidades en 245 pueden parecer a algunos un tecnicismo, la distinción entre la propiedad original de los derechos de la base de datos y los derechos derivados en curso que poseen quienes continúan invirtiendo en el mantenimiento y desarrollo de esa base de datos es legal y fundamentalmente significativa. En el caso de Bitcoin, esta distinción no solo es relevante sino intrínseca a su diseño mismo.…
Signed Ramon Quesada.🇻🇪
Todos aquellos que apoyan y amplían la versión original de Bitcoin poseen derechos de base de datos. Los mineros originales de Bitcoin poseen derechos de base de datos porque contribuyeron directamente a la creación y extensión de la cadena de bloques de Bitcoin. Para entender esto, necesitamos desglosar cómo la ley del Reino Unido maneja los derechos de base de datos y cómo esos mineros encajan en ella. En el Rei…
Signed Ramon Quesada.🇻🇪
BitCoin database ownership https://t.me/BitCoinDatabaseOwnership BitCoin Software Code https://t.me/+U7htXfOtrEBhMWFk BitCoin Issuier https://t.me/+Nenfav_eBLU2MWM0 Bitcoin File Format https://t.me/+EcfT8AJX6wJiMmZk BerkeleyDB to LevelDB https://t.me/+65VZoVIwACIwYzg0 CSW 131 Opcodes https://t.me/joinchat/a6oPQQ6qmEAyYjhk CSW UTXO https://t.me/+-UBmvY_rrtMxN2Jk UTXO transaction model https://t.me/+Lry65d2OuFo4…
Signed Ramon Quesada.🇻🇪
Grupo de canales de Telegram: BitCoin History (por años) https://t.me/TheBitcoinHistory Ingredientes invisibles en Bitcoin https://t.me/BitcoinIngredientes BitCoin database ownership https://t.me/BitCoinDatabaseOwnership Los mitos de BTC / BTC Myth https://t.me/BitcoinMyths https://t.me/c/2390601295/94 Minería https://t.me/c/2390601295/95
Signed Ramon Quesada.🇻🇪
Showing the 12 most recent of 20 posts we hold for @BitCoinDatabaseOwnership. 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.
Citation-graph rank — 1,132,426 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“2009 Database ownership” (@BitCoinDatabaseOwnership), 5 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/BitCoinDatabaseOwnership.
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.