Add a link to the project website (ethlambda.xyz) in the README

[pablodeymo]

Motivation

The project has a website at ethlambda.xyz, but it isn't referenced anywhere in the README.

Description

Adds a link to the website right under the tagline at the top of the README, with an invitation for readers to visit it. This is the first thing a reader sees, so the invitation lands where attention is highest.

How to Test

Open README.md and confirm the link appears below the tagline and points to https://ethlambda.xyz.

[github-actions]

🤖 Codex Code Review

No findings.

The diff is limited to README.md, adding a project website link. It does not touch consensus logic, networking, SSZ, signature handling, storage, or any runtime Rust code, so I do not see correctness, security, or performance risk from this PR.

Residual risk is minimal and non-code only: the external link should remain maintained and trustworthy over time. No test changes are needed for this patch.

---

Automated review by OpenAI Codex · gpt-5.4 · custom prompt

[github-actions]

🤖 Kimi Code Review

The provided diff only contains a trivial README modification and does not include any consensus-layer code (state transitions, fork choice, XMSS signatures, SSZ encoding, etc.) referenced in your review instructions.

Review of Actual Changes

File: README.md
Lines: +5

🌐 Visit our website at [**ethlambda.xyz**](https://ethlambda.xyz) to learn more about the project.

Assessment

Security & Correctness:

• Uses HTTPS scheme correctly (https://ethlambda.xyz)
• Markdown syntax is valid (proper nesting of bold ** inside link brackets)
• Action required: Verify that ethlambda.xyz is a domain permanently controlled by the LambdaClass organization. If the domain registration lapses, this link could become a phishing vector targeting users of this Ethereum client.

Maintainability:

• The emoji (🌐) and bold formatting are consistent with modern README conventions
• Line placement (between description and "Getting started") is logical

Missing Context:
If this PR was intended to include consensus-critical changes (as suggested by your request for XMSS/SSZ/finality logic review), the diff appears incomplete. Please provide the full diff containing:

• Rust source files (.rs)
• Changes to consensus/, crypto/, or ssz/ directories
• Any modifications to state transition or fork choice functions

Verdict: The README change is acceptable assuming domain ownership verification, but no consensus-code review is possible with the current diff.

---

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

[greptile-apps]

Greptile Summary

This PR adds the project website link near the top of the README. The main change is:

• A new ethlambda.xyz link below the project tagline.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed README content.

Important Files Changed

Filename	Overview
README.md	Adds a website callout below the project tagline.

_{Reviews (1): Last reviewed commit: "Add a link to the project website (ethla..." | Re-trigger Greptile}

[github-actions]

🤖 Claude Code Review

The diff is a 2-line README-only change. Running the full multi-angle review would spawn many agents for effectively zero code surface — I'll review this inline since it doesn't warrant parallel agents.

---

PR #475 Review — "Add a link to the project website (ethlambda.xyz) in the README"

Overview: This PR adds a single line to README.md placing a website link immediately after the project tagline. No code, logic, or configuration is touched.

Findings: None. The change is correct and complete.

A few minor observations worth a quick sanity-check, none of which require changes:

• Voice consistency — "our website" (first-person) is consistent with existing README prose ("We use cargo as our build system" on line 18), so no inconsistency.
• Bold inside link text — [**ethlambda.xyz**](https://ethlambda.xyz) renders correctly on GitHub (bold + link underline). It adds emphasis but is not incorrect.
• Emoji — 🌐 renders fine on GitHub and is common in open-source READMEs. The rest of this README doesn't use emoji, but the placement is the first reader touchpoint and the choice is intentional per the PR description.
• URL — uses HTTPS and matches the domain cited in the PR description. No bare HTTP or typo.

Verdict: Clean, minimal, correct. Nothing to block or change.

---

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