Iteration Three

By Oliver Jumpertz

Iteration Three - There Is Smart Contract Development And There Is Smart Contract Development





Subscribe to our newsletter

By subscribing, you agree with Revue’s Terms of Service and Privacy Policy and understand that Iteration Three will receive your email address.

Iteration Three
Iteration Three - There Is Smart Contract Development And There Is Smart Contract Development
By Oliver Jumpertz • Issue #8 • View online
Issue number 8! Wow, amazing how time passes.
This time, you’ll get a few valuable insights into smart contract development and a few techniques and advanced concepts any smart contract developer needs to learn at some point. Next to that, we take a quick look at the crypto market.
Additionally, I’m happy to show you two new articles I released this week and introduce you to my latest Twitter series. And if that is not enough for you, you might like this week’s learning resource of the week.
Enjoy going through this newsletter; you will definitely find something useful in it for you.

There Is Smart Contract Development And There Is Smart Contract Development
Oliver Jumpertz
Learning Solidity is one thing, and it's achievable; it only takes time.

But another thing is getting good at it.

You'll need to learn:

- Cryptography
- Common patterns
- Smart Contract security
- Optimization
- UX

Only a secure and usable contract is a good contract.
I wanted to use the opportunity to iterate on this tweet of mine a little further. A tweet and even a thread can only cover so much, but a few things are usually left out. But this issue is a perfect opportunity to go even further.
Solidity itself isn’t that complex. You might not fully agree with me, but believe me: Once you are really in, you will see that most of it is just some syntax. But like any other software you can develop, it takes a little more to make it really good. Let’s go over each point individually, so you understand.
Cryptography plays a huge role at the core of a blockchain, but it also has a significant part in your day-to-day job. You always need to keep in mind that everything on a blockchain is transparent, and everyone can see data if they want to. And this leads to an interesting problem: How do you handle more private details?
The answer is relatively simple but not what you might expect. There is actually no way to reliably encrypt data within a smart contract without it being visible within the transaction. This means that you need to work together with the client. When someone calls your smart contract’s functions, sensitive information needs to be already encrypted. This is the only way to store that data so that only the rightful owner can decrypt it in the client.
Why does that affect you? Well, because it is your job to know those details, and will be your job to work this out together with the clients. As someone who learned all this, it might even be your job to implement the specific functions for your clients, so they can continue to focus on the frontend. In other circumstances, you might want to build a backend for such use cases, and that would probably also be your job to implement.
Common Patterns
Patterns help a lot in making your Solidity code more readable, secure, and probably even performant.
There are a few of those patterns that you really need to learn well. To name some of them:
  • Guard Check
  • State Machine
  • Oracles
  • Access Restriction
  • Checks Effects Interactions
  • Pull over Push
  • Emergency Stop
  • Proxy Delegate
  • Eternal Storage
  • String Equality Comparison
  • Tight Variable Packing
  • etc.
