31 Jul 2025, 04:06 UTC467 views28 reactionsread 7 August 2026
Forwarded from @rgbconsortiumFile
Presenting RGB yellow paper: a preprint of an academic paper with the formal specification of RGB consensus I.0
🔥16❤5🎉5👍2
Channel
LNP/BP
@lnp_bp
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
434subscribers
-9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001348636183 |
|---|---|
| Type | Channel |
| Username | @lnp_bp |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/lnp_bp |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 90% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 19:17 | 434 | -2 |
| 18 Sept 2026, 13:56 | 436 | -1 |
| 9 Sept 2026, 16:41 | 437 | -1 |
| 23 Aug 2026, 21:37 | 438 | -2 |
| 15 Aug 2026, 20:03 | 440 | -3 |
| 7 Aug 2026, 02:17 | 443 | no change |
| 7 Aug 2026, 02:04 | 443 | first reading |
Engagement
18 posts held, back to 10 September 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 page of 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 31 July 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
520 reactions across 18 posts, in 14 distinct kinds. The most used accounts for 54.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 282 | 54.2% | |
| ❤ | 77 | 14.8% | |
| 👍 | 74 | 14.2% | |
| 🎉 | 26 | 5.00% | |
| 👏 | 17 | 3.27% | |
| ⚡ | 13 | 2.50% | |
| 🏆 | 6 | 1.15% | |
| 🍾 | 5 | 0.962% | |
| 💯 | 5 | 0.962% | |
| 🆒 | 4 | 0.769% | |
| 👎 | 4 | 0.769% | |
| 🤡 | 3 | 0.577% | |
| 👀 | 2 | 0.385% | |
| 🦄 | 2 | 0.385% |
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 18 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 520 reactions 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 10 September 2023 to 31 July 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.
Recent posts
31 Jul 2025, 04:06 UTC593 views5 reactionsread 7 August 2026
Today, with @rgbconsortium and @pandoraprime we are glad to present the formal specification for RGB smart contracts
🎉5
18 Jul 2025, 12:12 UTC802 views21 reactionsread 7 August 2026
An official security notice on RGB fork claimed to be 'RGB v0.11.1' It has come to our attention that the recently announced "release" of "RGB protocol version 0.11.1" runs a fork of RGB v0.11 from unreleased last year codebase, with heavily modifications to the consensus, affecting its security. These modifications were proposed to the main RGB repositories but didn't meet our security requirements and were of poor…
👍11❤6👎4
10 Jul 2025, 13:09 UTC≈1,360 views44 reactionsread 7 August 2026
🎉 Release Announcement The LNP/BP Standards Association is excited to announce the final production-ready release of the RGB smart contracts consensus layer (v0.12)! 🚀 From today, all RGB contract developers and issuers can deploy contracts on both testnet and Bitcoin mainnet using this stable consensus release. ⚠️ Important: For security and ecosystem consistency, we strongly recommend re-issuing any contracts cr…
🔥32👍9❤3
9 Jul 2025, 18:21 UTC898 views21 reactionsread 7 August 2026
🥳 Video from BTCPrague RGB event is up! 🥳 During the BTCPrague conference we organised a side event where the latest news on the state of RGB: protocol, tooling and ecosystem were presented. What is covered in the video? - Latest news on the state of the protocol and tooling around it. - Last steps towards the official RGB release. - Q&A session, including the answer on ‘How do I start with RGB?’ And much more 😎 H…
🔥9👍7❤5
3 Jul 2025, 14:46 UTC717 views38 reactionsread 7 August 2026
⚡️🥳Announcement alert ⚡️🥳 We are proud to announce that this year the LNP/BP Standards Association that has been overseeing the RGB development since 2019, has joined the sponsoring team of one of the oldest and most pure signal conferences in the sphere - Baltic Honeybadger that takes place 9th-10th August in Riga🇱🇻 We will be presenting many updates, news and throw workshops, so get your tickets and see you all so…
🔥23❤6👏5🍾2🎉2
16 Dec 2024, 08:35 UTC938 views2 reactionsread 7 August 2026
Dr. Maxim Orlovsky’s talk from Baltic Honeybadger is live! 🤓🍿 Check it out to learn more about RGB, its ecosystem and future.
🔥2
16 Dec 2024, 08:35 UTC≈1,360 views19 reactionsread 7 August 2026
RGB is a native member of Bitcoin and the Lightning Network ecosystem. Check out this video if you want to learn more about it! 🔥 https://www.youtube.com/watch?v=m5E6-npQ97w
👍18🔥1
5 Sept 2024, 18:07 UTC≈2,100 views42 reactionsread 7 August 2026
🚀 RGB v0.11 beta 8 is released, marking the start of the pre-release code freeze. The new beta comes with a several bugfixes and completion of previous epics related to the data persistence and better eltoo support. Beta 8 release continues a phase of preparation for a public preview of the RGB v0.11. All parties are strongly recommended switching to this latest beta 8, which contains a number of bugfixes and a cons…
🔥31🎉5🤡3👏2👍1
22 Aug 2024, 11:59 UTC≈1,200 views43 reactionsread 7 August 2026
🚀 RGB v0.11 beta 7 is released, coming with many bugfixes and an important improvements: - introspection of global contract state from scripts - improved handling of blockchain re-orgs and RBFs - improved Lightning operations - hot taproot RGB wallets - efficient managing of RGB contract state in enterprise and embedded environments - support for Mempool API and Testnet4 Read the official announcement and learn abou…
🔥21👍8⚡5👏4🎉2👀2❤1
9 Jun 2024, 16:18 UTC≈1,860 views49 reactionsread 7 August 2026
🚀️️ Congrats to everyone and thank you all for your contributions: we have v0.11 beta 6 out Beta 6 marks new stage in RGB readiness - please read all the details in the public announcement: https://rgb.tech/blog/release-v0-11-beta-6/
❤22🔥15🎉4🍾3👍3👏2
24 Apr 2024, 19:33 UTC≈1,440 views42 reactionsread 7 August 2026
Photo
Welcome #SSI: self-sovereign identities made with #Bitcoin single-use seals! ssi:LZS1ux-gjD9nXPF-OcetUUkW-6r3uSCS6-aQhs9W5f-8JE7w This SSI will be used by us for signing all standard #RGB interfaces and libraries - and assets issuers will be able to do the same for their contracts, such that wallets and users can be safu from impersonators. Stay tuned to learn more - we will be releasing SSI docs & code alongside …
🔥30⚡6❤6
Showing the 12 most recent of 18 posts we hold for @lnp_bp. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 1 registered channel — 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.
Cite this entry
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“LNP/BP” (@lnp_bp), 434 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/lnp_bp.
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.