EOS.IO Stack Exchange is a question and answer site for users and developers of distributed applications built on top of the blockchain operating system, EOS.IO. It only takes a minute to sign up.
Sign up to join this community
I have a bunch of user data and I want to store it in the EOS blockchain. Each user data doesn't exceed 1kb. At most it is just: name, phone, email, btc address, and btc private key (encrypted).
I currently have this data in mysql database and I'd like to migrate it to EOS.
Don't store personal information like email-addresses or phone-numbers on a public blockchain !!!
The memo-field itself has nothing to do with the type of storage as it's just an action-parameter of type string which doesn't say anything about the type of storage used.
Please follow the Data Persistence , Address-Book-Tutorial. It will also teach you the difference between the different storage-variants and how a typical memo-field works. Choosing the right type of storage for your application depends on the use-case and application-architecture.
There are several different ways to receive the data - public rpc-endpoints, dfuse, openapi, running your own node etc. What to choose depends on the use-case and your application-architecture.