Those are some pretty fancy names, but in the end, they only represent a particular style of doing things in Solidity. A guard check, for example, is nothing else than a pattern to use the require() function as early as possible in a function call to ensure that user input is correct.
It takes some time to learn them really well, but when you know them, you’ll be able to read Solidity code way more efficiently and make your own code more maintainable.
Smart Contract Security
It is straightforward to write Solidity code, but it can be way more challenging to write secure code.
A missing access restriction in a function is one of the more apparent flaws that can lead to a hostile takeover of your contract. It doesn’t take a seasoned Solidity developer long to spot such an issue, but an inexperienced developer might have more problems with it.
Other issues, like a reentrant attack, are way harder to spot. Calling another contract when you have problematic code placed before that call can lead to that contract calling your function again, in return leading to a loop. In one case, this led to the so-called DAO hack, where a reentrancy vulnerability cost the “DAO” (a fund) its treasury.
Learning about smart contract security is an ongoing process, and the field evolves as fast as attackers find new ways to exploit flaws in contracts. Although there are specialized smart contract auditors, having a good understanding of smart contract security as a Solidity developer definitely doesn’t hurt.
Smart contract optimization is a pretty deep field, and the harsh reality is that sometimes writing only Solidity isn’t enough. Especially on Ethereum, every gas unit saved counts (at least right now). The more gas you can save, the better for your users. And if you have dedicated backend logic calling smart contract functions, you’ll also be happy to save a few thousand dollars or even more.
Optimization efforts can begin with monitoring the gas consumption of your smart contracts with specific tools and lead to rewriting certain parts with more optimized code. And sometimes, even Solidity isn’t enough, and you will have to use Yul, the EVM Assembly flavor of Solidity. You then quickly go from writing human-readable code to placing binary instructions carefully.
At some point, every smart contract developer will probably have to learn Yul and optimization techniques. Overall, it will probably take as long to learn Yul as it took to learn Solidity.
Smart contracts are accessible by the public, but not in the sense that any backend API is accessible. It is way easier to access a smart contract on the client-side. All you need is the ABI of that contract, and off you go.
Many developers will use this to their advantage and build their own code around your contracts, which justifies taking a little more care of usability. Additionally, taking care of UX can also help you to optimize your contract. When one call is better, why make it two and let users pay their gas fee equally as often?
Sometimes, it’s just not feasible to let users call three setters in a row before they can finally call another function that contains the business logic you really need. Make it one function call in this case and help users to interact with your contracts conveniently.
Learning all this takes a lot of time, and it certainly helps to use your own contracts regularly. Start with your tests and also include end-to-end tests that model the whole user flow. This already gives you great insights into how well your contracts are really usable. From that point on, you can continue to iterate and improve the usability of your contracts step by step.
Crypto Is Back
Bitcoin 7-day chart - Source:
Bitcoin 7-day chart - Source:
Crypto is back, and not only with small green numbers but large ones. On February 4th, 2022, Bitcoin began to climb massively, evening out at around $41k. Since then, the price has moved sidewards.
Like usually, other cryptocurrencies followed Bitcoin’s trend and rose as well. For investors, this has only been a short valley, and gladly the whole ecosystem currently seems to recover.
We don’t know what follows next, but for now, it seems as if crypto could tackle the next new heights soon. Nevertheless, any new statement by the Fed or other government agencies could quickly destroy the upward trend once again.
Interestingly, the latest trend follows a statement by the Indian government to legalize crypto at a tax rate of 30% and an announcement of a digital rupee. Whether this statement is related to the latest market movements is still unclear, but we will hopefully find out this week.
For now, enjoy the new heights, and kudos to everyone who held through the valley.
New Articles By Me
The Ultimate Smart Contract Developer Roadmap - From Zero To Hero
If you subscribed to this newsletter some time ago, you might already know this roadmap. If you are new and haven’t seen it yet, it might be a worthwhile read for you if you plan to get into Web 3 as a smart contract developer with Solidity.
Create a Pack with TypeScript and Next.js
I recently had the chance to write a guide for thirdweb. The folks there approached me and asked whether I could write a guide for one of their interesting low-code modules. It didn’t take me long to say yes, and here it finally is. If you have access to thirdweb, you might love their Pack module, which is basically trading cards for NFTs.
What's Up On Twitter?
Oliver Jumpertz
💛 Web 3 - JavaScript explained 💛

ethers can dynamically create a complete API for any smart contract based on its ABI.

This does, for example, also work for ERC20 tokens. ↓
Guess what? You can currently follow my ethers series on Twitter and Instagram. Two valuable infographics each day focused on providing you with the basic use of ethers.js in JavaScript.
If you haven’t worked with ethers.js yet, definitely give it a try and follow the series. You could enjoy the library a lot.
Highlighted Learning Resource Of The Week
GitHub - ethereumbook/ethereumbook: Mastering Ethereum, by Andreas M. Antonopoulos, Gavin Wood
If there is one book I would ever recommend anyone into Web 3 to read, it would be “Mastering Ethereum.” It is not only free but also incredibly well written and valuable.
Andreas M. Antonopoulos does an incredible job at guiding the reader from the basics to more advanced concepts while even covering Solidity and Vyper.
Reading never hurts, even if you already know quite a few things. After finishing this book, you might have picked up a few more new concepts and techniques.
That's It For This Issue
This issue has now come to an end. I hope you enjoyed reading it, and that you took something worthwhile with you.
As usual, if you have any feedback, feel free to provide it. Even if you have any ideas, share them with me, I’ll do my best to find out how I can incorporate them into this newsletter.
Until then, stay safe, hodl, and go buidl some dApps!
Yours sincerely,
Did you enjoy this issue?
Oliver Jumpertz

Hey, I'm Oliver, and Iteration Three is my newsletter focused on Web 3 and me. One that I would love to get every week.

You will be kept up to date with my content, learn valuable lessons about the space, get to know important news from the space, and much more.

Prepare to get a lot of value into your inbox every Monday, 52 weeks a year.

In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue