Reprise:`issue_send_tx` equivalent in the V2 wallet API

[grin-user1]

Yeastplume provided instructions for getting a V2 wallet to behave in the same was as a V1 wallet here:

`issue_send_tx` equivalent in the V2 wallet API

The issue_send_tx in the original V1 API essentially did too much, creating a (sender-initiated only) transaction and posting it via HTTP all in in one go. In the V2 API, this was broken up into more granular API functions. You can replicate this functionality in the V2 API by providing a send_args parameter in the call to the V2 init_send_tx as follows: { "jsonrpc": "2.0", "method": "init_send_tx", "params": { "args": { "src_acct_name": null, "amount": "1000000000", …

However, when I add the send_args parameters as he suggests, I get this error:

{
“id”: 1,
“jsonrpc”: “2.0”,
“result”: {
“Err”: {
“ClientCallback”: “Other wallet is incompatible and requires an upgrade. Please urge the other wallet owner to upgrade and try the transaction again.”
}
}

I’m confused how this is possible since the V2 wallet is, I presume, communicating with itself here. Can someone explain this to me?

Here’s the full call:

curl -H “Content-Type: application/json” --data “{"jsonrpc":"2.0","method":"init_send_tx","params":{"args":{"amount":"100000000","minimum_confirmations":10,"max_outputs":1,"num_change_outputs":1,"selection_strategy_is_use_all":false,"message":null,"target_slate_version":null,"send_args":{"method":"http","dest":"http://127.0.0.1:3420","finalize":true,"post_tx":true,"fluff":true}}},"id":1}” -u grin: localhost:3420/v2/owner

[grin-user1]

Follow up question: looking at api/src/owner.rs, is it correct to assume that “file” is no longer a supported payment method? (the code makes it look like only “http” and “keybase” are now supported)