---
# System prepended metadata

title: 'How to deliver a codebase for scoping:'

---

# How to deliver a codebase for scoping:
This is not specific to Consensys Diligence, we believe that many auditing firms will appreciate if you share your auding request in the following way. When following this gide you are likely to have a lower quote in a shorter time period with less back and forth. All of those steps can be done in a markdown file added to a repo. A link to such file is the only thing you will ever need to provide. This information will be sufficient for most auditors.

### 1. Provide the repository link with the code that you want to audit and the commit hash.

We do understand that you might make some changes to the code, that is fine. Just give us the hash that will resemble the final code as much as possible. If your repo is private you can request a GitHub handle from the auditors and provide access to that handle.

### 2. Provide any availiable documentation.
Please share the links to documentation or even better - developer documentation. This will allow to estimate the time it will take to get familiar with the code.

### 3. Provide a short explanation that would have the information outlined bellow.
- Brief one or two sentence explanation of what the protocol is doing. Is it lending market, dex, liquid staking, oracle, ZKP Circuit or somethign else?
- One paragraph about the aspects of the code that you are most concerned about. For example some complex math formulas, or odd upgradeability pattern. 

### 4. Files in scope.
Please be specific. Be as specific as possible. This step can save you weeks of auditing and tens of thousands of dollars. For small protocols you can get away with `contracts/*` but for anything more complex you will most likely end up with a much larger quote that you really need in this case. Identify the key components and related files. 

### 5. Additional Notes.
Any additional information you think is important to share. One example is timelines if they are pressing.

# Example:


## 1Inch Audit Request for Router V5

Code: https://github.com/1inch/limit-order-protocol
Commit: a6f7179f9a0e39617119d3af18778f3bfb7e8897
Request: [LINK TO THE FILE WITH BELLOW CONTENT]

### Documentation:
https://docs.1inch.io/

### About us:
We are a dex aggregator protocol that specializes in finding our users best swapping routes. In this update we are adding functionality for limit orders that we would like to audit.

### Special Concerns:
We are all about optimization. We would like to ensure that some of the operations that we have reimplemented in yul are operating correclty. 

### Files in scope:
- contracts/SomeRouter.sol
- contracts/SomeOrders.sol
- contracts/utils/SomeRouterUtils.sol
- contracts/utils/SomeOrdersUtils.sol
- contracts/math/Rounding.sol

### Any additional notes:
We need to go to production in 3 weeks.
Maths component is not fully ready, but will have only one additional function.