iotaledger
Selected node should be saved
Actual behavior:
- The set node with the
nodecommand is only selected for the time the application is running - If you exit the application and start it again the node is set to the default
http://localhost:14265
Better behavior:
- If you set a node through the
nodecommand it should be stored - After restarting the application should use the stored node
Hi @mark-bradshaw, thanks for sharing. cannot figure out how to use the remote option, the instructions are unclear; Nevertheless, if I want to connect to a cloud server (eg/ http://iotanode.party:15265, and not a local one), I apparently just need to use the node command and all seems fine, I wanted to send zero iota transfer (legit, I had to mod transfer.js for that) but at some point error msg says :
One moment while the transfer is made. This can take a few minutes. Error: Request Error: COMMAND attachToTangle is not available on this node
which is weird, I used this node succesfully (for zero coin transfers) with https://github.com/alero3/IotaMessageSender and https://github.com/dsir-minute/IotaMessageSender2 Any comment ? Cheers.
@dsir-minute Your comment doesn't belong in this issue. This is an enhancement request for the node command to autosave as default when changed and has nothing to do with what you're experiencing.
Your problem is the message senders you linked to use Local PoW to perform the transaction signing. The cli-app does not do local PoW. The node you selected http://iotanode.party:15265 does not allow remote PoW. If you want to send zero value messages with the cli-app you still need to do PoW and you need to use a remote server that allows for that. http://nodes.iota.fm:80 will allow for this for example.
Working on this by the way, need to tidy some code up but did some stuff with the node command, including accepting user:pass in the url as well as cleaning up the initial connecting and changing logic a touch.
@plenarius , sorry to piggy back the initial "save node" request. thanks for the answer explaining my user experience with 0 value transfers to non Pow-able nodes.