yuriy77k

pragma solidity ^0.4.20;


library SafeMath {
  function mul(uint256 a, uint256 b) internal pure returns (uint256) {
    if (a == 0) {
      return 0;
    }
    uint256 c = a * b;
    require(c / a == b);

yuriy77k

BNC token security audit report performed by Callisto Security Audit Department

1. Conclusion:

No critical issue. This contract can be considered safe to be deployed. However, as highlighted users can accidentally send their tokens to 0x0 address.

2. Medium severity issues:

2.1. Token Transfer to Address 0x0

yuriy77k

TokenTrader Smart Contract security audit report performed by Callisto Security Audit Department

Conclusion:

No critical issue, bug fixing is necessary. It is highly recommended to complete a bug bounty before use.

Medium severity issues:

• If attacker creates smart contract with '''owner''' variable equal to real owner address and '''asset''' variable equal to real asset there is a risk of send money to this wrong address.

yuriy77k

Gigzi smart contract security audit conclusion: bug fixing is necessary.

Critical issue:

• Fees Avoidance. User can direct call transferFromAndCall or transferAndCall implemented in OpenZeppelin ERC827Token to transfer token without fee collection and possible manipulation of the reward since it the reward won't be updated.

Medium severity issues:

• FeeableToken contract overload transfer and transferFrom methods, if a user directly call these functions to transfer tokens, it can lead to lost tokens issue.

yuriy77k

ERC20andCrowdsale security audit report performed by Callisto Security Audit Department

Conclusion:

No critical issue, bug fixing is necessary. It is highly recommended to complete a bug bounty before use.

Medium severity issues:

• User can send tokens to Address 0x0 by mistake and lose it.

yuriy77k

pragma solidity ^0.4.16;

/*
 * Abstract Token Smart Contract.  Copyright © 2017 by ABDK Consulting.
 * Author: Mikhail Vladimirov <mikhail.vladimirov@gmail.com>
 */
pragma solidity ^0.4.20;

/*
 * EIP-20 Standard Token Smart Contract Interface.

yuriy77k

Gigzi smart contract improved (ETH) security audit report performed by Callisto Security Audit Department

1. Conclusion:

The contracts reviewed can be considered safe to be deployed. However a lot of optimization has to be done to minimize gas consumption.

2. Low severity issues:

2.1. Reserved Account of Fee Collector Address not updated

yuriy77k

CryptoAds smart contract security audit report performed by Callisto Security Audit Department

Conclusion:

No critical issue, bug fixing is necessary. It is highly recommended to complete a bug bounty before use.

Medium severity issues:

1. Zero address owner.

yuriy77k

pragma solidity ^0.4.8;

/**
 * Math operations with safety checks
 */
contract SafeMath {
  function safeMul(uint256 a, uint256 b) internal returns (uint256) {
    uint256 c = a * b;
    assert(a == 0 || c / a == b);
    return c;

yuriy77k

P3C Smart Contract security audit report performed by Callisto Security Audit Department

1. Conclusion:

The audit, conducted on P3C contract, concluded that the contract is safe to be used. Graphical analysis and the definition domains of the functions used for conversion (tokens to ether and ether to tokens) showed positive results. However, for better analysis the contract developers should provide the community with a white paper describing every aspect of the contract especial the conversion algorithms.

2. Low severity issues:

2.1. Known Issue of ERC20 Standard