Sendtoaddress does not set the transaction message

[tomasbrod]

No description provided.

[iFoggz]

I fail to see what you mean? are you referring to the comment and comment-to these were never intended to be in transaction. they are just for local reference for yourself. bitcoin does the same as well. thou I don't see why we cannot add another field if you'd like a tx message sent with transaction

[tomasbrod]

I know that one of them is for local reference only, but wasn't the other intended to be in transaction?

[barton2526]

@denravonska Can we please move this to a milestone? The issue keeps coming up and needs to be fixed.

[jamescowens]

I am assigning this to Denise.

[satonakamo]

i would like to offer a bounty of 2500 GRC payable to whomever submits the first working solution to the repository.

[barton2526]

@denravonska please add bounty tag

[denravonska]

comment and comment-to are both just stored as text with the transaction. The intent is that comment be used to store what the transaction is for, and comment-to be used to store the name of the person or organization to which you're sending the transaction.

@satonakamo Do you want to include a message as well?

[satonakamo]

@denravonska actually that's is the only thing I want, the message in the hashBoinc field of the transaction. Thanks for looking into it.

[jamescowens]

I don't think we want that in the hashBoinc field. On Sat, Feb 09, 2019 at 09:52 AM, satonakamo wrote: @denravonska <https://github.com/denravonska> actually that's is the only thing I want, the message in the hashBoinc field of the transaction. Thanks for looking into it. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1346 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHLi4tBp5s-GrkmQzNgdQGz35f1k9J9wks5vLuCYgaJpZM4X893n> .

[satonakamo]

how do you mean? as far as I can see the hashBoinc field is where messages go, or am I mistaken

{"txid":"71fc138fc315c11da5a8a2171d468ec8bb78a587213499b6dde440dea6c39553","version":1,"time":1549318857,"locktime":0,"hashboinc":"<MESSAGE>49 0 #7a02ec</MESSAGE>","vin":

ok maybe I should clarify further: I am interested in being able to set the message field from the RPC command sendtoaddress. I am not proposing that the comment and comment-to be entered into the hashBoinc field.

[denravonska]

@jamescowens That is how we send messages. It seems like the only way to send messages now is by using the Qt UI.

[jamescowens]

Looking at the code you are right. Let’s just wire it up in the rpc command.

…

Sent from my iPhone

On Feb 9, 2019, at 11:45 AM, Marco Nilsson ***@***.***> wrote: @jamescowens That is how we send messages. It seems like the only way to send messages now is by using the Qt UI. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[denravonska]

@satonakamo Would an additional message argument be sufficient for you?

[satonakamo]

@denravonska yes, thank you very much.
can you claim the bounty from bountysource?

[denravonska]

@satonakamo I can claim it when #1400 is accepted and this issue is closed.