Singularity

CertiK3 addresses on BNB Chain

CertiK reviewed Singularity Hubs (Singularity) on 1 Aug 2022: 18 findings, 0 critical; 2 marked fixed, 7 acknowledged, 9 open.

No open critical findings
Open the reportOpen Singularity Hubs’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings18

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High050
Medium021
Low901
Low`setPlan()` Allows Owner To Change Previous PlansOpen

Pre-set staking plans are created upon contract deployment. The function `setPlan` allows the contract owner to create new staking plans. \ However, there is no check to ensure previous plans are not overridden, which could disrupt contract functionality.

LowComparison to Boolean ConstantOpen

Boolean constants can be used directly and do not need to be compared to true or false.

LowFunction Should Be Declared `external`Open

The functions which are never called internally within the contract should have external visibility for gas optimization.

LowLack of DocumentationOpen

The contracts `SGT`, `Pledge`, and `EneToken` lack comments explaining the methodology and the reasoning behind the calculation and implementation. Detailed documentation could benefit future code reviewers and improve the project's transparency.

LowMissing Emit EventsOpen

There should always be events emitted in the sensitive functions that are controlled by centralization roles.

LowMissing Zero Address ValidationOpen

Addresses should be checked before assignment or external call to make sure they are not zero addresses.

LowUnclear CodeOpen

The logic behind the `setWithdrawInfo()` function is unclear and seems to be very centralized. It appears that the owner of the `SGT.sol` contract, which is an externally owned account, must use `setWithdrawInfo()` to create `pendingBalances` for every user that wants to interact with the contract. However, users cannot interact with the `SGT.sol` contract directly, and must first choose a staking plan within the `Pledge.sol` contract to receive SGT tokens as a reward. It seems that receiving this reward would not work, since the owner of `SGT.sol` has authority over many of the functions; or receiving the reward would depend on whether the owner has created a `pendingBalances` for a specific address.

LowUser-Defined GettersOpen

The linked functions are equivalent to the compiler-generated getter functions for the respective variables.

LowVariables That Could Be Declared as `immutable`Open

The linked variables assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation but will remain constant throughout the lifetime of a deployed contract. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage.

Contracts in scope3

AddressChainSource code
0x4f4b055f5ed20c5d335a17addeab10f0461036f8Chain: BNB ChainSource code: Verified source
0x7055caee03ec8c0fc7182cb8f23d97d76b4f60b5Chain: BNB ChainSource code: Verified source
0xc19c1bdc6e4f2d3350a63b4846399010a1ded751Chain: BNB ChainSource code: Verified source

Part of Singularity Hubs’s security record

Singularity Hubs
Audits1 audit by 1 firmLast audit Aug 2022, by CertiK.
Critical findingsNo open critical findingsIn 1 report.
Open Singularity Hubs’s security record

Security firm

CertiK

1,045 projects reviewed · 1,376 reports · latest May 2025

See CertiK’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us