4

In the documentation on https://tezos.gitlab.io you will find: https://tezos.gitlab.io/introduction/howtouse.html: a description of what Tezos does at a high level under the form of an introductory tutorial targetted at new Tezos users. In https://tezos.gitlab.io/whitedoc/the_big_picture.html: the organisation of the code base. In the rest of the "...


3

As said in the glossary, tz accounts are called "implicit accounts" and KT1 accounts are called "originated accounts" or "smart contracts" (these two expressions are synonyms since Babylon).


3

You actually answered the question in the comments, but for those who don't read comments: There are two limitations: max_operation_data_length: 16384 bytes hard_storage_limit_per_operation: 60000 bytes This means that you can't send more than ~16KB per transaction, so the only way is to split the "really long string" into chunks and store those ...


2

You shouldn't do it. It's very expensive and a total waste of resources. What you can definitely do is store a hash of your string or a ipfs address for example (which is more or less the same).


Only top voted, non community-wiki answers of a minimum length are eligible