personal_listWallets
Last updated:
`personal_listWallets` returns an array describing every wallet the backing Ethereum node knows about. Each entry carries the wallet's backend `url` (for example a keystore directory or a hardware-wallet path), the current `status` of that backend, and the list of `accounts` that have been derived from or unlocked within it.
This method belongs to the `eth_peergraph` category and is restricted to the **Business** tier. It is an operational / introspection call — it reflects the key-management state of the specific node serving your request, so the wallet set and its statuses vary between calls and between nodes. Use it to inspect node-side account state alongside [personal_listAccounts](./personal_listAccounts.md), not to manage end-user keys.
It takes no parameters.
Parameters
This method takes no parameters.
Returns
| Field | Type |
|---|---|
| result | object |
Examples
curl https://<your-endpoint>/ \
-X POST -H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"personal_listWallets","params":[]}'const res = await fetch("https://<your-endpoint>/", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
"id": 1,
"method": "personal_listWallets",
"params": [],
"jsonrpc": "2.0"
}),
});
const data = await res.json();import requests
resp = requests.post("https://<your-endpoint>/", json={"id":1,"method":"personal_listWallets","params":[],"jsonrpc":"2.0"})
print(resp.json())Usage
- Transport: HTTP (JSON-RPC).
- Networks: mainnet.
- Credit cost: 1 per call.
FAQ
- What does personal_listWallets do?
- Returns the wallets managed by the backing Ethereum node, each with its backend URL, unlock status, and derived accounts.
- How many credits does personal_listWallets cost?
- personal_listWallets costs 1 credit(s) per call on Triport by default.
- Is personal_listWallets available over WebSocket?
- personal_listWallets is an HTTP JSON-RPC method.