MacBobby Chibuzor
Jun 17, 2022 ⋅ 11 min read

Smart contract development: Common mistakes to avoid

MacBobby Chibuzor Go, Solidity, and Haskell developer interested in the cloud native world and blockchain technology. A fanatic for technical writing and open source contribution.

Recent posts:

Using CRDTs To Build Collaborative Rust Web Applications

Using CRDTs to build collaborative Rust web applications

CRDTs, or conflict-free replicated data types, is a concept that underlies applications facing the issue of data replication across a […]

Mario Zupan
Feb 23, 2024 ⋅ 15 min read
Guide to Using TensorFlow in Rust

Guide to using TensorFlow in Rust

We explore the fusion of TensorFlow and Rust, delving into how we can integrate these two technologies to build and train a neural network.

Rosario De Chiara
Feb 22, 2024 ⋅ 8 min read
Using Signaldb With React

Using SignalDB with React: A complete guide

SignalDB enables automatic data synchronization between your components and a local in-memory or persistent database.

Antonello Zanini
Feb 20, 2024 ⋅ 6 min read
Guide To Next Js Layouts And Nested Layouts

A guide to Next.js layouts and nested layouts

Understanding how layouts, nested layouts, and custom layouts work in Next.js is crucial for building complex, user-friendly projects.

Ibadehin Mojeed
Feb 19, 2024 ⋅ 12 min read
View all posts

3 Replies to "Smart contract development: Common mistakes to avoid"

  1. Thanks for the good overview, although I cannot quite get the race conditions example. In smart contracts you cannot call anything simultaniously, Transactions and functions calls are atomic, so you cannot put the transfer call within the withdrawal call. Once withdrawal finishes the balance is updated. Please, let me know if I am wrong

  2. It’s somewhat concurrent. The withdrawBalance function starts, then in-between, the transfer function is run. When the transfer function ends, the withdrawBalance function continues and then end. Because the withdrawBalance function hasn’t updated the state, it could give the user more than the coin/money.

    Liken it to running a function inside the main function in Rust or Go.

  3. This insightful article highlights common mistakes to avoid in smart contract development – it reinforces the importance of metaverse training to ensure robust and secure implementations.

Leave a Reply