I was doing a deep dive to understand what is happening with IPFS and Filecoin and how Filecoin uses IPFS in reality.

I wanted to know if it is worth it to make a lookup for the whole struct and parse info from it or to always get single values with getters from it to optimize. So the value of gas needed for most single lookup is around 2900 gas or less. But the value for the whole struct lookup is 9861 gas, which means that if the lookup is using less than 3 values it’s more worth it to do a single lookup for each value in a struct. This changes as the stuct is larger, if there are more values in it then it’s less worth it to do a lookup of the whole struct and more sense to do lookup for just one value whish is kind of obvious.

Warning, this post is only useful if you tried out adding liquidity both with UI and with code, read about V3 most of the info, and want to have more clearer idea of what is what.

I was getting this error on a custom cluster with the geth node

I am sure many of you had a similar experience when you were about to sign something online and you were not sure what you were signing and how secure it is. Many websites today ask you to sign a message when just logging in to dapp. Sometimes it shows you some message you are about to sign in clear format but sometimes it’s just some random hex values and you are not sure what you are signing. So I wondered how secure or insecure that is and what are we doing by signing some messages.

This is more a note to myself as to when is transfer used and when is transferFrom and that with transferFrom you need to have approval of token transfers and for just pure transfer its not needed.

Here are some quick snippets that help when you want to get info from Blockchain.

Similar to what we did for Uniswap V2 on how to find address of smart contract pool that will be generated we can do the same for V3

As this topic is very familiar with what I do and I saw a lot of misinformation I have an urge to explain this a bit.