ico-arrow-big-left

Smart Contract Hacker Challenge II - PoWH Coin

Key Information

Register
Submit
The challenge is finished.
Show Deadlines

Challenge Overview

Welcome to build a Smart Contract Hacker Challenge

Project Background

The client's intention is to launch a Hacking Contest for smart contract systems, and this will be its second challenge. Participants will learn smart contract security by trying to exploit vulnerabilities that have occured in the past in popular smart contract projects. The challenges will be published as self-contained GitHub projects, that can be easily cloned and installed locally. Within minutes participants will be able to start hacking smart contract systems in a realistic and safe environment.

Be sure to check the previous challenge in the series, and how it was implemented. We want to use the similar setup / structure here, so that the new challenge can be added to the same repository, and handled in the same manner.

Technology Stack

This is a blockchain-related challenge. Relevant technologies are: Ethereum, Solidity, Truffle.

Code Access

Codebase created in the previous challenge is referenced above. Note that you are not supposed to modify in any way the Parity_1_2 challenge, already present in the repo; but you are expected to use its code / setup for reference, to ensure that the newly created challenge can be used in the similar way.

Individual Requirements

Below is the list of what you should do in this challenge. Consider all requirements as major.
  1. Users can start the challenge with ./src/start_level (e.g. https://github.com/thec00n/Smart-Contract-Hacker-Playground/blob/master/Parity_1_2/start_level). Deploy PoWH token contract (https://etherscan.io/address/0xa7ca36f7273d4d38fc2aec5a454c497f86728a7a#code) from ./src/contracts/. Create users that call the function fund() with randomly selected Ether deposits ranging between 1 and 10 ETH. Create as many user transactions necessary to have at least 1000 ETH in the contract. A user only makes one transaction.
     
  2. All dependencies need to be installable with npm install!  You can assume that nodejs 10.x and npm 6.x are installed by the user.
     
  3. Create a src/README.md as part of the repo that explains objective of the hacker challenges. Creative ideas are welcome (e.g. https://github.com/thec00n/Smart-Contract-Hacker-Playground/blob/master/Parity_1_2/README.md)
     
  4. Create solutions/hack.js that exploits the vulnerabilities in the contract and that transfers all of the Ether in the contract to the user. The user’s address is 0xd34435a94f999e0e9fc7c3780a15aa1a815f76e9 (priv: 0x601aaaf5f9ac507ffd34eb3b10bb1bf7b382bf312f460572ba207e4e2b221787) he has 10 ETH starting balance.
     
  5. Users can verify if they have succeeded in getting all the ETH from the contract by running ./src/get_status (e.g. https://github.com/thec00n/Smart-Contract-Hacker-Playground/blob/master/Parity_1_2/get_status). User 0xd34435a94f999e0e9fc7c3780a15aa1a815f76e9 should have more than 1000 ETH balance.

Final Submission Guidelines

Submit Git patch for the repo, a brief demo video. The newly created challenge should be placed into ./PoWH_Coin folder of the repo. The first challenge, already present in the repo (Parity_1_2) should not be altered in any way.

This challenge will be reviewed by the client, using subjective scorecard.

Reliability Rating and Bonus

For challenges that have a reliability bonus, the bonus depends on the reliability rating at the moment of registration for that project. A participant with no previous projects is considered to have no reliability rating, and therefore gets no bonus. Reliability bonus does not apply to Digital Run winnings. Since reliability rating is based on the past 15 projects, it can only have 15 discrete values.
Read more.

ELIGIBLE EVENTS:

2018 Topcoder(R) Open

REVIEW STYLE:

Final Review:

Community Review Board
?

Approval:

User Sign-Off
?

CHALLENGE LINKS:

Review Scorecard

?