Channel
@privoracash
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
70subscribers
+16 since we began measuring on 30 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003949455289 |
|---|---|
| Type | Channel |
| Username | @privoracash |
| Created | Between 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 September 2026 |
| Last confirmed live | 14 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 October 2026 |
| On Telegram | t.me/privoracash |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 44% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Oct 2026, 03:28 | 70 | -2 |
| 5 Oct 2026, 12:38 | 72 | +18 |
| 30 Sept 2026, 02:22 | 54 | no change |
| 30 Sept 2026, 01:47 | 54 | first reading |
20 posts held, back to 27 September 2026 — 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 29 September 2026 |
|---|---|
| Posts held | 20 (27 September 2026 – 29 September 2026) |
| Views total | 2,034 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Sept 2026, 02:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 7 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Where do PRIVORA fees go? On-chain, where you can watch them. Deposit is free, with gas sponsored by the relayer. Send costs 0.15% per withdrawal. Multi costs 0.10% per withdrawal. Every fee routes to the on-chain treasury inside the same transaction that serves you, and the contract itself caps fees at 1%. There is no spreadsheet to trust and no support ticket to file. Anyone can open the explorer and follow every…
Privacy is a headcount. Every privacy system is only as strong as the number of people inside it. An anonymity set of ten is a spotlight. An anonymity set of ten thousand is cover. Each deposit into the pool grows the crowd, and the crowd is what protects you. This is why we obsess over growth that is real. More accounts, more deposits, more epochs, more cover for everyone who came before you and everyone who arriv…
First-generation mixers solved half the problem. They broke the link between sender and receiver, but they could not separate honest users from bad actors. Regulators did the math for them. Privacy pools add the missing layer: association sets. Every withdrawal proves membership in an approved set of deposits, without revealing which deposit was yours. Honest funds prove themselves. Nothing else is exposed. This de…
Distribution is where privacy breaks first. One funding wallet suddenly touches hundreds of recipients, in public, forever. PRIVORA Multi was built for exactly this. One note funds the entire batch through change-note chaining. Up to 25 recipients per run, each paid with their own zero-knowledge proof, each receiving an ordinary transfer with no visible link to you or to each other. If one transfer fails, the rest c…
Anatomy of a private withdrawal. Every claim below is on-chain. What this transaction contains: → A groth16 proof, generated in the user's browser, verified by the Entrypoint contract → Public signals: newCommitment, nullifierHash, withdrawnValue, stateRoot, ASPRoot, context → context binds the proof to exactly one recipient and one fee. Nothing else can be claimed → nullifierHash is recorded, the note is burned. D…
Season 1 of PRIVORA Points starts now. The rules are simple on purpose. Use the product, earn points. Every deposit, every private send, every batch through Multi accumulates points for your account, tracked per season, visible in the app. The Season 1 quest board: 01. Create your account and secure your keyfile 02. Make your first deposit into the pool 03. Send a private withdrawal 04. Verify any proof on the publ…
An operational note for everyone who joined before launch. During pre-TGE, every PRIVORA feature was open to all. That was our thank you to the earliest users. Now that $VORA is live, the hold-gate activates: Multi checks for 500,000 VORA or more in your embedded wallet before it executes. Deposit and Send stay free and open to everyone. That never changes. If you ran batches during the open period, thank you for …
A DAO needs to pay twelve contributors this week. From a public wallet, that payment is a press release it never agreed to make. The treasury address, the amounts, the timing, the contributors. Permanent, searchable, linkable. From PRIVORA, the same payment looks very different. Funds enter the pool once. Each contributor receives an ordinary transfer at a fresh address. On-chain, observers see proofs and nullifier…
What does $VORA actually do? Let's be precise, because the answer is not "number go up." Holding 500,000 $VORA or more in your PRIVORA embedded wallet unlocks every premium feature, starting with Multi: private batch distribution to up to 25 recipients from a single note. The gate is a proof of ownership, not a payment. Your tokens never move. There is no approval to sign, no transaction to send, no lock period. A …
$VORA is live. The token behind the private account layer for on-chain finance launches today on @ponsdotfamily , the native launchpad of Robinhood Chain, the same chain our pool runs on. CA: 0x1a8733d45b32adc02c740d4e6d95f8d67dbc2f2dd VORA is a utility token with a fixed supply of 1,000,000,000. Holding 500,000 $VORA or more unlocks every premium feature inside PRIVORA, starting with Multi, our private batch dist…
Two minutes. That is all it takes to go from a public balance to a private one. Watch the full walkthrough below. Creating a PRIVORA account with a username and password. Receiving your encrypted keyfile. Depositing ETH into the pool with an ordinary transfer from an ordinary wallet. Watching your private balance appear. No seed phrase. No wallet connect. No gas management. No link between your old address and your…
Most projects announce what they will build. We prefer to show what already works. Live on PRIVORA today: ✅ Deposit. Free, with gas sponsored by the relayer. Send ETH from any wallet or exchange to a one-time session address. ✅ Send. Private withdrawals verified by zero-knowledge proofs, 0.15% per withdrawal. ✅ Multi. Batch distribution to up to 25 recipients from a single note, 0.10% per withdrawal. Everything …
Showing the 12 most recent of 20 posts we hold for @privoracash. 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.
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.
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 14 October 2026 — this entry's latest reading, not the date you are reading this.
“PRIVORA” (@privoracash), 70 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/privoracash.
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.