You’ve just finished the development of your smart contract and you’re ready to release it for the whole world to use. But before you do, take a step back and make sure you have all the bases covered. Deploying your contract to production is a big step with (literally) a lot at stake and can be a scary and daunting task. Especially in the blockchain world, where one regularly reads about smart contract hacks involving millions of stolen funds.
That’s why we’ve put together a checklist on things you should do before releasing your smart-contracts.
Make sure that your contract follows coding best practices. This usually leads to cleaner code which in return leads makes spotting bugs easier. …
You’ve sat down at your terminal, opened up a terminal and are ready to start debugging your new smart contract.
You type in
nodeos, hit Enter and then see those cryptic words every EOSIO smart contract developer who has ever played around regularly with nodeos dreads:
nodeos replay required
Or, my personal favourite:
nodeos database dirty flag set
What in the….? You think. Why is the database dirty?
You start Googling and going through EOSIO Dev Telegram posts for a solution, all the while wondering how it suddenly became your job to be a part-time BP!
You figure out how to clean your dirty database, which will probably require you to completely wipe your local test net and reinitialise the state of your smart contract and all your local system contracts. And eventually you get your tests running. …
EOSIO software developer Block.one announced today that it has awarded Klevoya with a $50k grant to further develop it’s smart contract verification system and foster the adoption of blockchain technology.
“At Klevoya we know that building quality dApps is complicated. So we made it our mission to help EOSIO dApp developers ship bug free, secure code. With the support from the EOS.VC grants program, we will increase the number of vulnerabilities that our Inspect smart contract analysis tool can detect,” said Moti Tabulo, Founder of Klevoya. “Developers who are using Inspect and Hydra, our smart contract execution environment, have found that checking for bugs in their smart contracts is not the painful experience it used to be,” he added.
Originally published at https://klevoya.com on May 28, 2020.