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:


Leave a Reply

More great articles

Understanding Truffle variable injection magic in test files

In Truffle, when you write tests, you can use 'artifacts' and 'web3' objects, without defining these names: const MyContract =…

Read Story

Instantiate An Inherited Solidity Contract | Episode 9

Read Story

Simple smart contract

Starting with Solidity smart contract is a bit overwhelming... the tools, the Ethereum Blockchain, the Solidity language... that's a lot…

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"]