Search for a command to run...
Series
In this series, I'll be highlighting and examining some Solidity Smart Contract Security Vulnerabilities, and Vectors. As you read, please remember to comment and share. Let's go 馃殌
Callback functions play a vital role in Solidity, allowing functions to communicate and exchange data within a smart contract. However, their misuse can lead to unforeseen consequences and potential security vulnerabilities. In this article, we explo...
A timestamp dependence vulnerability in a smart contract occurs when the smart contract relies on the block timestamp value that is generated by the node executing the smart contract to run a function when a transaction is mined. This can lead to une...
What is Tx.origin? In Solidity, Tx.origin is a global variable that returns the address of the account that originated the transaction. In other words, it is the address of the account that sent the original transaction that led to the execution of t...
Any unknown visibility type of a function was set to public visibility type in older versions of the Solidity compilers. However, in more current versions, visibility type of the function must be specified in order to avoid the compiler throwing an e...
The distributed ledger of the blockchain does not instantaneously update with new transactions. They are gathered into blocks and only added to the ledger as a part of these blocks. A malicious node can view the transaction, determine its purpose, an...
In the previous article, we talked about outdated Solidity compiler versions and their vulnerabilities. Floating pragma vulnerabilities are related to it because it still has to do with the Solidity compiler version. What then is Floating pragma? Flo...
