bsc-rex.io audit reports

BNB Chainbsc-rex.io

bsc-rex.io has 1 public audit report from CertiK; dated 20 Sep 2022; no critical findings reported.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm10

Statuses are the security firms’ own

10 findings are still open or acknowledged in the firms’ reports: 5 high, 5 low (5 open, 5 acknowledged).

High
5
Low
5
  • High Open

    Centralization Risk in REX_AIRDROP.sol

    REX. · CertiK · 20 Sep 2022 · Report ↗

  • High Open

    Centralization Risk in REX_DEX.sol

    REX. · CertiK · 20 Sep 2022 · Report ↗

  • High Open

    Centralization Risk in REX_RDA.sol

    REX. · CertiK · 20 Sep 2022 · Report ↗

  • High Open

    Centralization Risk in REX_REX.sol

    REX. · CertiK · 20 Sep 2022 · Report ↗

  • High Open

    Centralization Risk in REX_TREX.sol

    REX. · CertiK · 20 Sep 2022 · Report ↗

  • Low Acknowledged

    Hardcode Address

    REX. · CertiK · 20 Sep 2022 · Report ↗

  • Low Acknowledged

    Missing Emit Events

    REX. · CertiK · 20 Sep 2022 · Report ↗

  • Low Acknowledged

    Missing Error Messages

    REX. · CertiK · 20 Sep 2022 · Report ↗

  • Low Acknowledged

    Third Party Dependencies

    REX. · CertiK · 20 Sep 2022 · Report ↗

  • Low Acknowledged

    Weak PRNG

    REX. · CertiK · 20 Sep 2022 · Report ↗

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
REX.Security firm: CertiKDate: Scope: Files listedNone openFindings: 5 high · 2 medium · 19 low
16 fixed · 5 acknowledged · 5 open
skynet.certik.com ↗

Findings26

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

SeverityOpenAcknowledgedFixed
Critical000
High500
Medium002
Low0514
HighCentralization Risk in REX_AIRDROP.solREX. · CertiK · 20 Sep 2022Open

The `TOKEN_DEFINER` of the contract `RexAirdrop` has the responsibility to notify users about the following capabilities: - provides the address of `REX_CONTRACT` through `initRexContract()` - sets the claimable amounts per address through `initClaimables()` - revokes access through `revokeAccess()` Any compromise to the privileged account which has access to `TOKEN_DEFINER` may allow the hacker to provide the address of `REX_CONTRACT`. and set the claimable amounts.

Open the report
HighCentralization Risk in REX_DEX.solREX. · CertiK · 20 Sep 2022Open

The `TOKEN_DEFINER` of the contract `RexDEX` has the responsibility to notify users about the following capabilities: - provides the address of `REX_CONTRACT` through `initRexContract()` - revokes access through `revokeAccess()` Any compromise to the privileged account which has access to `TOKEN_DEFINER` may allow the hacker to provide the address of `REX_CONTRACT`. The `REX_CONTRACT` of the contract `RexDEX` has the responsibility to notify users about the following capabilities: - offers a stake through `listStake()`

Open the report
HighCentralization Risk in REX_RDA.solREX. · CertiK · 20 Sep 2022Open

The `TOKEN_DEFINER` of the contract `RexDailyAuction` has the responsibility to notify users about the following capabilities: - sets the address of `REX_CONTRACT`, `TREX_TOKEN`, `LP_TOKEN` and `UNISWAP_PAIR` through `initRexContract()` - revokes access through `revokeAccess()` Any compromise to the privileged account which has access to `TOKEN_DEFINER` may allow the hacker to provide the address of `REX_CONTRACT`, `TREX_TOKEN`, `LP_TOKEN`, and `UNISWAP_PAIR`. The `GAS_REFUNDER` of the contract `RexDailyAuction` has the responsibility to notify users about the following capabilities: - withdraw any tokens from the contract after the contract has ended through `withdrawTokensAfterContractEnd()` Any compromise to the privileged account which has access to `GAS_REFUNDER` may allow the hacker to withdraw any tokens from the contract after the contract has ended.

Open the report
HighCentralization Risk in REX_REX.solREX. · CertiK · 20 Sep 2022Open

The `TOKEN_DEFINER` of the contract `RexToken` has the responsibility to notify users about the following capabilities: - sets the address of `AIRDROP_CONTRACT`, `RDA_CONTRACT`, `DEX_CONTRACT`, `TREX_TOKEN` and `UNISWAP_PAIR` through `initRexContract()` - revokes access through `revokeAccess()` Any compromise to the privileged account which has access to `TOKEN_DEFINER` may allow the hacker to provide the address of `AIRDROP_CONTRACT`, `RDA_CONTRACT`, `DEX_CONTRACT`, `TREX_TOKEN`, and `UNISWAP_PAIR`. The role of `AIRDROP_CONTRACT` and `RDA_CONTRACT` of the contract `RexToken` has the responsibility to notify users about the following capabilities: - mints tokens to any address through `mintSupply()` - create a stake through `createStake()` The role of `DEX_CONTRACT` of the contract `RexToken` has the responsibility to notify users about the following capabilities: - restore a stake through `restoreStake()` - create a stake through `createBoughtStake()`

Open the report
HighCentralization Risk in REX_TREX.solREX. · CertiK · 20 Sep 2022Open

The `owner()` of the contract `TREX` has the responsibility to notify users about the following capabilities: - renounces ownership of the contract through `renounceOwnership()` - transfers ownership of the contract to a new account through `transferOwnership()` - creates `amount` tokens and assigns them to `msg.sender` and increases the total supply through `mint()` - saves the airdrop amounts after deployment through `initClaimables()` Any compromise to the privileged account which has access to `owner()` may allow the hacker to create tokens and save the airdrop amounts after deployment.

Open the report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

The repositories and files the reports name

bsc-rex.io: questions

Is bsc-rex.io audited?

Trustblock holds 1 public audit report for bsc-rex.io, dated 20 Sep 2022. The latest is by CertiK (“REX.”).

Who audited bsc-rex.io?

CertiK wrote the report Trustblock holds for bsc-rex.io.

Are there open findings in bsc-rex.io’s audits?

10 findings are still open or acknowledged in the firms’ reports: 5 high, 5 low (5 open, 5 acknowledged). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

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.

Content

Facts

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.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="bsc-rexio"
></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