Sales

Miscellaneous

Hi there! Welcome onboard with QuillAudits. We are glad you chose us; let's buckle up and begin.

About us

QuillAudits is a leading web3 cybersecurity firm committed to securing Blockchain projects with our cutting-edge Web3 security solutions.

We provide smart contracts auditing and DApps pen testing services for web3-based, DeFi and NFT-based gaming projects.

SUI Blockchain - Move Smart Contracts

Sui Blockchain is a layer 1 blockchain designed to enable creators and developers to build experiences catering to the next billion users in web3. It is a permissionless, proof-of-stake blockchain with smart contract capabilities. Sui aspires to deliver Ethereum-style capabilities but with better design and tools for scaling. It has been designed to provide instant settlement and high throughput, making it suitable for on-chain use cases like DeFi and GameFi. Sui blockchain uses Move as its native programming language for writing smart contracts.

Why Sui - Move Smart Contracts Need Audits?

<aside> 📌

Security: Smart contract audits help ensure the system's security by identifying and mitigating potential vulnerabilities and risks. In a decentralized system like the Sui blockchain, where there is no central authority to regulate transactions, security is paramount to prevent malicious actors from exploiting loopholes or introducing malicious code.
Accuracy: Smart contract audits ensure that the code executes as intended and achieves its intended results. Accuracy is critical in ensuring the contract operates smoothly and fairly for all parties involved.
Efficiency: Smart contract audits help to optimize the performance of the code, reducing the risk of delays, congestion, or other issues that can negatively impact the system's usability.
Reliability: Smart contract audits increase the reliability of the code by identifying potential points of failure or other issues that can lead to system downtime or other types of disruptions.
Transparency: Smart contract audits increase the system's transparency by providing insights into the inner workings of the contract. This can increase trust and confidence in the system.
Compatibility: Smart contracts may need to interact with other components of the blockchain ecosystem, such as other smart contracts. Auditing the code can ensure that the contract is compatible with these other components and can prevent issues that may arise from incompatibility. </aside>

<aside> 💭 Connecting with you You must have been added to a closed group with the Auditing Team by this time. You would be connected with the Project Manager and the Auditors through this dedicated channel during the process for collaboration and instant resolution. At any point, if you face any query or find a need to discuss anything - we are just a message away!

</aside>

Multi-layer Audit Process

Things We Cover in Move Contract Audit Process but not limited to:

Reentrancy
Integer Overflow/Underflow
Number of Rounding Errors
Denial of Service/Logical Oversights
Time Manipulation
Lack of Input Validation
Interoperability with Other Smart Contracts
Governance and Upgradeability
Gas Limitations
Access Control
Unchecked CALL Return Values
Business Logic Contradiction
Transaction-ordering Dependence
Arbitrary Token Minting
Witness Type
The Flow of Capability

We ensure your smart contract goes through all the stages, from manual code review to automated testing, before generating the Initial Audit Report. Once your team updates the code, we thoroughly scrutinise the smart contract to provide you with the Final Audit Report. Let's dive deep into it and explore more.

image (2).png

Step 1 - Specification Gathering / Prepare For a Security Audit

This is the most crucial stage because the detail is key for a successful smart contract security audit. Here is how you can prepare for it:

Code quality • Remove dead code and comments. • Consistent coding style. • Follow the Move style guide.

Use comments to document complex parts of the code and ensure these are consistent with the code.

Test the code • Make sure the contracts can be compiled and fully tested. • Perform high coverage and high-quality unit tests.

This will maximize focus on the difficult parts of the code. Auditing should not discover that some functions are uncallable or do not do what they are expected to do under entirely straightforward inputs. Optimal auditing should focus on unexpected, corner-case, and possibly adversarial behaviour.

Code freeze • Freeze the code and specify the commit hash. Or, deploy the code on testnet and share the link.

After freezing the code, we will gather the specifications from you to know the intended behaviour of the smart contract through the 'Smart Contract Specification' document.

<aside> 🦋 How can you help? Please ask your developers to fill out the specification doc - It would help us to understand & verify the business logic and facilitate confirming everything thoroughly.

</aside>

Step 2 - Manual Review

Here we would look for undefined, unexpected behaviour and common security vulnerabilities. The goal is to get as many skilled eyes on contract code as possible. Aims of manual review:

Focus on issues regarding security, attacks, mathematical errors, logical issues, etc.
Check the code for any vulnerabilities that can be exploited.
Verify that every detail in the specification is implemented in the smart contract.
Verify that the contract does not have any behaviour that is not stated in the specifications.
Verify that the contract does not violate the intended behaviour of specifications.

Step 3 - Functional Testing

The smart contract will be manually deployed in a sandbox environment like Move testnet/mainnet forks, Move IDE, Move VM etc.
Smart contract functions will be tested on multiple parameters and under multiple conditions to ensure that all paths of functions are operating as intended.
In this phase, the expected behaviour of the 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.

Step 4 - Testing over the Latest Attack Vectors

The team researches newly discovered attacks (like market manipulation, LP pricing, front-running vectors, and more) and tries to replicate them to ensure the project is safe from those attacks.
Move attack vectors:
NFT attack vectors:
DeFi attack vectors:
DAO attack vectors:
Sui attack vectors:
Web2 attack vectors:
If the current implementation is vulnerable to those newly discovered attacks, we recommend the project team switch to a safer implementation.

Step 5 - Testing with Automated Tools

Testing with automated tools is essential to catch those bugs that humans miss. Some of the tools we would use are (based on the requirement/auditor preference, we use specific tools) :

Move Prover
Move IR Visualizer

Step 6 - Initial Audit Report

In the end, we will provide you with a comprehensive report, which we call an Initial Audit Report (IAR):