Pawtocol is a global online community of pet lovers who aim to disrupt the pet industry by leveraging blockchain technology to monetize data about their pets, improve owners’ purchasing experience, and help veterinarians to deliver better care.
Pawtocol is the world’s most advanced online pet community, combining blockchain, AI and IoT technologies to improve the lives of the world’s 400+ million pets. This user-friendly, multi-functional platform will seamlessly integrate into the average pet parent’s daily life, uniquely positioning it to take over this fast-growing, $150B+ industry.
Pawtocol’s blockchain technology provides its users cutting-edge privacy and security features, including complete control of their data and the ability to get paid for securely selling it to data buyers. With the help of AI, the platform will offer pet parent’s helpful, personalized guidance with everything from buying treats to providing healthcare. The company’s integrated, NFC-enabled dog tag makes interacting with the platform simple and intuitive, because Pawtocol is for all the world’s pets.
One of the most unique innovations of the Pawtocol platform is the Data Marketplace, a first of its kind, peer-to-peer exchange for users to safely sell their de-identified data directly to companies and groups that want to buy it. For users, this means getting paid when someone wants to use their data. For buyers, it means richer datasets, with cheaper price tags.
The Pawtocol Data Marketplace represents a revolution in how data flows around the pet industry. But, it also represents another first: a sustainable technology company that more fairly pays for the digital resources it consumes. All of this means that when Pawtocol grows, everyone will benefit.
Unable to find manual contract audit (e.g. Certik, PeckShield, Solidity...)
ERC20Detailed.constructor(string,string,uint8).name (#127) shadows:
- ERC20Detailed.name() (#136-138) (function)
ERC20Detailed.constructor(string,string,uint8).symbol (#127) shadows:
- ERC20Detailed.symbol() (#144-146) (function)
ERC20Detailed.constructor(string,string,uint8).decimals (#127) shadows:
- ERC20Detailed.decimals() (#160-162) (function)
Rename the local variables that shadow another component.
Additional information: link
Context._msgData() (#103-106) is never used and should be removed
SafeMath.div(uint256,uint256) (#269-271) is never used and should be removed
SafeMath.div(uint256,uint256,string) (#286-293) is never used and should be removed
SafeMath.mod(uint256,uint256) (#306-308) is never used and should be removed
SafeMath.mod(uint256,uint256,string) (#323-326) is never used and should be removed
SafeMath.mul(uint256,uint256) (#244-256) is never used and should be removed
Remove unused functions.
Additional information: link
Pragma version0.5.11 (#5) allows old versions
solc-0.5.11 is not recommended for deployment
Deploy with any of the following Solidity versions: 0.5.16 - 0.5.17, 0.6.11 - 0.6.12, 0.7.5 - 0.7.6 Use a simple pragma version that allows any of these versions. Consider using the latest version of Solidity for testing.
Additional information: link
Redundant expression "this (#104)" inContext (#93-107)
Remove redundant statements if they congest code but offer no value.
Additional information: link
BUPIToken.slitherConstructorConstantVariables() (#580-592) uses literals with too many digits:
- _INITIAL_SUPPLY = 1000000000000000000000000000 (#582)
Use: Ether suffix, Time suffix, or The scientific notation
Additional information: link
name() should be declared external:
- ERC20Detailed.name() (#136-138)
symbol() should be declared external:
- ERC20Detailed.symbol() (#144-146)
decimals() should be declared external:
- ERC20Detailed.decimals() (#160-162)
totalSupply() should be declared external:
- ERC20.totalSupply() (#366-368)
balanceOf(address) should be declared external:
- ERC20.balanceOf(address) (#373-375)
transfer(address,uint256) should be declared external:
- ERC20.transfer(address,uint256) (#385-388)
allowance(address,address) should be declared external:
- ERC20.allowance(address,address) (#393-395)
approve(address,uint256) should be declared external:
- ERC20.approve(address,uint256) (#404-407)
transferFrom(address,address,uint256) should be declared external:
- ERC20.transferFrom(address,address,uint256) (#421-425)
increaseAllowance(address,uint256) should be declared external:
- ERC20.increaseAllowance(address,uint256) (#439-442)
decreaseAllowance(address,uint256) should be declared external:
- ERC20.decreaseAllowance(address,uint256) (#458-461)
burn(uint256) should be declared external:
- ERC20Burnable.burn(uint256) (#567-569)
burnFrom(address,uint256) should be declared external:
- ERC20Burnable.burnFrom(address,uint256) (#574-576)
Use the external attribute for functions never called from the contract.
Additional information: link
BscScan page for the token does not contain additional info: website, socials, description, etc.
Additional information: link
Unable to find token contract audit
Unable to verify token contract address on the website
Unable to find audit link on the website
Unable to find whitepaper link on the website
Unable to find token on CoinHunt
Additional information: link
Young tokens have high risks of scam / price dump / death
Young tokens have high risks of price dump / death
Telegram account has relatively few subscribers
Unable to find Youtube account
Unable to find Discord account