balsoft/ligo
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fill in empty sections of Tezos-specific function page

Browse Source
This commit is contained in:
John David Pressman 2020-01-17 23:19:49 -08:00
parent 1d485b0242
commit dea98d408c
1 changed files with 12 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
gitlab-pages/docs/language-basics/tezos-specific.md
View File

@ -12,8 +12,7 @@ Michelson provides the `PACK` and `UNPACK` instructions for data serialization.
`PACK` converts Michelson data structures to a binary format, and `UNPACK` `PACK` converts Michelson data structures to a binary format, and `UNPACK`
reverses it. This functionality can be accessed from within LIGO. reverses it. This functionality can be accessed from within LIGO.
> ⚠️ There should be a message here about the dangers of using `UNPACK` on untrusted > ⚠️ An `UNPACK` isn't *quite* an `eval`, but it should be kept in mind that if you're deserializing untrusted input certain types could be problematic. If you deserialize an `operation` from an untrusted source and then execute it, [you are running eval on user input](https://nedbatchelder.com/blog/201206/eval_really_is_dangerous.html).
data, perhaps about executable code?
<!--DOCUSAURUS_CODE_TABS--> <!--DOCUSAURUS_CODE_TABS-->
@ -43,6 +42,11 @@ let id_string = (p: string) : option(string) => {
## Hashing Keys ## Hashing Keys
It's often desirable to hash a public key. In Michelson, certain data structures
such as maps will not allow the use of the `key` type. Even if this weren't the case
hashes are much smaller than keys, and storage on blockchains comes at a cost premium.
You can hash keys with the `key_hash` type and associated built in function.
<!--DOCUSAURUS_CODE_TABS--> <!--DOCUSAURUS_CODE_TABS-->
<!--PascaLIGO--> <!--PascaLIGO-->
@ -81,9 +85,12 @@ let check_hash_key = (kh1_k2: (key_hash, key)) : (bool, key_hash) => {
## Checking Signatures ## Checking Signatures
> ⚠️ There is no way to *generate* a signed message in LIGO. This is because that Sometimes a contract will want to check that a message has been signed by a
would require storing a private key on chain, at which point it isn't very private particular key. For example, a point-of-sale system might want a customer to
anymore. sign a transaction so it can be processed asynchronously. You can do this in LIGO
using the `key` and `signature` types.
> ⚠️ There is no way to *generate* a signed message in LIGO. This is because that would require storing a private key on chain, at which point it isn't very private anymore.
<!--DOCUSAURUS_CODE_TABS--> <!--DOCUSAURUS_CODE_TABS-->