Juris Protocol Info
While $LUNC has built a strong community and shows impressive liquidity, it faces a significant challenge: the lack of founders and practical uses. This gap has limited the ecosystem's ability to fully leverage its blockchain technology. Juris Protocol is stepping in to fill this void by bringing in visionary ideas and creating valuable applications. Our goal is to revitalize the $LUNC ecosystem by promoting the use of $USTC and IBC-enabled stablecoins through innovative Layer 2 solutions on the Terra Classic network.
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.
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.
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.
Security Assessments
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 can mint
It is 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 without any allowances.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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
Note - This Audit report consists of a security analysis of the Juris Protocol 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 Juris Protocol team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
low Issues | 1 findings
Pending
#1 low Issue
Missing zero amount check.
Missing zero amount check in execute_transfer/execute_send function. It is recommended to add a zero amount validation check in execute_transfer/execute_send function. If the amount is 0, it should revert.
informational Issues | 4 findings
Pending
#1 informational Issue
Missing validation check.
Missing validation check for the recipient address is not a whale after minting tokens in execute_mint function. It is recommended to add a validation check for the whale account after minting tokens on the recipient address.
Pending
#2 informational Issue
Missing validation check.
Missing validation check of max_tax for setting new tax map info in execute_set_tax_map function . It is recommended to add a validation check of max tax amount for setting tax info for transfers in execute_set_tax_map function.
Pending
#3 informational Issue
Missing validation check.
Missing validation check of max_tax for setting new tax map info in migrate function. It is recommended to add a validation check of max tax amount for setting tax info for transfers in migrate function.
Pending
#4 informational Issue
Skip updating balance for tax
Skip updating balance for tax if the recipient address is the proceeds wallet or tax is zero. Updating contract tax balance in case of zero tax if the recipient address is proceeds wallet can be avoided.