Polbot Info

PolBot token holders will be eligible for 100% profit share from our Trending Services on PolBot. Each Crypto.com, CoinGecko, etc. trending service that is purchased through the PolBot platform will be accumulated and distributed to the $POLBOT holders.

Polbot Logo

TrustNet Score

The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.

79.47
PoorExcellent

Real-Time Threat Detection

Real-time threat detection, powered by Cyvers.io, is currently not activated for this project.

This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks. For more information, click here.

TrustNet DataPulse

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0x700E...2D24
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/07/31
Revision date In progress

Summary and Final Words

No crucial issues found

The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.

Contract owner cannot mint

It is not possible to mint new tokens.

Contract owner cannot blacklist addresses.

It is not possible to lock user funds by blacklisting addresses.

Contract owner cannot set high fees

The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.

Contract cannot be locked

Owner cannot lock any user funds.

Token cannot be burned

There is no burn function within the contract.

Ownership is renounced

Contract cannot be manipulated by owner functions.

Scope of Work

This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.

The auditing process consists of the following systematic steps:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.

A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.

Final Words

The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.


Ownership Privileges
  • The owner can update the router address.
  • The owner can whitelist multiple addresses from fees.
  • The owner can set the marketing wallet address.
  • The owner enable/disable max wallet amount.
  • The owner can set any number to max transaction amount.
  • The owner can set any number to liquidity, marketing fees.
  • The owner can enable/disable swapping.
  • The owner can set the automated market pair address.
  • The owner can blacklist addresses from the transfer of tokens.
  • The ownership is set to this address during the initial deployment (0x5b8a969814aea42cc1fac408e95383eb5c44e059)

Note - The ownership of the token is renounced.This Audit report consists of a security analysis of the Poldot Token smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the Poldot team, other contracts associated with the project were not audited by our team. We recommend investors to do their own research before investing.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 5 findings

Pending

#1 low Issue
Missing Events Arithmetic (events-maths)
SmartTax.sol
L1433-1437
L1439-1441
L1443-1446
L1448-1451
L1453-1455
Description

Emit an event for critical parameter changes.

Pending

#2 low Issue
Missing Zero Address Validation (missing-zero-check)
SmartTax.sol
L1100
L1347
L1403-1404
L1425
Description

Check that the address is not zero.

Pending

#3 low Issue
Floating Pragma solidity version
SmartTax.sol
L3
Description

Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.

Pending

#4 low Issue
Remove Safemath Library
SmartTax.sol
L5-158
Description

compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow, It is recommended to remove the unwanted code in order to avoid high gas fees.

Pending

#5 low Issue
Remove Unused code
SmartTax.sol
L652-721
Description

The contract contains some irrelevant code that will increase the gas fees. Remove unused code so that you can avoid high gas fees.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
SmartTax.sol
L1302
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
SmartTax.sol
L349-351
L357-359
L374-376
L406-414
L419-427
L436-444
L459-474
L488-499
L515-529
L661-663
L665-674
L676-682
L684-686
L1127-1130
L1136-1143
L1396-1406
L1414-1423
L1457-1467
L1484-1486
Description

Use the `external` attribute for functions never called from the contract.

informational Issues | 2 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
SmartTax.sol
L175-178
L593-604
L1075-1081
L1083-1085
L134-136
L150-157
L1223-1226
L1214-1218
L1194-1200
L1182-1189
L1205-1209
L1228-1231
L1239-1243
Description

Remove unused functions.

Pending

#2 informational Issue
Unused state variables (unused-state)
SmartTax.sol
L1177
L1307
Description

Remove unused state variables.