Skip to content

docs: point the Telegram links at t.me/lambdaconsensus - #766

Merged
pablodeymo merged 1 commit into
mainfrom
docs/telegram-lambdaconsensus
Nov 3, 2026
Merged

pablodeymo merged 1 commit into
mainfrom
docs/telegram-lambdaconsensus

Conversation

@MegaRedHand

Copy link
Copy Markdown
Collaborator

Motivation

The project's Telegram group is now t.me/lambdaconsensus, but the docs still sent readers to the old t.me/ethlambda_client link.

Changes

Replaces the Telegram URL in the three places it appears:

  • README.md
  • CONTRIBUTING.md
  • docs/introduction.md (mdbook)

The link label ("ethlambda group") and the surrounding text are unchanged.

The project's Telegram group is now t.me/lambdaconsensus; the README,
CONTRIBUTING and the mdbook introduction still sent readers to the old
ethlambda_client link.
@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown

🤖 Kimi Code Review

I'll review this PR diff for the ethlambda repository.

Overview

This PR changes Telegram group links across three documentation files from https://t.me/ethlambda_client to https://t.me/lambdaconsensus.

Review Findings

1. Consistency Check — PASS

The change is applied consistently across all three locations:

  • CONTRIBUTING.md:153
  • README.md:499
  • docs/introduction.md:48

No dangling references to the old URL remain in the diff. Good.

2. URL Validation — QUESTION

The new URL https://t.me/lambdaconsensus should be verified:

  • Confirm this Telegram group actually exists and is controlled by the project
  • Confirm @lambdaconsensus is the correct username (Telegram usernames are case-insensitive but must be at least 5 characters; this meets that requirement)

Recommendation: If not already done, verify the link resolves correctly before merge. This is a social engineering attack vector if an attacker can squat the username.

3. Documentation Scope — POTENTIAL ISSUE

The diff shows only three files changed, but other documentation may reference the old URL:

Check for other occurrences (not in diff, but worth verifying):

  • docs/ subdirectories beyond introduction.md
  • Website/blog content
  • Cargo.toml repository or homepage fields (though these typically point to GitHub, not Telegram)
  • Any generated docs or configuration templates

Recommendation: Run a repository-wide search for ethlambda_client to ensure no stale references remain:

grep -r "ethlambda_client" .

4. Link Text vs. URL Mismatch — MINOR

In all three files, the link text remains "ethlambda group" while the URL now points to lambdaconsensus. This is intentional and correct (the group name changed, not necessarily the descriptive text), but worth confirming this is the desired branding.

5. No Code Changes — NOTE

This PR contains no Rust code changes, so none of the consensus-critical review criteria (fork choice, attestation processing, XMSS signatures, SSZ encoding, etc.) apply here.

Summary

Aspect Status
Correctness ✓ No bugs
Security ⚠ Verify URL ownership (low risk for docs-only change)
Completeness ? Check for other occurrences of old URL
Rust/Performance N/A — documentation only

Recommendations

  1. Before merge: Confirm https://t.me/lambdaconsensus is the official, controlled group
  2. Before or after merge: Search repository for any remaining ethlambda_client references
  3. Optional: Consider if link text should update to "lambdaconsensus group" for clarity

The change itself is straightforward and appears correct. No blocking issues.


Automated review by Kimi (Moonshot AI) · kimi-k2.6 · custom prompt

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown

🤖 Codex Code Review

⚠️ The review job did not complete (result: failure). See the job log


Automated review by OpenAI Codex

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown

🤖 Claude Code Review

Review of PR 766: docs: point the Telegram links at t.me/lambdaconsensus

This is a docs-only change. It swaps one URL in README.md, CONTRIBUTING.md and docs/introduction.md. It touches no code, so there are no consensus, security or performance concerns.

  • I searched the repo for ethlambda_client and found no remaining references to the old link. All three occurrences were updated.
  • The link label and surrounding text are unchanged, as the PR description says.
  • One small point: the label still reads "ethlambda group" while the URL is now lambdaconsensus. That's fine if the group is still the ethlambda community channel. If it has become a broader LambdaClass or consensus group, the label could change, but that's optional.

I haven't checked that t.me/lambdaconsensus resolves to the intended group, so a maintainer should confirm that.

LGTM.


Automated review by Claude (Anthropic) · sonnet · custom prompt

@pablodeymo
pablodeymo added this pull request to the merge queue Nov 3, 2026
Merged via the queue into main with commit f822a2b Nov 3, 2026
16 of 17 checks passed
@pablodeymo
pablodeymo deleted the docs/telegram-lambdaconsensus branch November 3, 2026 18:29
MegaRedHand added a commit that referenced this pull request Nov 5, 2026
Brings in #751 (bump rustls, quick-xml, zstd-sys, ruint and quinn-proto
past RustSec advisories, and drop libp2p's unused transports), #763 (the
DeepSeek, Gemini and Grok AI reviewers) and #766 (the Telegram links).

#746 is main's version of a PR nightly already carries as squash 2b0f720.
Its reference test sits elsewhere in fork_choice.rs on main, so the merge
added a second, identical copy; that copy is dropped, which leaves
fork_choice.rs exactly as nightly had it.

Claude-Session: https://claude.ai/code/session_011vghNmndKPkZinHRkVTwVB
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants