In the last tutorial, you learned how to create a bug bounty for a smart contract project on Bug Buster from scratch, but running in development mode locally on your computer. This time you will be able to accomplish the same goal, but in Bug Buster's Testnet environment! What is the difference? You will not need to worry about some steps and following the tutorial now will be much more easier and quicker. Time is money, isn't it? :wink: Requirements In order to follow this tutorial you will need to have the following dependencies installed on your machine: Git Foundry framework

In a previous tutorial you learned how to create a bug bounty for a simple smart contract project on Bug Buster from scratch. For the sake of simplicity, a project with no external dependencies was chosen, but real projects commonly depend on one or more external dependencies. As you may remember, Bug Buster expects bounties to be submitted in a particular format. All the necessary files (such as source code, binaries, etc.) must be bundled as an archive file with tar and compressed with xz. The final product should be a file with the .tar.xz extension. Therefore, you may conclude that for projects with external dependencies you should have only to include the dependencies' source code to the bundle. This logic is right, but there is a limit to the size of bundles that can be sent on-chain, which is around 95KiB, according to tests on Optimism Sepolia and Mainnet. Built-ins: OpenZeppelin In order to avoid bundles from surpassing the size limit, Bug Buster already includes commonly used artifacts in its execution environment. For smart contract projects, Bug Buster provides the OpenZeppelin smart contract library out-of-the-box. The library contains ERC interfaces and implementations, as well as other utility libraries and contracts. In this new tutorial you will learn how to prepare a project that depends on OpenZeppelin to be submitted as a bug bounty on Bug Buster.