Twittelonboss has 2 public audit reports from Cyberscope and SolidProof; the latest is Cyberscope, 27 Apr 2022; no critical findings reported. It also holds 2 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
20 findings are still open or acknowledged in the firms’ reports: 20 low (all open).
CO - Code Optimization
Twittelon BOSS · Cyberscope · 27 Apr 2022 · Report ↗
L01 - Public Function could be Declared External
Twittelon BOSS · Cyberscope · 27 Apr 2022 · Report ↗
L02 - State Variables could be Declared Constant
Twittelon BOSS · Cyberscope · 27 Apr 2022 · Report ↗
L04 - Conformance to Solidity Naming Conventions
Twittelon BOSS · Cyberscope · 27 Apr 2022 · Report ↗
L05 - Unused State Variable
Twittelon BOSS · Cyberscope · 27 Apr 2022 · Report ↗
L07 - Missing Events Arithmetic
Twittelon BOSS · Cyberscope · 27 Apr 2022 · Report ↗
L09 - Dead Code Elimination
Twittelon BOSS · Cyberscope · 27 Apr 2022 · Report ↗
L13 - Divide before Multiply Operation
Twittelon BOSS · Cyberscope · 27 Apr 2022 · Report ↗
MAL - Misused Algorithmic Logic
Twittelon BOSS · Cyberscope · 27 Apr 2022 · Report ↗
OCTD - Owner Contract Tokens Drain
Twittelon BOSS · Cyberscope · 27 Apr 2022 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| Twittelon BOSS | Security firm: Cyberscope | Date: | Scope: 1 address on BNB Chain | None open | Findings: 11 low 11 open | IPFS ↗ |
| Twittelonboss | Security firm: SolidProof | Date: | Scope: 1 address on BNB Chain | None open | Findings: 9 low 9 open | IPFS ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 20 | 0 | 0 |
The report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportNo description was provided.
Open the reportNo description was provided.
Open the reportNo description was provided.
Open the reportNo description was provided.
Open the reportNo description was provided.
Open the reportNo description was provided.
Open the reportNo description was provided.
Open the reportNo description was provided.
Open the reportNo description was provided.
Open the report| Address | Chain | Source code |
|---|---|---|
| 0xf9b0…7f150xf9b0fa7feee99a9c154fbd58a289011320da7f15 | Chain: BNB Chain | Source code: Verified source |
| 0xcce9…0d700xcce97687c8666bbf3900c1626145f5be31db0d70 | Chain: BNB Chain | Source code: Verified source |
Trustblock holds 2 public audit reports for Twittelonboss, dated 25 Apr 2022 to 27 Apr 2022. The latest is by Cyberscope (“Twittelon BOSS”).
2 security firms wrote the reports Trustblock holds for Twittelonboss: Cyberscope and SolidProof.
20 findings are still open or acknowledged in the firms’ reports: 20 low (all open). 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="twittelonboss"></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