We are looking for an experience developer, familiar with EOSIO/Antelope to conductan open-ended CODE REVIEW for the following repo:
We are looking for a code review of these files in the repo:
The focus is centred around if you find anything of concern, whether a logic error, inefficiency, security-related, architecturally, etc,
Anything that departs from best practice.
An important aspect is not to concentrate too much on whether the logic is correct - we are QA-ing the code to ensure that. It's best to concentrate on coding practices generally.
NOTE: This is NOT a full, smart contract audit that goes into deeper details (i.e. fuzzing, overflow, DoS attacks etc.).We are looking for an independent 3rd party to review the code as to our focus illustrated above.
The contract documentation can be found here:
We require some indication of the type of quality we'd like to see and are looking for a small sample review.
Please see the attached points.hpp
Please provide a sample code review—apologies for asking this. We have had very mixed quality when asking for a code review.
Candidates that wish to take this job need to provide a small sample code review of the attached "points.hpp" file to:
1) find 1 issue and identify the location of the issue,
2) provide the severity of the issue, and
3) provide a proposed fix, improvement or best practice for the identified issue
This ONLY needs to be 1 issue in points.hpp for the sample.We don't want to waste anyone's time.
Please provide the sample code review via private message.We will engage with quality candidates that have provided a solid, good sample code review.