When I have a object of type ContractAbstraction<ContractProvider>, I can get a key/value map of all the endpoints in the deployed contract like this: const contract: ContractAbstraction<ContractProvider> = client.contract.at(this.state.contractAddress); where
When a smart contract is deployed it gets an address. How is this address of the "originated account" calculated?
I am stuck when getting Tezos from faucet https://faucet.tzalpha.net/ : ./tezos-client activate account bob with tz1YdaJWrDdHz4qfVEhPEs7f5EBy4DE2Fzv1.json Disclaimer: … Error: Unrecognized command. Try using the man command to get more information.
Are there multiple ways to write comments in LIGO? I think it makes code more readable if I can for example divide the code into various parts using comments. How
I am using the tezos-sandbox cli and trying out packing/unpacking data. I want to try doing the equivalent of sp.unpack(x, t = …), specifying a type to unpack into, using
To which extend can bakers manipulate the timestamp Michelson uses for NOW? I am not really sure how this value is provided to the smart contract and how reliable/unreliable it
When is the Tezos mainnet expected to switch to Delphi? Is there anything that node owners should do in anticipation?
Context: I Created a Tezbox Wallet in July 2018 with XTZ from my ICO wallet and began delegating. Since then, I have logged into this wallet several times but never
I have this parameter for a function: type modify_list is | Add of list(address) | Remove of list(address) type modify_list_michelson is michelson_or_right_comb(modify_list) When I try to supply the parameter in