-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation for working with the Tezos Blockchain #1412
Conversation
Signed-off-by: Dzianis Andreyenka <[email protected]>
Signed-off-by: Dzianis Andreyenka <[email protected]>
Signed-off-by: Dzianis Andreyenka <[email protected]>
Signed-off-by: Dzianis Andreyenka <[email protected]>
Signed-off-by: Dzianis Andreyenka <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #1412 +/- ##
=======================================
Coverage 99.98% 99.99%
=======================================
Files 321 321
Lines 22960 23027 +67
=======================================
+ Hits 22956 23025 +69
+ Misses 2 1 -1
+ Partials 2 1 -1 |
Signed-off-by: Dzianis Andreyenka <[email protected]>
As we know from the previous section - smart contracts on the Tezos blockchain are using the domain-specific, stack-based programming language called [Michelton](https://tezos.gitlab.io/active/michelson.html). It is a key component of the Tezos platform and plays a fundamental role in defining the behavior of smart contracts and facilitating their execution. | ||
This language is very efficient but also a bit tricky and challenging for learning, so in order to teach FireFly how to interact with the smart contract, we will be using [FireFly Interface (FFI)](../../reference/firefly_interface_format.md) to define the contract inteface which later will be encoded to Michelton. | ||
|
||
The following FFI sample demonstrates the specification for the widely used FA2 (analogue of ERC721 for EVM) smart contract: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we put the FFI for the sample "Simple Storage" contract that the rest of the tutorial uses here instead of the FA2 contract?
It seems like we're missing the step where we generate the contract interface in this guide.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FFI for tezos smart contracts is not generated and it needs to be build manually, as well as for Fabric chaincode.
I used the example of the FA2 contract, since it covers most of the different data types and it is better to rely on it when building FFI for your own smart contract.
Later I plan to add an additional doc section for building FFI for tezos smart contracts with a review of all supported types and examples.
Co-authored-by: Nicko Guyer <[email protected]> Signed-off-by: Dzianis Andreyenka <[email protected]>
Co-authored-by: Nicko Guyer <[email protected]> Signed-off-by: Dzianis Andreyenka <[email protected]>
Co-authored-by: Nicko Guyer <[email protected]> Signed-off-by: Dzianis Andreyenka <[email protected]>
Co-authored-by: Nicko Guyer <[email protected]> Signed-off-by: Dzianis Andreyenka <[email protected]>
Co-authored-by: Nicko Guyer <[email protected]> Signed-off-by: Dzianis Andreyenka <[email protected]>
Co-authored-by: Nicko Guyer <[email protected]> Signed-off-by: Dzianis Andreyenka <[email protected]>
Co-authored-by: Nicko Guyer <[email protected]> Signed-off-by: Dzianis Andreyenka <[email protected]>
Co-authored-by: Nicko Guyer <[email protected]> Signed-off-by: Dzianis Andreyenka <[email protected]>
Co-authored-by: Nicko Guyer <[email protected]> Signed-off-by: Dzianis Andreyenka <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this!
No description provided.