Landshare security record

Arbitrum, BNB Chain, Ethereum, Polygon (POS)landshare.ioXGitHub

As of 3 Nov 2026, Landshare has 1 audit report on Trustblock, by QuillAudits, dated 30 Jul 2024. That report lists no open critical findings.

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

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

Audits1

Newest first

AuditSecurity firmDateScopeCritical findingsReport
LandShareSecurity firm: QuillAuditsDate: Scope: Files named in the reportNo open critical findingsOpen · quillaudits.com

Findings11

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

SeverityOpenAcknowledgedFixed
Critical000
High005
Medium000
Low303
LowLack of Zero Address Checks for Addresses Set in ConstructorsLandShare · QuillAudits · 30 Jul 2024Open

The constructors of all four audited contracts (CrossChainVault, CrossChainReceiver, CrossChainSender, and CCIPTokenSender) do not currently include checks to prevent zero addresses from being set. If any of these addresses are inadvertently set to the zero address, it could lead to the contracts being in an incorrect or unusable state, potentially causing operational issues and security vulnerabilities.

Open the report
LowPotential Gas Reversion in getFailedMessagesIds Function Due to Large Number of EntriesLandShare · QuillAudits · 30 Jul 2024Open

The getFailedMessagesIds function retrieves the IDs of failed messages by iterating over the entire s_failedMessages map. If the number of failed messages is large, this loop could consume excessive gas and potentially cause the transaction to revert due to reaching the gas limit.

Open the report
LowRisk of Improper Contract State Due to Manual Allowlist ConfigurationLandShare · QuillAudits · 30 Jul 2024Open

The contracts rely on strict access control mechanisms, where each contract has specific counterparties it should accept transactions from:• CrossChainVault should accept transactions only from CrossChainReceiver. • CCIPTokenSender should accept transactions only from CrossChainVault. • CrossChainReceiver should accept transactions only from IRouterClient. • CrossChainSender is available for all token holders • CCIPTokenSender should accept transactions only from trusted addresses However, the allowlists are managed via separate instructions from the contract owner. If the allowlist configurations are set incorrectly, the contracts could end up in an improper state, potentially leading to security vulnerabilities or operational failures. It is crucial to document the access control processes thoroughly and ensure that the allowlist configuration is managed carefully to prevent such issues.

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

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="landshare"
></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