Evidently the “pockets” parameter will not be acknowledged by the “load_wallet” technique within the context of the JSON-RPC name you’re making.
One resolution may very well be to cross the pockets path as a command-line argument when beginning the JSON-RPC server. For instance, if you’re utilizing Electrum, you possibly can begin the server with the next command:
electrum --testnet --rpcuser= --rpcpassword= --rpchost=localhost --rpcport=8000 /electrum/testnet/wallets/orders001
This command begins the Electrum server in testnet mode and specifies the pockets path because the final argument.
As soon as the server is operating, you can also make JSON-RPC requests to it with out together with the “pockets” parameter within the payload. The server ought to routinely load the pockets specified within the command-line argument.
Alternatively, you possibly can strive utilizing the “load_wallet_file” technique as a substitute of “load_wallet”. In line with the Electrum documentation, “load_wallet_file” takes a single argument, which is the trail to the pockets file. Right here is an instance payload:
{"jsonrpc":"2.0","id":"check","technique":"load_wallet_file","params":["/electrum/testnet/wallets/orders001"]}
Word that the pockets path is handed as an array component within the “params” subject, not as a separate “pockets” parameter.
