vlayer audit reports

Ethereumvlayer.xyz

vlayer has 1 public audit report from Veridise; dated 12 May 2025; 3 critical findings, all marked fixed by the firms.

Critical findings
No open critical findings
In that report, 3 critical findings were reported. Each is marked fixed by the firm that reported it. See the findings
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 firm5

Statuses are the security firms’ own

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

Low
5
  • Low Open

    Primary redaction characters may exist in values

    vlayer · Veridise · 12 May 2025 · Report ↗

  • Low Open

    REVM block number not set for ForgeBlock

    vlayer · Veridise · 12 May 2025 · Report ↗

  • Low Open

    Sequencer output silently overwritten

    vlayer · Veridise · 12 May 2025 · Report ↗

  • Low Open

    Two step ownership is preferred

    vlayer · Veridise · 12 May 2025 · Report ↗

  • Low Acknowledged

    Lack of SpecID may cause confusion to users

    vlayer · Veridise · 12 May 2025 · Report ↗

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
vlayerSecurity firm: VeridiseDate: Scope: Not recorded; see the report3 critical findings, fixedFindings: 3 critical · 6 high · 6 medium · 8 low
18 fixed · 1 acknowledged · 4 open
veridise.com ↗

Findings30

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

SeverityOpenAcknowledgedFixed
Critical003
High006
Medium006
Low413
LowPrimary redaction characters may exist in valuesvlayer · Veridise · 12 May 2025Open

The report gives no description here.

Open the report
LowREVM block number not set for ForgeBlockvlayer · Veridise · 12 May 2025Open

The report gives no description here.

Open the report
LowSequencer output silently overwrittenvlayer · Veridise · 12 May 2025Open

The report gives no description here.

Open the report
LowTwo step ownership is preferredvlayer · Veridise · 12 May 2025Open

The report gives no description here.

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.

vlayer: questions

Is vlayer audited?

Trustblock holds 1 public audit report for vlayer, dated 12 May 2025. The latest is by Veridise (“vlayer”).

Who audited vlayer?

Veridise wrote the report Trustblock holds for vlayer.

Are there open findings in vlayer’s audits?

5 findings are still open or acknowledged in the firms’ reports: 5 low (4 open, 1 acknowledged). Of 3 critical findings: all marked fixed by the firms. 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="vlayer"
></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