Cudos Blast Release v2.1.0

Release notes

Release v2.1.0 includes the following changes:

Added:

• Ability to define customs tasks and custom commands. More information can be found in the documentation.
• Introduced gas limit and gas multiplier.

Improved:

• Documentation updated and improved.
• Improvements in gitignore file.
• Improved custom error handling.
• Improved contract funding at deployment time. More options are now added.
• Other small improvements and changes.

Cudos Blast Release v2.0.0

Release notes

Release v2.0.0 includes the following changes:

The release will include breaking changes. Guide how to migrate to v2.0.0 can be found below

Added:

• Ability to use console.log in JEST unit tests
• Ability to handle future plugins install
• options object introduced
• bre object introduced

Improved:

• Documentation Updated
• Improve contract deploying and instantiating
• Cudos-noded version update to latest - v1.0.0 mainnet release
• Project structure is improved
• Smart contract template is updated and improved
• Cosmswasm dependencies version updated

Migrate from v1 to v2

In order to migrate properly the following changes must be applied in all users scripts (test files, deployment scripts, etc)

• getSigners() is now unavailable in the global scope. It can be accessed through bre object. If a non-local network is used, getSigners() now returns accounts from private-accounts.json
  getSigners() —> bre.getSigners()
• getCustomSigners() is removed. Use getSigners() instead.
  const {account1: privateAccount1} = await getCustomSigners() —> const [alice] = await bre.getSigners()
• getContractFactory() is now unavailable in the global scope and does not accept signer as parameter. The function is available in bre object.
  getContractFactory("myLabel", alice) —> bre.getContractFactory("myLabel")
• getContractFromAddress() is now unavailable in the global scope and does not accept signer as parameter. The function is available in bre object.
  getContractFromAddress("cudos1uul3yzm2lgskp3dxpj0zg558hppxk6pt8t00qe", alice) —> bre.getContractFromAddress("cudos1uul3yzm2lgskp3dxpj0zg558hppxk6pt8t00qe")

Contract object functions

• Contract object no longer saves deployer. Default signer is now always the first one returned by getSigners(). All functions that pass signer are affected by this change: deploy(), execute(), query()
• deploy function now introduces new parameter options instead of signer. The signer obeject can have the following fields:

options: {
	signer: <signer>,
	funds: <coins>,

}

• contract.deploy(): The way parameters are passed in changed, label parameter is now mandatory and initTx in the returned object is renamed to instantiateTx

const {initTx} = contract.deploy(msg, alice, "label", 123) —> 
const {instantiateTx} = contract.deploy(msg, "label", { signer: alice, funds: 123})

Cudos Blast Release v1.0.2

Release v1.0.2 includes the following changes:

Added:

• Ability to fund contracts on deployment time
• Allow users to use external libraries in custom scripts
• Added --network optional parameter to run, test, node status commands

Improved:

• Fix GitHub vulnerabilities
• Improve project testing
• Improve the accounts.json file. The file is currently read-only, in order to avoid any issues
• Simplify the .connect functionality and provide ability to easily change singers
• Fixed issues with node status

Removed:

• Removed the default network option

Cudos Blast Release v1.0.1

Release 1.0.1 includes the following improvements and changes:

• Improved error handling on for running local node and script files
• Improved integration tests (improved performance and increase coverage)
• Added ESLint checks which will help for future community contribution
• Improve test commands - Better naming and experience for better user experience
• Fixed repository vulnerabilities (reported from bots for packages versions)
• Improved documentation
• Performance and usage improvements

🚀

Cudos Blast Release v1.0.0

This the first official release of the Cudos Blast 🚀 .

More information about the development framework can be found in the README file.