Syndicatus Token Info

In an era where digital innovation is not just an advantage but a necessity, the Syndicatus Ecosystem emerges as a pioneering force, redefining the intersection of blockchain technology, decentralized finance (De-Fi), and community empowerment. Built on the robust Syndicatus Chain, utilizing Hyperledger Fabric for unparalleled security and scalability, the ecosystem is designed to cater to a global community of digital nomads, entrepreneurs, and tech enthusiasts seeking a more equitable and efficient digital economy.

Syndicatus Token Logo

Team and KYC Verification

The KYC verification for this project is currently in progress.

The team has submitted their information and verification is pending.

KYC Badge

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.

56.26
Poor Excellent

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

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xF370...ab36
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/05/27
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 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.

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 tax helper wallet can buy back the burn tokens to the owner's wallet.

Note - This Audit report consists of a security analysis of the Sydicatus 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 Sydicatus Token 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

/

Findings and Audit result

low Issues | 3 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
TaxToken.sol
L3998
L4048
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Zero Address Validation (missing-zero-check)
TaxToken.sol
L3729
L3727
L4339
L4455
Description

Check that the address is not zero.

Pending

#3 low Issue
Dangerous usage of `tx.origin` (tx-origin)
TaxToken.sol
L2244-2280
Description

Do not use `tx.origin` for authorization.

optimization Issues | 2 findings

Pending

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

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

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
TaxToken.sol
L269-272
L313-315
L317-319
L455-471
L627-629
L631-634
L636-638
L640-643
L645-647
L649-652
L654-656
L658-661
L663-665
L667-670
L672-674
L676-679
L681-683
L685-688
L886-889
L891-895
L897-900
L902-906
L908-923
L927-931
L933-937
L939-949
L951-953
L955-959
L961-975
L979-983
L985-989
L991-1001
L1003-1005
L1007-1012
L1014-1018
L1020-1028
L1482-1581
L1612-1638
L1695-1697
L1699-1701
L1772-1775
L1777-1780
L1805-1810
L1812-1817
L1819-1825
L1827-1830
L1832-1845
L1847-1849
L1851-1864
L1866-1879
L1881-1886
L1888-1914
L1916-1942
L1944-1949
L1951-1954
L1956-1959
L1961-1964
L1966-1975
L2148-2237
L2288-2298
L2300-2309
L2423-2427
L2485-2488
L2490-2493
L2807-2809
L2815-2817
L2832-2834
L2839-2841
L2846-2848
L2858-2861
L2866-2868
L2877-2880
L2895-2903
L2917-2920
L2936-2942
L3549-3556
L3558-3567
L3569-3573
L3575-3577
L3579-3581
L3586-3591
L3655-3657
L3659-3663
L3665-3667
L3669-3673
L3675-3677
L3679-3683
L3755-3757
L3761-3766
L3803-3805
L3807-3809
L3811-3813
L3815-3817
L3819-3821
L3823-3825
L3827-3829
L3831-3833
L3835-3837
L3839-3841
L3843-3845
L3847-3849
L3851-3853
L3855-3857
L3859-3861
L3863-3865
L3867-3869
L3871-3873
L3875-3877
L3879-3881
L3883-3885
L3887-3889
L3891-3893
L3895-3897
L3899-3901
L3903-3905
L3907-3909
L3911-3913
L3915-3917
L3919-3921
L3923-3925
L3927-3929
L3931-3933
L3935-3937
L3998-4000
L4002-4005
L4030-4036
L4038-4046
L4093-4095
L4119-4126
L4193-4201
L4381-4384
L4386-4388
L4494-4497
L4499-4501
Description

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

informational Issues | 2 findings

Pending

#1 informational Issue
Costly operations in a loop (costly-loop)
TaxToken.sol
L529-559
L529-559
Description

Use a local variable to hold the loop computation result.

Pending

#2 informational Issue
Functions that are not used (dead-code)
TaxToken.sol
L207-210
L3002-3013
L2981-2989
L3289-3291
L3305-3307
L3444-3446
L3343-3345
L3482-3484
L3322-3324
L3461-3463
L3329-3331
L3468-3470
L3315-3317
L3454-3456
L3421-3430
L3355-3357
L3494-3503
L2095-2105
L3127-3130
L3139-3142
Description

Remove unused functions.