Jordan Peterson INU Info

www.jordanpetersoninu.com

In a world with rampant censorship and increased ideological polarity, we need the ability to have open debates on contentious and salient issues. Jordan Peterson Inu is a meme coin based on the most viral intellectual of all time, who himself has been the subject of many memes.

Jordan Peterson INU Logo

Team and KYC Verification

The team has securely submitted their personal information to SolidProof.io for verification.

In the event of any fraudulent activities, this information will be promptly reported to the relevant authorities to ensure accountability and compliance.

Show KYC Certificate

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.

On-Chain Insights

Smart Contract Audit

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xd041...a554
Network Ethereum - Mainnet
License N/A
Compiler N/A N/A
Type N/A
Language Solidity
Onboard date 2022/12/09
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 can be burned

There is a function to burn tokens in the contract.

Ownership is not renounced

Contract can be manipulated by owner functions.

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:
  • Enable trading but cannot disable it
  • Remove limits but cannot add them later.
  • Disable Transfer delay only once
  • Update tokens swap at amount, max txn amount, max wallet amount within limitations
  • Include/Exclude accounts from fees and max transaction
  • Enable/Disable swap.
  • Set AMM Pair, Marketing wallet, dev wallet
  • Set auto LP burn setting within limitation but the owner can manually burn LP tokens with a few restrictions

Scope of Work

Files and details

This audit covered the following files listed below with a SHA-1 Hash. The Team mentioned above provided us with the files that need to be evaluated.

The auditing process follows a routine series of steps:
  1. Review the specifications, sources, and instructions provided to SolidProof to ensure we understand the smart contract's size, scope, and functionality.
  2. Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
  3. Specification comparison checks whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
  4. Test coverage analysis determines whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
  5. Symbolic execution is analyzing a program to determine what inputs cause each part of a program to execute.
  6. Based on the established industry and academic practices, recommendations, and research, best practices review smart contracts to improve efficiency, effectiveness, clarity, maintainability, security, and control.
  7. Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.

A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.

Findings and Audit result

low Issues | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
JordanPetersonInu.sol
L1156
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
JordanPetersonInu.sol
L1213-1228
L1230-1236
L1238-1244
L1258-1268
L1270-1280
L1551-1567
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
JordanPetersonInu.sol
L1305
L1313
Description

Check that the address is not zero.

Pending

#4 low Issue
Contract doesn't import npm packages from source (like OpenZeppelin etc.)
JordanPetersonInu.sol
-
Description

We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities

informational Issues | 1 findings

Pending

#1 informational Issue
Unused return values (unused-return)
JordanPetersonInu.sol
L1482-1495
Description

Ensure that all the return values of the function calls are used.