Skip to content

Sei chain description#8651

Merged
0xFirekeeper merged 2 commits intomainfrom
cursor/sei-chain-description-78cd
Mar 5, 2026
Merged

Sei chain description#8651
0xFirekeeper merged 2 commits intomainfrom
cursor/sei-chain-description-78cd

Conversation

@Yash094
Copy link
Member

@Yash094 Yash094 commented Jan 29, 2026


Slack Thread

Open in Cursor Open in Web


PR-Codex overview

This PR adds information about the Sei Mainnet to the utils.ts file, specifically detailing its features and achievements.

Detailed summary

  • Added a new entry for Sei Mainnet at line 1329.
  • Included an about description highlighting Sei's capabilities, transaction volume, active user base, and backing by notable investors and talent.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Summary by CodeRabbit

New Features

  • Added support for Sei Mainnet (chain ID 1329) with corresponding network metadata.

✏️ Tip: You can customize this high-level summary in your review settings.

Co-authored-by: yashjoisar <yashjoisar@thirdweb.com>
@cursor
Copy link

cursor bot commented Jan 29, 2026

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@changeset-bot
Copy link

changeset-bot bot commented Jan 29, 2026

⚠️ No Changeset found

Latest commit: 2d4b035

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Jan 29, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs-v2 Ready Ready Preview, Comment Mar 5, 2026 8:23am
nebula Ready Ready Preview, Comment Mar 5, 2026 8:23am
thirdweb_playground Ready Ready Preview, Comment Mar 5, 2026 8:23am
thirdweb-www Ready Ready Preview, Comment Mar 5, 2026 8:23am
wallet-ui Ready Ready Preview, Comment Mar 5, 2026 8:23am

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 29, 2026

Walkthrough

Added chain metadata entry for Sei Mainnet (chain ID 1329) to the chainMetaRecord object in the utils configuration file with corresponding about description.

Changes

Cohort / File(s) Summary
Chain Configuration
apps/dashboard/src/app/(app)/(dashboard)/(chain)/utils.ts
Added metadata entry for chain ID 1329 (Sei Mainnet) to chainMetaRecord with about description.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Sei chain description' accurately and specifically describes the main change: adding a description for the Sei chain to the chainMetaRecord.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check ✅ Passed The PR description provides clear context about the changes, including what was added and how to test it, though it lacks the recommended title format and Linear issue tag.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch cursor/sei-chain-description-78cd

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (2)
  • TEAM-0000: Entity not found: Issue - Could not find referenced Issue.
  • C7838948-6995: Entity not found: Issue - Could not find referenced Issue.

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

@github-actions github-actions bot added the Dashboard Involves changes to the Dashboard. label Jan 29, 2026
@Yash094 Yash094 marked this pull request as ready for review January 29, 2026 07:57
@Yash094 Yash094 requested review from a team as code owners January 29, 2026 07:57
@codecov
Copy link

codecov bot commented Jan 29, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.72%. Comparing base (1d28988) to head (2d4b035).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8651      +/-   ##
==========================================
- Coverage   52.74%   52.72%   -0.02%     
==========================================
  Files         934      934              
  Lines       62965    62965              
  Branches     4136     4136              
==========================================
- Hits        33211    33201      -10     
- Misses      29654    29666      +12     
+ Partials      100       98       -2     
Flag Coverage Δ
packages 52.72% <ø> (-0.02%) ⬇️
see 6 files with indirect coverage changes
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@apps/dashboard/src/app/`(app)/(dashboard)/(chain)/utils.ts:
- Around line 288-292: The about string for the chain entry with key "1329"
contains hard-coded, time‑sensitive metrics (e.g., "4B transactions", "80M
wallets", "#1 EVM chain"); update the "about" property to use evergreen wording
or replace the static metrics with dynamic values sourced from a maintained
API/CMS; locate the object with key 1329 and either change the copy to remove
specific numbers and superlatives or wire the field to read from a maintained
data source (e.g., a CMS client or metrics fetcher) and render the fetched
values instead of hard‑coding them.

Comment on lines +288 to +292
//Sei Mainnet
1329: {
about:
"Sei is a blockchain designed for fast, cheap financial transactions, combining the network effects of Ethereum with the performance of Solana. Sei has processed more than four billion transactions across more than 80 million wallets and has become the #1 EVM chain by number of active users. The team is backed by top investors such as Multicoin, Jump, Coinbase Ventures, and Circle Ventures – and includes talent from companies like Robinhood, Google, Coinbase, Databricks, Uber, and Goldman Sachs.",
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Avoid hard‑coding time‑sensitive metrics and superlatives.

The “4B transactions / 80M wallets / #1 EVM chain” claims will quickly become stale and could be misleading in UI copy. Consider making this description evergreen or sourcing these metrics from a maintained API/CMS.

✏️ Suggested evergreen wording
     about:
-      "Sei is a blockchain designed for fast, cheap financial transactions, combining the network effects of Ethereum with the performance of Solana. Sei has processed more than four billion transactions across more than 80 million wallets and has become the `#1` EVM chain by number of active users. The team is backed by top investors such as Multicoin, Jump, Coinbase Ventures, and Circle Ventures – and includes talent from companies like Robinhood, Google, Coinbase, Databricks, Uber, and Goldman Sachs.",
+      "Sei is a blockchain designed for fast, low-cost financial transactions, combining the network effects of Ethereum with high-performance execution. Backed by leading investors and built by a team with experience from top tech and fintech companies.",
   },
🤖 Prompt for AI Agents
In `@apps/dashboard/src/app/`(app)/(dashboard)/(chain)/utils.ts around lines 288 -
292, The about string for the chain entry with key "1329" contains hard-coded,
time‑sensitive metrics (e.g., "4B transactions", "80M wallets", "#1 EVM chain");
update the "about" property to use evergreen wording or replace the static
metrics with dynamic values sourced from a maintained API/CMS; locate the object
with key 1329 and either change the copy to remove specific numbers and
superlatives or wire the field to read from a maintained data source (e.g., a
CMS client or metrics fetcher) and render the fetched values instead of
hard‑coding them.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 29, 2026

size-limit report 📦

Path Size
@thirdweb-dev/nexus (esm) 105.66 KB (0%)
@thirdweb-dev/nexus (cjs) 319.47 KB (0%)

@github-actions
Copy link
Contributor

This PR has been inactive for 7 days. It is now marked as stale and will be closed in 2 days if no further activity occurs.

@github-actions github-actions bot added Stale and removed Stale labels Feb 10, 2026
@github-actions
Copy link
Contributor

This PR has been inactive for 7 days. It is now marked as stale and will be closed in 2 days if no further activity occurs.

@github-actions github-actions bot added Stale and removed Stale labels Feb 19, 2026
@github-actions
Copy link
Contributor

This PR has been inactive for 7 days. It is now marked as stale and will be closed in 2 days if no further activity occurs.

@github-actions github-actions bot added Stale and removed Stale labels Feb 28, 2026
@0xFirekeeper 0xFirekeeper deleted the cursor/sei-chain-description-78cd branch March 5, 2026 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Dashboard Involves changes to the Dashboard.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants