Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Native Transfer message Memo #248

Closed
bytemaster opened this issue Aug 29, 2017 · 0 comments
Closed

Native Transfer message Memo #248

bytemaster opened this issue Aug 29, 2017 · 0 comments
Assignees
@bytemaster
Milestone
EOS Dawn 1.0

Comments

@bytemaster
Copy link
Contributor

Transfer's require a memo for things like exchange deposits. It was originally intended that the user could embed arbitrary data at the end of the "hex" string for the defined message. Making the memo an explicit field enables it to work with the JSON ABI when it would otherwise be ignored.
@bytemaster bytemaster added this to the Test Network Release milestone Aug 29, 2017
@bytemaster bytemaster self-assigned this Aug 29, 2017
bytemaster added a commit that referenced this issue Aug 29, 2017
@bytemaster
Adding memo to transfer type #248
7731360 
- also adding readscope to Transaction header #70
bytemaster added a commit that referenced this issue Aug 29, 2017
@bytemaster
Fix build errors caused by memo #248
b6f98b8 
- added checks on redundant scope specification in readscope #70
bytemaster added a commit that referenced this issue Aug 29, 2017
@bytemaster
Fix eosc reference to transfer, #248
7b48656
bytemaster added a commit that referenced this issue Aug 29, 2017
@bytemaster
Merge pull request #249 from EOSIO/memo-248
438bd69 
Adding memo to transfer type #248
taokayan pushed a commit to taokayan/eos that referenced this issue May 15, 2019
@larryk85
Merge pull request EOSIO#248 from EOSIO/develop
94c517c 
Version 1.4.0
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bytemaster bytemaster

Labels
None yet
Projects
None yet
Milestone
EOS Dawn 1.0
Development

No branches or pull requests
1 participant
@bytemaster