Avium Origins audit reports

Avium Origins has 1 public audit report from CertiK; dated 24 Jan 2023; 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 firm15

Statuses are the security firms’ own

15 findings are still open or acknowledged in the firms’ reports: 1 high, 14 low (all open).

High
1
Low
14
  • High Open

    Centralization Risks in Origins

    Avium 1 - audit addendum · CertiK · 24 Jan 2023 · Report ↗

  • Low Open

    Declaration Naming Convention

    Avium 1 - audit addendum · CertiK · 24 Jan 2023 · Report ↗

  • Low Open

    External Call Inside Loop

    Avium 1 - audit addendum · CertiK · 24 Jan 2023 · Report ↗

  • Low Open

    Missing Emit Events

    Avium 1 - audit addendum · CertiK · 24 Jan 2023 · Report ↗

  • Low Open

    Missing Zero Address Validation

    Avium 1 - audit addendum · CertiK · 24 Jan 2023 · Report ↗

  • Low Open

    Redundant Code Components

    Avium 1 - audit addendum · CertiK · 24 Jan 2023 · Report ↗

  • Low Open

    Shadowing Local Variable

    Avium 1 - audit addendum · CertiK · 24 Jan 2023 · Report ↗

  • Low Open

    Uninitialized Local Variable

    Avium 1 - audit addendum · CertiK · 24 Jan 2023 · Report ↗

  • Low Open

    Unlocked Compiler Version

    Avium 1 - audit addendum · CertiK · 24 Jan 2023 · Report ↗

  • Low Open

    Unsafe Integer Cast

    Avium 1 - audit addendum · CertiK · 24 Jan 2023 · Report ↗

All 15 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Avium 1 - audit addendumSecurity firm: CertiKDate: Scope: Files listedNone openFindings: 1 high · 14 low
15 open
skynet.certik.com ↗

Findings15

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

SeverityOpenAcknowledgedFixed
Critical000
High100
Medium000
Low1400
HighCentralization Risks in OriginsAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

In the contract `Origins` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and change different contract parameters, pause/unpause the contract and even withdraw all funds from it. ![](https://accelerator-tasks-prod.acc.corp.certik.com/ff1e95858ff24e01badef4949886e98f/diagrams/centralization_Origins-Origins-_owner.svg)

Open the report
LowDeclaration Naming ConventionAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

One declaration does not conform to the [Solidity style guide](https://solidity.readthedocs.io/en/v0.7.3/style-guide.html#naming-conventions) with regards to its naming convention. Particularly: - `camelCase`: Should be applied to function names, argument names, local and state variable names, modifiers - `UPPER_CASE`: Should be applied to `constant` variables - `CapWords`: Should be applied to contract names, struct names, event names and enums ```solidity=56 bytes32 private DOMAIN_SEPARATOR; ``` - Variable `DOMAIN_SEPARATOR` is not in `camelCase`.

Open the report
LowExternal Call Inside LoopAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

External calls are made inside a *for* loop. This might lead to a denial-of-service attack. If any of the calls fail, it will cause the entire loop to revert. ```solidity=21 erc721Contract.transferFrom(msg.sender, to[i], tokenIds[i][j]); ```

Open the report
LowMissing Emit EventsAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

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

Open the report
LowMissing Zero Address ValidationAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

Addresses should be checked before assignment or external call to make sure they are not zero addresses. ```solidity=74 signer = signer_; ``` - `signer_` is not zero-checked before being used. --- ```solidity=247 to.transfer(address(this).balance); ``` - `to` is not zero-checked before being used.

Open the report
LowRedundant Code ComponentsAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

The linked statements do not affect the functionality of the codebase and appear to be either leftovers from test code or older functionality.

Open the report
LowShadowing Local VariableAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

A local variable is shadowing another component defined elsewhere. ```solidity=68 address owner, ``` - Local variable `owner` in `Origins.constructor` shadows the function `owner` in `Ownable`.

Open the report
LowUninitialized Local VariableAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

```solidity=18 for (uint256 i; i < length; ) { ``` - Local variable `i` is never initialized. --- ```solidity=20 for (uint256 j; j < tokenLength; ) { ``` - Local variable `j` is never initialized. --- ```solidity=38 for (uint256 i; i < length; ) { ``` - Local variable `i` is never initialized.

Open the report
LowUnlocked Compiler VersionAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

The contracts cited have an unlocked compiler version. An unlocked compiler version in the source code of the contract permits the user to compile it at or above a particular version. This, in turn, leads to differences in the generated bytecode between compilations due to differing compiler version numbers. This can lead to ambiguity when debugging, as compiler specific bugs may occur in the codebase that would be hard to identify over a span of multiple compiler versions rather than a specific one.

Open the report
LowUnsafe Integer CastAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

```solidity=75 ogwlPrices[0] = uint128(prices_[0]); ``` - The type conversion `uint128(prices_[0])` from larger type uint256 to smaller type uint128 may truncate data. --- ```solidity=76 ogwlPrices[1] = uint128(prices_[1]); ``` - The type conversion `uint128(prices_[1])` from larger type uint256 to smaller type uint128 may truncate data. --- ```solidity=188 _setAux(msg.sender, uint64(aux + (1 << bitPos))); ``` - The type conversion `uint64(aux + (1 << bitPos))` from larger type uint256 to smaller type uint64 may truncate data.

Open the report
Show 5 more
LowUnused Custom ErrorAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

`MintNotStarted` is declared but never used: ```solidity=33 error MintNotStarted(); ```

Open the report
LowUnused EventAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

`PriceChanged` is declared in `Origins` but never emitted: ```solidity=97 event PriceChanged(uint256 mintState, uint256 price); ```

Open the report
LowUnused State VariableAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

One state variables are never used in the codebase. Variable `PUBLIC_PRICE` in `Origins` is never used in `Origins`. ```solidity=44 uint256 private constant PUBLIC_PRICE = 2; ```

Open the report
LowUsage of `transfer` for sending EtherAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

It is not recommended to use Solidity's `transfer()` and `send()` functions for transferring Ether, since some contracts may not be able to receive the funds. Those functions forward only a fixed amount of gas (2300 specifically) and the receiving contracts may run out of gas before finishing the transfer. Also, EVM instructions' gas costs may increase in the future. Thus, some contracts that can receive now may stop working in the future due to the gas limitation. ```solidity=247 to.transfer(address(this).balance); ``` - `Origins.withdraw()` uses `transfer()`.

Open the report
LowUsage of Magic NumbersAvium 1 - audit addendum · CertiK · 24 Jan 2023Open

Different magic numbers are used as-is in code.

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

Avium Origins: questions

Is Avium Origins audited?

Trustblock holds 1 public audit report for Avium Origins, dated 24 Jan 2023. The latest is by CertiK (“Avium 1 - audit addendum”).

Who audited Avium Origins?

CertiK wrote the report Trustblock holds for Avium Origins.

Are there open findings in Avium Origins’s audits?

15 findings are still open or acknowledged in the firms’ reports: 1 high, 14 low (all open). 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="avium-origins"
></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