Skip to content

fix(scan): remove redundant sticky stats bar from home#104

Merged
github-actions[bot] merged 1 commit into
mainfrom
fix/scan-drop-redundant-sticky-stats
Jun 25, 2026
Merged

fix(scan): remove redundant sticky stats bar from home#104
github-actions[bot] merged 1 commit into
mainfrom
fix/scan-drop-redundant-sticky-stats

Conversation

@satyakwok

Copy link
Copy Markdown
Member

The sticky stats bar under the navbar showed four cells: SRX Price, Latest Block, Network TPS, Active Validators. None of them added unique information:

  • SRX Price was hardcoded to $-.-- / not listed with no price source, so it was permanently dead on both networks.
  • Latest Block, TPS, and Active Validators already appear in the LiveTicker and the main stats grid.

Block height and the validator count were rendered three times above the fold. Removed the bar and deleted its component (it was only used on the home page).

Testing

typecheck and build pass. Verified live: the home page no longer renders the bar (no SRX Price cell), layout is clean, and the LiveTicker plus stats grid still cover every value.

The sticky stats bar showed SRX Price (hardcoded "not listed", no price
source) plus Latest Block, TPS, and Active Validators, all of which already
appear in the LiveTicker and the main stats grid. Block height and validator
count rendered three times above the fold. Dropped the bar and its component.
@github-actions github-actions Bot enabled auto-merge (squash) June 25, 2026 09:06
@coderabbitai

coderabbitai Bot commented Jun 25, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@satyakwok, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 15 minutes and 10 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8861d21b-80c8-4ccf-aef7-613691053ea4

📥 Commits

Reviewing files that changed from the base of the PR and between b03fa31 and d6d0d58.

📒 Files selected for processing (2)
  • apps/scan/app/[locale]/HomeContent.tsx
  • apps/scan/components/home/StickyStatsBar.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/scan-drop-redundant-sticky-stats

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot merged commit cc636e7 into main Jun 25, 2026
7 checks passed
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.

1 participant