Singularity Hubs has 1 public audit report from CertiK; dated 1 Aug 2022; no critical findings reported. It also holds 3 deployed contracts on 1 chain.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
16 findings are still open or acknowledged in the firms’ reports: 5 high, 2 medium, 9 low (9 open, 7 acknowledged).
Centralization Risks in EneToken.sol
Singularity · CertiK · 1 Aug 2022 · Report ↗
Centralization Risks in Pledge.sol
Singularity · CertiK · 1 Aug 2022 · Report ↗
Centralization Risks in SGT.sol
Singularity · CertiK · 1 Aug 2022 · Report ↗
Initial Token Distribution
Singularity · CertiK · 1 Aug 2022 · Report ↗
Initial Token Distribution
Singularity · CertiK · 1 Aug 2022 · Report ↗
No Upper Limit For`_burnRate`
Singularity · CertiK · 1 Aug 2022 · Report ↗
Unused Return Value
Singularity · CertiK · 1 Aug 2022 · Report ↗
`setPlan()` Allows Owner To Change Previous Plans
Singularity · CertiK · 1 Aug 2022 · Report ↗
Comparison to Boolean Constant
Singularity · CertiK · 1 Aug 2022 · Report ↗
Function Should Be Declared `external`
Singularity · CertiK · 1 Aug 2022 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| Singularity | Security firm: CertiK | Date: | Scope: 3 addresses on BNB Chain | None open | Findings: 5 high · 3 medium · 10 low 2 fixed · 7 acknowledged · 9 open | skynet.certik.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 5 | 0 |
| Medium | 0 | 2 | 1 |
| Low | 9 | 0 | 1 |
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.
Open the reportBoolean constants can be used directly and do not need to be compared to true or false.
Open the reportThe functions which are never called internally within the contract should have external visibility for gas optimization.
Open the reportThe 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.
Open the reportThere should always be events emitted in the sensitive functions that are controlled by centralization roles.
Open the reportAddresses should be checked before assignment or external call to make sure they are not zero addresses.
Open the reportThe 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.
Open the reportThe linked functions are equivalent to the compiler-generated getter functions for the respective variables.
Open the reportThe 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.
Open the report| Address | Chain | Source code |
|---|---|---|
| 0x4f4b…36f80x4f4b055f5ed20c5d335a17addeab10f0461036f8 | Chain: BNB Chain | Source code: Verified source |
| 0x7055…60b50x7055caee03ec8c0fc7182cb8f23d97d76b4f60b5 | Chain: BNB Chain | Source code: Verified source |
| 0xc19c…d7510xc19c1bdc6e4f2d3350a63b4846399010a1ded751 | Chain: BNB Chain | Source code: Verified source |
Trustblock holds 1 public audit report for Singularity Hubs, dated 1 Aug 2022. The latest is by CertiK (“Singularity”).
CertiK wrote the report Trustblock holds for Singularity Hubs.
16 findings are still open or acknowledged in the firms’ reports: 5 high, 2 medium, 9 low (9 open, 7 acknowledged). No critical finding is reported. Statuses are the security firms’ own.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="singularity-hubs"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
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