Route read RPC methods directly to node for injected wallets

[MuncleUscles]

Summary

• route only wallet/signing methods through the injected provider
• keep read/tx-polling RPC methods on direct node fetch transport
• add tests to lock method routing for eth_sendTransaction, eth_chainId, and eth_getTransactionByHash

Why

Injected providers can alter or normalize read responses, which breaks localnet-specific transaction polling paths that expect GenLayer fields like status.

Validation

• npm test -- --run tests/client.test.ts tests/contracts-actions.test.ts tests/transactions.test.ts

[coderabbitai]

Warning

Rate limit exceeded

@MuncleUscles has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 16 minutes and 29 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/wallet-compat-no-filltx

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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