phyro

David is right. The method has been deprecated and removed from [ListenArgs](https://github.com/mimblewimble/grin-wallet/blob/master/controller/src/command.rs#L195). I think we can safely remove all the args in the [grin-wallet/src/bin/grin-wallet.yml](https://github.com/mimblewimble/grin-wallet/blob/429db61bb7ef42f009abb8886fd90221301dfc74/src/bin/grin-wallet.yml#L59-L67) because we never parse these as...

I very much agree the optimal is to have a single reliable source in this case. Perhaps one thing to note is that maybe there are links to wiki page...

@antiochp @quentinlesceller do you guys think this one is good to merge?

alright, @antiochp @quentinlesceller could one of you two also give it a quick look now and merge if it looks good?

It seems the question is whether you want atomicity of a request or you want to make it have multiple rounds. A couple of questions come to mind for interactive...

@Giszmo this specific case is not safe. Consider you have a pubkey `A`. I could forge the signature with ``` pubkeys: [A, -A+x*G] ``` If you sign the sum of...

@fiatjaf I think this solves my concurrency questions if it's done strictly before you start doing other requests. Some other questions apply thought i.e. do you want a session/token model...

@Giszmo I see, then it doesn't really introduce state :+1: Regarding key aggregation, note that I spelled out the pubkeys as well `pubkeys: [A, B]`, the second pubkey just happens...

Are there any updates to the proposal? if yes please update it when you find the time, thanks! :+1:

Just a note for whoever tackles this: https://medium.com/etcdev/geth-classic-v5-2-introducing-geth-getaddresstransactions-133c76fa82d1 Seems like querying the transactions is now easier from geth (i'm not sure if this always queries the node or has information...