This is possible, but not advised. If you do this, you should cast the int32 to an int256 in order to be explicit.
int32 a = 1;
int256 b = 3;
int256 c = int256(a) + b;
However, using types smaller than 32 bytes may actually be more expensive than using types that are 32 bytes exactly (such as int256, uint256, etc.). The reason for this is that the EVM ...
You can use this solution to sync the state of public ethereum chains into your local private blockchain in truffle (or embark) and then locally simulate the execution of both transactions in the correct causal order to properly estimate the gas cost.
You need to set the target gas limit in your command starting the geth network
Target gas limit sets the artificial target gas floor for the blocks to mine (default: 4712388)
If you don't do this, each time a block is published, the miner of the block moves the gas limit closer to their defined target gas limit.
Remix IDE is not authoritative. If it crashes, it's a failure of the simulation. In the end, the network block gasLimit is a hard stop. That value is voted on by miners and has been known to drop during periods of high congestion. Caution about cutting it too close.
I think you should have a look over here. https://blog.b9lab.com/getting-loopy-with-...
What is the meaning of stipend if transactions are always have gas limit set by sender?
Not really. When EOA calls contract A, the gas limit is set in the transaction, this is true. However, when contract A calls contract B, contract A may set limit on how much gas the contract B is allowed to spend. This limit may be lower than the remaining gas ...
You have to pay some gas for every byte in data field of a transaction.
After Istanbul fork new cost are given in EIP 2028
16 gas a non-zero byte (it was 68 gas)
4 gas a zero byte (it didn't change)
So if your addresses have a zero byte the transaction will be 12 gas cheaper.