Blog

Checkout Smart Contracts Security Audit Scope

Table of Contents

Read Time: 3 minutes

Our Smart Contracts Security Audit process consists of the following stages:-

Stage 1 – Specification gathering

This is the most crucial stage because the detail is key for a successful smart contract Security audit. Here we will gather the specifications from you to know the intended behavior of smart contract. In this stage, we need a summary of the intended behavior of the smart contract from your side. We would also gather specification through forms.

You can provide specification summary in the form of example image attached below:-

Stage 2 – Manual Review

Manual Review is king in smart contract auditing

Goals of manual review:-

a.) Verify that every detail in the specification is implemented in smart contract.

b.) Verify that the contract does not have any behavior that is not specified in specifications.

c.) Verify that contract does not violate original intended behavior of specifications.

Here we would look for undefined, unexpected behavior and common security vulnerabilities like:-

=> Re-entrance
=> Overflows
=> Uncheck return values for low-level calls.
=> Denial of service
=> Bad randomness
=> Front running
=> Time manipulation
=> Short address attack
=> Unknown vulnerabilities

In manual review more that one auditor will review the code. The goal is to get to as many skilled eyes on contract code as possible.

Also, Read Our Next Article on QuillAudits.

=> We will apply all security attacks known till date on your contract manually to find security vulnerabilities

=> We will also ensure that your contract has some mechanism to defend against unknown vulnerabilities. Because the state of ethereum is constantly changing and we cannot say which vulnerabilities will arise in the future so we must have a mechanism beforehand.

=> We would ensure that smart contract code must respond to bugs and vulnerabilities well.

=> Manual testing will be done on test nets like rinkeby and ropsten.

=> We would also ensure that there is no unnecessary code in the contract.

=> Best code practices will also be considered in this phase.

Stage 3 – Unit testing

Goal:-Writing and running a comprehensive test suite.

=> In this stage smart contract functions will be unit tested on multiple parameters and under multiple conditions to ensure that all paths of functions are functioning as intended.

=> In this phase intended behavior of smart contract is verified.

=> In this phase, we would also ensure that smart contract functions are not consuming unnecessary gas.

=> Gas limits of functions will be verified in this stage.

Stage 4 – Testing with automated tools

=> Testing with automated tools is important to catch those bugs that humans miss.

Some of the tools we would use are:-
Mythril
Oyente
Manticore
Solgraph
Solidity-coverage

At the end, we would provide you a comprehensive report along with details of audit and steps to cover up with the vulnerabilities if we found any in your contracts.

Launch your blockchain project with Quillhash: https://quillhash.typeform.com/to/KQ5Hhm

Thanks for reading. Also, do check out our earlier blog posts.


At QuillHash, we understand the Potential of Blockchain and have a good team of developers who can develop any blockchain applications like Smart Contracts, dApps,Smart Coins, DeFi, DEX on the any Blockchain Platform like EthereumEOS and Hyperledger.

To be up to date with our work, Join Our Community :-

Telegram | Twitter | Facebook | LinkedIn

345 Views

Related Articles

View All

Trending

⚠️⚠️

In one of the protocol's lending pools, an exploiter escaped with over 44 RBTC by employing a price manipulation method.

#cyberattacks

🧵..
↓↓

We request BSC Validators to get in touch with us within the next few hours so that we can plan a node upgrade.

We'd like to thank the community again for their continuous support.

⚠️⚠️

A spammer has caused havoc for Zcash node operators by filling transaction Blocks with a large number of shielded transaction outputs. Many believe this is a FUD designed to draw attention.

#cyberattacks

🧵🪡..

↓↓

🧵..

[MUST KNOW] Security Tips for Web3—

Don’t ever think it can’t happen to you🚫!

Don’t Rush⚡

In crypto, we all like to move fast, grab the most hyped thing to shell out millions in a minute.

But at the same time, we forget that we are the most vulnerable ones as well.

Hashing Bits | Week - 39 📮

A recap of last week’s Web3 security exploits unwrapped –

‣MEV bot earns $1M to find them all lost to a hack due to the contract vulnerabilities
‣Jason Falovitch, a cryptocurrency entrepreneur, lost six ETH and four NFTs of $150K to a hack.

↓↓

Load More

90 Types of Crypto Worth $160M Stolen 🚨

It was observed from the Omni bridge source code that the logic to verify chainID was present, but the verified chainID used in the contract was pulled from a value stored in the storage named uintStorage.

Become a Quiffiliate!
Join our mission to safeguard web3

Sounds Interesting, Right? All you have to do is:

1

Refer QuillAudits to Web3 projects for audits.

2

Earn rewards as we conclude the audits.

3

Thereby help us Secure web3 ecosystem.

Total Rewards Shared Out: $190K+