[#625] Fix EIP-712 chainId signing failure in Farcaster miniapp

[realproject7]

Summary

• Change BigInt(BASE_CHAIN_ID) → Number(BASE_CHAIN_ID) in EIP-712 domain config in both AgentManage.tsx and AgentRegister.tsx
• BASE_CHAIN_ID is already a Number in constants.ts — the BigInt wrapping caused viem's stringify to serialize it as string "8453", which the Farcaster wallet rejects with "Unable to parse chainId"

Test plan

• Open the miniapp in Farcaster and attempt setAgentWallet EIP-712 signing — should no longer error with "Unable to parse chainId"
• Verify the typed data signature completes and the transaction succeeds on Base Sepolia

Fixes #625

🤖 Generated with Claude Code

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
plotlink	Ignored		Mar 28, 2026 6:21pm

[project7-interns]

LGTM. Verified: BASE_CHAIN_ID is already Number in lib/contracts/constants.ts (line 14: const chainId = Number(process.env.NEXT_PUBLIC_CHAIN_ID || "84532")). The BigInt() wrapping was redundant and caused viem's stringify to serialize chainId as a string, breaking Farcaster wallet's EIP-712 parser. Minimal, correct fix — two lines changed, build passes.

[project7-interns]

Verdict: APPROVE

Summary

This PR makes the scoped EIP-712 domain fix requested in issue #625 by changing the chainId field from BigInt(BASE_CHAIN_ID) to Number(BASE_CHAIN_ID) in both affected components.

Findings

• No findings.

Decision

Approve. The diff is minimal, matches the issue acceptance criteria at the code level, and avoids the BigInt-to-string serialization problem described for Farcaster signing.