Trabajo24 Info
T24 revolutionizes our freelancer escrow payments with blockchain technology. Our platform in Paraguay offers instant payroll payments and streamlined escrow processes through inswitch. Developed by experts, our DeFi automation ensures secure transactions with minimal manual intervention. Partnering withindustry leaders ensures governance, fraud detection, and AML compliance. Join Trabajo24 for secure and efficient freelancer payments.
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 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 can set high fees
Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.
Token transfer can be locked
Owner can lock user funds with owner functions.
Token cannot be burned
There is no burning within the contract without any allowances
Ownership is not renounced
The owner retains significant control, which could potentially be used to modify key contract parameters.
Contract is upgradeable
The contract uses a proxy pattern or similar mechanism, enabling future upgrades. This can introduce risks if the upgrade mechanism is not securely managed.
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
- The owner can update the marketing wallet, development wallet, and sustainability tax to not more than 25%, respectively.
- The owner can set the max transaction amount to any arbitrary value, excluding zero.
- The owner can set the number of blocks for the blacklist.
- The owner can enable trading only once.
- The owner can set the marketing, development wallet, and sustainability wallet addresses.
Note - This Audit report consists of a security analysis of the Trabajo24 token smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited the mentioned contracts for the Trabajo24 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
Findings and Audit result
medium Issues | 3 findings
Pending
#1 medium Issue
The owner can lock transfer
The current setMaxAmount function allows the owner to set an extremely low transaction limit, potentially locking transfers. To prevent this, a minimum threshold should be enforced (e.g., 1000 tokens). This ensures the maxTransactionAmount cannot be set too low, maintaining token usability. The updated function includes a check to prevent values below the threshold, protecting users from accidental or malicious restrictions. Alternatively, a governance mechanism could dynamically adjust this limit for added decentralization. This fix balances security and flexibility, ensuring smooth trading while preventing potential misuse by restricting transfers to an unreasonably small amount.
Resolved
#2 medium Issue
The owner can blacklist wallets.
The blacklistAddress function allows the admin to blacklist specific wallet addresses by setting isBlacklisted[_account] to true. Once blacklisted, these addresses may be restricted from performing certain actions (e.g., transferring tokens), depending on the contract's logic. While this feature can prevent malicious activities or comply with regulations, it introduces centralization risks, as the admin has unilateral control over user access. Additionally, there is no function to unblacklist addresses, which could lead to permanent restrictions. To improve, consider adding an unblacklistAddress function and implementing safeguards (e.g., multi-signature approvals) to ensure fair and transparent governance.
Pending
#3 medium Issue
The owner can set fees more than 25%.
The contract allows the owner to set marketing, development, and sustainability taxes up to 25% each, potentially totaling 75%, making trading impractical. To fix this, modify the setter functions to ensure the combined tax never exceeds 25%. Each function should check that the sum of all taxes stays within this limit before updating values. This prevents excessive taxation while allowing flexibility for adjustments. The fix protects users from extreme fees, ensuring fair transactions while maintaining owner control. Optionally, a configurable max tax could be introduced for further flexibility. This change keeps the token usable and prevents potential abuse.
low Issues | 4 findings
Resolved
#1 low Issue
Floating pragma solidity version
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.
Resolved
#2 low Issue
Missing Visibility
It is recommended to add 'public,' 'private,' or internal visibility during the declaration or initialization of a state variable or a mapping in the contract.
Resolved
#3 low Issue
Missing zero or dead address check.
It is recommended to check that the address can not be set to zero or dead address.
Pending
#4 low Issue
Missing events arithmetic
It is recommended to emit all the critical parameter changes.