Hot answers tagged

8

So this is a huge question and I think there are many people more qualified than me, but I'll offer some initial guidance. In Software Foundations, a book on Coq, they talk about an implied language called Imp. Imp has a syntax like: Z ::= X;; Y ::= 1;; WHILE ~(Z = 0) DO Y ::= Y * Z;; Z ::= Z - 1 END Which should be somewhat easily understood as ...


7

If you plan to write Smart Contracts, using Liquidity is often simpler than Michelson: http://www.liquidity-lang.org/


7

The key_hash is just the address, which is derived from hashing the key. So if you have the key, you can easily generate the key_hash/address. The reason you may want the key is because you need this to verify a signature signed by the private_key, which can be used in multiple ways within a dapp/smart contract (one example is a smart-contract based multi-...


6

If we agree that the purpose of analyses is to both prove properties and help users of smart contracts to understand them, I would say: Values: studying what values each element of the storage can take in the future. Effects: studying what effects can occur in the future: typically what transfers can occur and on what conditions. Ownership: who can trigger ...


5

As of Taquito release v6.1.0-beta.0 Taquito offers a new API for Maps which support pairs as keys in Maps and BigMaps. Here's a link to documentation & examples on Accessing Map values using Pairs


5

There are several useful Tools/SDKs, this are some that come to my mind: https://github.com/TezTech/eztz https://github.com/maht0rz/tezos-environment-manager https://github.com/keefertaylor/tezoskit https://github.com/LMilfont/TezosJ https://github.com/mscappini/Tz.Net


4

Here is a link to a guide from reddit on how to set up a development environment using a localhost instance of a Tezos network and emac. https://medium.com/tezsure/setting-up-a-development-environment-for-tezos-36f86c382484


4

The contract you point to takes a single parameter of type address. Thus, as you write, it only has the default entrypoint. In taquito, the main entry point can be call through contract.methods.main. So your call should be: contract.methods.main(contractAddress).send()


1

Taquito return an operation object for each operation you inject using it. For instance if you do: const op = Tezos.contract.transfer({to: address, amount: 1}) You can wait until the confirmation with await op.confirmation(); Or op.then(() => { // post operation logic here })


1

Apparently Galleon just added support for calling contracts 🎉 Seems like this is something most wallets has not gotten around to yet. I will encourage anyone who stumbled across one that support it to add a comment to this answer with a link 😬🙌 Thanks!


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