What’s new in ZeppelinOS 2.4
Here you will find all the major new features shipped in version 2.4. Check out the changelog for a more detailed list of what has changed since 2.3.
While in 2.3 we focused on improving the ZeppelinOS inputs, by implementing friendlier interacting commands, in 2.4 we focused on improving its outputs. We removed much of the verbosity that plagued the CLI, and show you only what actually matters. We also integrated the awesome spinnies library for presenting long-running operations.
If you miss having the CLI filling your terminal with lots of output, you can bring back the old mode (with even more info!) by using the
--verbose flag in any command.
You can now run ZeppelinOS without depending on truffle. Version 2.4 ships with a new
zos compile command that will install and run
solcjs on your behalf, and compile your Solidity contracts when needed. As a bonus feature,
zos will check if there is a
solc on your
zos compile follow the same format as truffle’s.
zos init will now create a framework-independent
networks.js file with the description of the network connections for your project. The format is similar to that of
truffle-config.js, with an additional
protocol key that allows you to specify whether you want to connect to your node via
Of course, ZeppelinOS remains fully compatible with truffle. If the CLI detects a
truffle(-config).js on your project root, it will still rely on truffle for compiling your contracts, and will load the networks configuration from truffle as usual.
You can try out the following commands:
zos balancequeries the balance of an account, either in ETH or in an ERC20
zos transfersends funds from one of your accounts to another
zos callexecutes a constant method in one of your contracts, and returns the value
zos send-txsends a transaction to one of your contracts, and returns the events
We have added experimental support for EIP1167 minimal proxies. These proxies rely on the same delegatecall pattern as the usual ZeppelinOS proxies, but have two main differences:
They cannot be upgraded to a different version of the code
They are incredibly cheap to deploy: about 1/10th of the standard proxy!
These features make minimal proxies an ideal choice when you want to spawn many copies of the same contract, without worrying about maintaining them in the future. They also play nicely with EVM packages: since the package developer pays the deployment cost of the logic contracts, you only need to pay for the minimal proxies.
You can try deploying one of these proxies by adding the
--minimal flag when running
zos create. Remember that these proxies will not be upgradeable to a different version of the code: the reduced deployment gas fee comes at a cost!