Hot answers tagged

1

I would like to clarify some of the beacon behavior. The main responsibility of beacon is establishing and maintaining a communication channel between a dApp and a wallet. Beacon itself does NOT do any type checking or error handling regarding the contents of the tezos operations. The operations are sent to the other side as is, without any changes or error ...


1

Did you try value: { "int" : "10000" }? It seems that: the field value in parameters should be micheline (seeing how Unit is expressed) the entrypoint %stake has type nat (the linked contract says (nat %stake) in the parameter type) the Micheline encoding of the nat 10000 is {"int": "10000"} (this can be verified by ...


1

I suspect you are using Taquito's Contract API, but the Wallet API should be used to interact with a wallet. For example: const contract = await tezos.wallet.at(contractAddress); Instead of : const contract = await tezos.contract.at(contractAddress); More details on the wallet API here: https://tezostaquito.io/docs/wallet_API#calling-a-smart-contract


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