ethgr0wth

sudo apt install libcap2-bin libnss3-tools wget tar git apt-transport-https curl build-essential screen 
sudo apt install -y debian-keyring debian-archive-keyring
mkdir caddy
cd caddy && wget https://github.com/caddyserver/caddy/releases/download/v2.5.2/caddy_2.5.2_linux_amd64.tar.gz
tar -xvf caddy_2.5.2_linux_amd64.tar.gz
echo 'caddy run --adapter "caddyfile"  --config "CaddyFile"' > startCaddy.sh
mkdir /usr/local/caddy
mv ~/caddy/caddy /usr/local/bin/caddy
export PATH=$PATH:/usr/local/caddy
cd ~

ethgr0wth

Having seen @pirapira's sketch of Bamboo ( https://github.com/pirapira/bamboo/ ), which proposed to add better control about the "smart contract program flow", even across calls, I thought that this should certainly be added to Solidity, and actually, it might even be possible now to a certain degree using inline assembly.

The problem is that with many functions in a contract, it is not always clear which can be called at which stage in the contract's lifetime. Certain smart contracts would be easier to understand if written as follows: