[BUG] Node showing wrong EVM Chain ID on json RPC call

[NWNZale]

Seid version

name: sei
server_name:
version: v6.0.5-1-gb3fff251
commit: b3fff25
build_tags: netgo ledger,
go: go version go1.21.13 linux/amd64
build_deps:

• cosmossdk.io/errors@v1.0.0
• filippo.io/edwards25519@v1.0.0-rc.1
• github.com/99designs/keyring@v1.2.1

Chain ID
1329

Describe the bug
EVM RPC endpoint is showing chain 713715, despite the node syncing on mainnet, and seid status showing pacific-1

To Reproduce
seid status
{"NodeInfo":{"protocol_version":{"p2p":"8","block":"11","app":"0"},"id":"ec4b9e772bee61997611931ee359fb197e505447","listen_addr":"tcp://:26656","network":"pacific-1","version":"0.35.0-unreleased","channels":"40202122233038606162630070717273","moniker":"dm-westus-mainnet-sei-rpc-01","other":{"tx_index":"on","rpc_address":"tcp://127.0.0.1:26657"}},"SyncInfo":{"latest_block_hash":"91720CA15B9DC375DFDB39EAFD550C9546A11D4B83B1EDDFDE471AFC623AE6F6","latest_app_hash":"737DBD627E735C3A21AD21EA1BE6D125561643C0C41F302817FD8F2E6A1ED52A","latest_block_height":"137668756","latest_block_time":"2025-03-21T03:00:44.279485646Z","earliest_block_hash":"3CBED65EEC09D9B0A252DC0F9ECB11BC7C655333EB55AFAE930952C60B56D5C8","earliest_app_hash":"502BC75534C8C7EB58233573701BC05F10E25290E3541D60336DB4AA46179508","earliest_block_height":"135879999","earliest_block_time":"2025-03-10T16:37:33.081566243Z","max_peer_block_height":"137789128","catching_up":true,"total_synced_time":"0","remaining_time":"0","total_snapshots":"0","chunk_process_avg_time":"0","snapshot_height":"0","snapshot_chunks_count":"0","snapshot_chunks_total":"0","backfilled_blocks":"0","backfill_blocks_total":"0"},"ValidatorInfo":{"Address":"","PubKey":{"type":"tendermint/PubKeyEd25519","value":"="},"VotingPower":"0"}}

curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}' http://localhost:8545
{"jsonrpc":"2.0","id":1,"result":"0xae3f3"}

Expected behavior
I expect the EVM RPC calls to show chain 1329, not 713715

Note this is consistent on v6.0.3 as well.

[NWNZale]

Closed, related to #1232