fbpx

Debugging calls vs transactions

Julien Klepatch

When I started to debug Solidity smart contracts, I was really confused by the fact that although there was a return statement in Solidity, I could not always read returned values when triggering functions from outside the smart contract. I was confused because I didn’t know that Ethereum has 2 APIs (calls and transactions) for interacting with smart contracts: calls and transactions.

In this video, I will explain what are calls vs transactions and why it matters when debugging Solidity smart contracts:

0 Comments

Leave a Reply

More great articles

Debugging with events

Do you like often use console.log() statement to debug your Javascript code? Convenient, uh? How about Solidity smart contracts, can…

Read Story

Ether wallet – Part I

In this video, we will start to code a wallet for Ether, using a Solidity smart contract. You will learn…

Read Story

ToDo List Ethereum Dapp (Step5) | Build a smart contract client with Truffle Contract

This tutorial is part of the series ToDo List Ethereum Dapp. It is the Step 5. Tutorials already published: (more…)

Read Story

Never miss a minute

Get great content to your inbox every week. No spam.
[contact-form-7 id="6" title="Footer CTA Subscribe Form"]
Arrow-up