eth_sendRawTransaction and eth_getBalance keep repeating and failing

```
An unexpected error occurred while executing "eth_sendRawTransaction" JSON-RPC method: Error: RPC request failed
at RPC. (/home/ubuntu/.nvm/versions/node/v18.12.1/lib/node_modules/@lightclients/kevlar/node_modules/@lightclients/patronum/lib/rpc.js:93:19)
at Generator.next ()
at fulfilled (/home/ubuntu/.nvm/versions/node/v18.12.1/lib/node_modules/@lightclients/kevlar/node_modules/@lightclients/patronum/lib/rpc.js:28:58)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

An unexpected error occurred while executing "eth_getBalance" JSON-RPC method: Error: RPC request failed
at RPC. (/home/ubuntu/.nvm/versions/node/v18.12.1/lib/node_modules/@lightclients/kevlar/node_modules/@lightclients/patronum/lib/rpc.js:93:19)
at Generator.next ()
at fulfilled (/home/ubuntu/.nvm/versions/node/v18.12.1/lib/node_modules/@lightclients/kevlar/node_modules/@lightclients/patronum/lib/rpc.js:28:58)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
```

these two errors keep showing up, my guess is that wallet will keep calling this rpc and rpc failed without sending error to wallet so that wallet will keep calling.

How to fix this issue? And how to reset?

Start by reproducing the eth_sendRawTransaction and eth_getBalance failures and inspect the RPC stack trace location, @lightclients/patronum/lib/rpc.js:93. Trace how the wallet handles the failed RPC response and determine whether repeated calls can be stopped or reset. Done means the failure path is understood and the issue has a verified fix or documented reset procedure.

Written by the indexing model from the issue text.