Smart contract audit for Paygine project

Smart contract audit for Paygine project.

Project’s web-site: https://paygine.com

Code repository: https://github.com/bobomurod/paygine

The version of the contracts for which the audit was conducted: https://github.com/bobomurod/paygine/tree/1d6597b74c18ecf14587209615ee5cc73f2c0d03

Classification of identified problems

CRITICAL – the possibility of theft of the ETH/tokens or their blocking without the possibility of restoring access or other loss of ether / tokens due to any party, for example, dividends.
SERIOUS – the possibility of violations of the contract, in which to restore its correct operation, it is necessary to modify the state of the contract manually or completely replace it.
WARNINGS – the possibility of violation of the planned logic of the contract or the possibility of organizing a DoS attack on the contract.
NOTES – all other remarks.

Methodology of audit
The contract code is manually scanned for known vulnerabilities, logic errors, WhitePaper compliance. If necessary, unit tests are written for questionable moments.

Identified problems

[CRITICAL]
– None.

[SERIOUS]
– None.

[WARNINGS]
– None.

[NOTES]

https://github.com/bobomurod/paygine/blob/1d6597b74c18ecf14587209615ee5cc73f2c0d03/contracts/PGC_token.sol#L186
Tokens can only be burned to the nearest integer.