🟢Vested USDN can now be exported into tokenized form: 1 Vested USDN can be 1:1 converted to a free-circulating token VVUSDNLP(id: 8KEtor9aSsSj38MknyAE7k1uRThHY9prAXgiE4D7WpyL ). ⚠️The import and redeem mechanics is not available yet and will require a certain minimal amount (no less than 100K VVUSDNLP).

Channel
Vires.Finance Announcements
@vf_announcements
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,242subscribers
-15 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001548058559 |
|---|---|
| Type | Channel |
| Username | @vf_announcements |
| Created | Between 1 August 2021 and 11 July 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/vf_announcements |
Topic
Crypto & trading — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 |
|---|---|---|
| 11 Oct 2026, 12:17 | 1,242 | -1 |
| 4 Oct 2026, 21:58 | 1,243 | -2 |
| 25 Sept 2026, 19:40 | 1,245 | -8 |
| 15 Sept 2026, 18:56 | 1,253 | -2 |
| 7 Sept 2026, 08:59 | 1,255 | -1 |
| 30 Aug 2026, 17:07 | 1,256 | -1 |
| 24 Aug 2026, 00:36 | 1,257 | -1 |
| 16 Aug 2026, 19:58 | 1,258 | +1 |
| 6 Aug 2026, 08:21 | 1,257 | no change |
| 6 Aug 2026, 01:04 | 1,257 | first reading |
Engagement
20 posts held, back to 11 July 2022 — 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 20 posts for this entry, the most recent from 25 November 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
New proposal: (VIP-031) Restrict Alameda's address activity within Vires Protocol Voting starts in 24 hrs: https://vires.finance/governance/vote/GT6WmGtjb9ts7SeeQvemqnLv7qbcQEmG8WptMcqXc6ds
🟢Adaptive vesting is here! We know you've been waiting for it, finally a decentralized system to vest USDN is now live. You can already claim up to your daily limit. Here's how it works: ▶️ https://medium.com/@viresfinance/usdn-adaptive-vesting-how-it-works-5f63e5a3e700
🟢Following VIP-30, Vested USDN is skaked and currently earns 7.5% APY. The rewards are accounted several times a day and can be claimed right through vires.finance interface!
New proposal: (VIP-030) Start new USDT and USDC markets, Stake all vested USDN Voting starts in 24 hrs: https://vires.finance/governance/vote/64kiDiyEtJNGtidU11AjEa5KNSYvsR2ARQcugVBzFgVe
🟢$SURF withdrawals for Vested USDN are now live! Any user with vested USDN can now choose to exchange the converted part into $SURF immediately. Find out more here: https://medium.com/@viresfinance/vested-usdn-withdraw-now-using-surf-token-c7ad1b49697e
Vires Finance Plan — Discussion Piece Blog post | Forum thread Read the blogpost and join the discussion on the Vires Strategic Plan going forward!
New proposal: (VIP-029) Unlock USDC and USDT LP Tokens Voting starts in 24 hrs: https://vires.finance/governance/vote/CPz1MQrCadKgLRKp352AN9q4TZzsLLtqfpY2fnAGv3a6
🟢The VIP-028, focused on Repayment in USDN Option for Depositors successfully passed! The option is now accessible through the vires.finance web interface. Thank you to the community for your continued support. Next, we'll be publishing more detailed roadmap for discussion with community. The top priority would be providing comprehesive solution for the still locked liquidity, as well as addressing LP tokens and ac…
New proposal: (VIP-028) Reduce max interest and add repayment in USDN option for all depositors of USDT and USDC Voting starts in 24 hrs: https://vires.finance/governance/vote/C6jQsnCDpgxXAdroSnhheqeq5ersGrqxyrwEqwJCD4Rj
🟢 We hear you, as always, your passion about the project is amazing! Join us tomorrow for AMA with Sasha Ivanov - Thursday 1st of September - 12pm UTC!
Vires Full Reset: Pre-voting discussion Blog post | Forum thread Read the blogpost and join the discussion on the new the proposal aimed to offer a solution for all lenders!
Showing the 12 most recent of 20 posts we hold for @vf_announcements. 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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Vires.Finance Announcements” (@vf_announcements), 1,242 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/vf_announcements.
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.