Update Telegram community chat link#767
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Warning Review limit reached
More reviews will be available in 52 minutes and 7 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR updates the contact information in the README documentation. The Telegram community chat link in the contact section is changed from Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 146: The README currently links the Telegram community chat as
"t.me/Sentrix_Chain"; verify whether this is the official/redirected handle and,
if not, replace it with the official "t.me/SentrixCommunity" (or the correct
canonical handle) in the README entry that contains "**Telegram:**
[t.me/SentrixChain] ... [t.me/Sentrix_Chain]"; ensure the visible text and the
href both match the verified handle and add a short comment/note in the README
only if this is a deliberate/temporary replacement to avoid routing users to an
incorrect/inactive chat.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 478ea93b-1fef-498a-89c4-93682c9182a1
📒 Files selected for processing (1)
README.md
| **gRPC + gRPC-Web:** [grpc.sentrixchain.com](https://grpc.sentrixchain.com) · [grpc-testnet.sentrixchain.com](https://grpc-testnet.sentrixchain.com) | ||
| **WebSocket:** `wss://api.sentrixchain.com/ws` (mainnet) · `wss://testnet-api.sentrixchain.com/ws` (testnet) | ||
| **Telegram:** [t.me/SentrixChain](https://t.me/SentrixChain) (announcements) · [t.me/SentrixCommunity](https://t.me/SentrixCommunity) (community chat) | ||
| **Telegram:** [t.me/SentrixChain](https://t.me/SentrixChain) (announcements) · [t.me/Sentrix_Chain](https://t.me/Sentrix_Chain) (community chat) |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Search for references to the old Telegram community link
# Search for the old community link in all files
rg -i 'SentrixCommunity' --type md --type-add 'config:*.{toml,yaml,yml,json}' --type config -C2
# Also check documentation and config directories if they exist
fd -e md -e yml -e yaml -e toml -e json . | xargs rg -l 'SentrixCommunity' 2>/dev/null || trueRepository: sentrix-labs/sentrix
Length of output: 46
🌐 Web query:
Is the Telegram channel t.me/Sentrix_Chain active and accessible?
💡 Result:
Based on official documentation and project resources as of June 2, 2026, the official Telegram channel for Sentrix Chain is t.me/SentrixCommunity [1]. The specific URL t.me/Sentrix_Chain is referenced as a contact link within the official Sentrix Chain metadata [2], but it is not the primary community channel maintained by the developers [1]. If you are attempting to access a project channel, you should use the official link t.me/SentrixCommunity to ensure you are connecting to the verified community [1]. Always verify links against the project's official website (sentrixchain.com) or their GitHub organization (sentrix-labs) to avoid potential impersonation or invalid links [1][3].
Citations:
- 1: https://github.com/sentrix-labs/sentrix/blob/14f7b1a5b0bcce3c4b55b1141c9cdd2c6c96cb1f/README.md
- 2: https://t.me/SentrixChain
- 3: https://github.com/sentrix-labs
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "=== old link references (handle) ==="
rg -n -i 't\.me/SentrixCommunity|SentrixCommunity' .
echo "=== new link references (handle) ==="
rg -n -i 't\.me/Sentrix_Chain|Sentrix_Chain' .
echo "=== announcements handle references ==="
rg -n -i 't\.me/SentrixChain|SentrixChain' README.md || trueRepository: sentrix-labs/sentrix
Length of output: 101
🌐 Web query:
t.me/Sentrix_Chain active accessible
💡 Result:
The Telegram link in your query (t.me/Sentrix_Chain) does not appear to be the official, publicly indexed Telegram channel name for Sentrix Chain. What I could verify instead: 1) Sentrix Chain’s official documentation and GitHub README point to a Telegram channel named t.me/SentrixCommunity, not t.me/Sentrix_Chain [1]. 2) Sentrix Chain’s official site/docs describe the live Sentrix Chain network (EVM-compatible L1, Voyager consensus, etc.), but those sources still link to t.me/SentrixCommunity for Telegram, not Sentrix_Chain [2][3][1]. So, I can’t confirm that t.me/Sentrix_Chain is “active/accessible” or official based on authoritative sources I found. It may be a different community, an outdated/incorrect link, or an impostor. If you want to check safely on your side: - Compare the exact Telegram username in the official Sentrix website/docs (t.me/SentrixCommunity) with what you were shown. - If it’s different, treat it as unverified and avoid sending funds/messages based on it. Sources: [1][2][3]
Citations:
- 1: https://github.com/sentrix-labs/sentrix/blob/14f7b1a5b0bcce3c4b55b1141c9cdd2c6c96cb1f/README.md
- 2: https://sentrixchain.com/en
- 3: https://docs.sentrixchain.com/
🌐 Web query:
t.me/SentrixCommunity active accessible Sentrix Chain official community
💡 Result:
As of June 2, 2026, the Telegram group located at t.me/SentrixCommunity exists and is publicly accessible, though it appears to have a very low number of participants (noted as having 2 subscribers) [1]. It is officially listed in the Sentrix Chain documentation and repository as the designated community chat [2][3]. The core official channel for Sentrix Chain updates is @SentrixChain [4][2]. Sentrix Chain is a Rust-based, EVM-compatible Layer-1 blockchain [2][5]. Official technical information, such as the network's chain ID (7119), RPC details, and project roadmap, is maintained on the official website (sentrixchain.com) and the project's official GitHub repositories under the Sentrix Labs organization [6][2][3]. Users are advised to rely on these verified, technical sources for project developments, as other blockchain projects (such as IONIX CHAIN) may appear in search results but are unrelated to Sentrix Chain [7][8].
Citations:
- 1: https://t.me/SentrixCommunity
- 2: https://github.com/sentrix-labs/awesome-sentrix
- 3: https://github.com/sentrix-labs/sentrix
- 4: https://t.me/SentrixChain
- 5: https://github.com/sentrix-labs/sentrix/tree/v2.1.47
- 6: https://sentrixchain.com/en
- 7: https://www.openpr.com/news/4523261/best-crypto-presale-list-2026-ionix-chain-ranked-1-among-top
- 8: https://www.openpr.com/news/4520721/best-crypto-to-buy-now-ionix-chain-is-the-smartest-buy-right-now
🏁 Script executed:
#!/bin/bash
set +euo pipefail
echo "=== old link exact URLs (t.me/SentrixCommunity) ==="
rg -n --hidden --no-ignore -S 't\.me/SentrixCommunity' . || true
echo "=== old link handle (SentrixCommunity) ==="
rg -n --hidden --no-ignore -S 'SentrixCommunity' . || true
echo "=== new link exact URLs (t.me/Sentrix_Chain) ==="
rg -n --hidden --no-ignore -S 't\.me/Sentrix_Chain' . || true
echo "=== new link handle (Sentrix_Chain) ==="
rg -n --hidden --no-ignore -S 'Sentrix_Chain' . || trueRepository: sentrix-labs/sentrix
Length of output: 570
Telegram community chat link: new URL may not match official sources
- Codebase no longer references the old community chat (
t.me/SentrixCommunity); onlyt.me/Sentrix_Chainis present inREADME.md(line 146). - Public/official references for Sentrix Chain point to
t.me/SentrixCommunityas the community chat, sot.me/Sentrix_Chainlooks unverified and may be incorrect (risk: users can be routed to a wrong/inactive chat).
Update the link to the official handle (or ensure t.me/Sentrix_Chain is the correct replacement/redirect) before merging.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` at line 146, The README currently links the Telegram community
chat as "t.me/Sentrix_Chain"; verify whether this is the official/redirected
handle and, if not, replace it with the official "t.me/SentrixCommunity" (or the
correct canonical handle) in the README entry that contains "**Telegram:**
[t.me/SentrixChain] ... [t.me/Sentrix_Chain]"; ensure the visible text and the
href both match the verified handle and add a short comment/note in the README
only if this is a deliberate/temporary replacement to avoid routing users to an
incorrect/inactive chat.
satyakwok
force-pushed
the
fix/telegram-community-chat-link
branch
from
b442344 to
0c57d75
Compare
1 participant
Summary
Risk tier
Check ONE:
sentrix-core,sentrix-trie,sentrix-staking,sentrix-bft),block_executor,apply_block_*,state_rootpathRequired by tier
🟢 Low — minimum bar
🟡 Medium — adds
#[test]in same PR🟠 High — adds
🔴 Critical — adds
Test plan
Rollback plan
Related
Summary by CodeRabbit