The so called
poc-framework is a tool we developed to help us quickly testing bugs in smart-contracts.
Especially for more complicated bugs, it is often easier to verify an idea practically rather than statically by just reading code.
This is usually a multistep process. First, you obviously do not want to test on the live Solana chain. That means you have to replicate the setup locally somehow. If you have ever tried to write integration tests for smart contracts before, you know that it is a bit tedious to get the correct setup.
Normally, smart contracts work the following way: you have a Rust cli or some web3js that generates instructions and sends them via RPC to a validator. On the validator, the contract is already initialized, and your instructions can be executed by the network, returning you the result.
For testing, it is often times not necessary to have a full network. Just the solana smart contract runtime is enough to see most behaviour.
This is where the
poc-framework comes in. It is a collection of helper methods to interact with the core solana code in a way that is similar to what would happen when a contract is used on the normal network.
An exploit utilizing the framework consists of three parts: setup code (marked with the comment: "SETUP CODE BELOW"), the actual exploit (the
fn hack() function you will write) and a check if the exploit succeeded (the
fn verify() function). We have already provided the first and the last one in the poc files for you, just the exploit is missing.
To see how the Framework can help you, its best to check out the functions provided by the
Environment: poc_framework::Environment docs.
The hacker is given 1 sol for paying fees on transactions. The goal is to give the hacker more money than they started with. It is not necessarily possible to steal all the money.
verify function will check this for you automatically, so you will know when you have succeeded.