ClayStack security record

Ethereum, Polygon (POS)claystack.comX

As of 3 Nov 2026, ClayStack has 4 audit reports by 3 security firms on Trustblock; the latest is by Nethermind Security, dated 25 Jan 2024. Those reports list no open critical findings.

Critical findings
No open critical findings
Across the 4 reports, 1 critical finding was reported. It 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

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

Audits4

Newest first

AuditSecurity firmDateScopeCritical findingsReport
Claystack security reviewSecurity firm: Nethermind SecurityDate: Scope: Not recorded (see the report)1 critical finding, fixedOpen · GitHub
Claystack/Matic platformSecurity firm: ChainSecurityDate: Scope: Files named in the reportNo open critical findingsOpen · chainsecurity.com
ClayStackSecurity firm: QuantstampDate: Scope: Files named in the reportNo open critical findingsOpen · certificate.quantstamp.com
Claystack Matic platformSecurity firm: ChainSecurityDate: Scope: Files named in the reportNo open critical findingsOpen · chainsecurity.com

Findings42

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

SeverityOpenAcknowledgedFixed
Critical001
High000
Medium001
Low0634
CriticalClaiming withdrawals on EigenLayer can be done without updating internal accountingClaystack security review · Nethermind Security · 25 Jan 2024Fixed

The report gives no description here.

Open the report
MediumNo Message Relayed on claimClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowDecoding InefficienciesClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowIncorrect PermissionsClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowInefficient ModifierClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowLogic ContractClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowMissing CheckClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowMissing whenNotPaused in Migrate DelegationClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowNo Limit On Withdrawal and Deposit Fee AmountsClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowPossible UnderflowClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
Show 10 more
LowRedundant FunctionClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowRedundant Storage VariablesClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowReuse balanceOf Result When PossibleClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowStaking IssuesClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowStorage Operations in LoopsClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowValidator Contract Check Not Strict EnoughClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowVariables Could Be ImmutableClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowWrong Variable LoggedClaystack/Matic platform · ChainSecurity · 29 Nov 2022Fixed

The report gives no description here.

Open the report
LowMissing InitializersClayStack · Quantstamp · 26 Sep 2022Fixed

`ClayManager` is missing a call to `__UUPSUpgradeable_init()` in the `initialize()` function. Though the function may be empty, it is important to call the initializer in case this changes in future version upgrades.

Open the report
LowMissing Input ValidationClayStack · Quantstamp · 26 Sep 2022Fixed

Some functions do not validate their inputs, which can result in unexpected behavior by the contracts. A non-exhaustive list includes: * `ClayManager.initialize()`: Validate that `_csToken` is a non-zero address. * `ClayManager._claim()`: Validate that `claimVault` is a non-zero address. * `ClayManager.earlyClaim()`: * Validate that order exists. * Validate that `claimVault` is a non-zero address. * Validate that the order cannot be claimed through ordinary means.

Open the report
Show 10 more
LowPrivileged Roles and OwnershipClayStack · Quantstamp · 26 Sep 2022Fixed

Certain contracts have state variables, e.g. `TIMELOCK_UPGRADES_ROLE`, which provide certain addresses with privileged roles. Such roles may pose a risk to end-users. The `ClayManager` contract contains the following privileged roles: * `onlyProxy` modifier-guarded functions * `initialize()` -- initialize the contract's variables post-deployment. * `upgradeTo()` -- upgrade the implementation of the proxy to a new contract. * `onlyRole(CS_SERVICE_ROLE)` modifier-guarded functions * `setBridgeFee()` -- set the fee to manually trigger the bridge by user in matic * `setBridgeRequirements()` -- set the days and amounts required for bridge transfers * `setMinClaimDays()` -- set the minimum number of days to claim tokens when netted locally * `pause()` -- pause the contract * `unpause()` -- unpause the contract * `onlyRole(TIMELOCK_UPGRADES_ROLE)` modifier-guarded functions * `setTreasury()` -- set the treasury wallet * `setClaimVault()` -- set the vault to which MATIC tokens will be sent * `upgradeTo()` -- upgrade the implementation of the proxy * `_authorizeUpgrade()` -- require a certain sender to be used (when upgrading the implementation) The `CsToken` contract contains the following privileged roles: * `onlyClayMain` modifier-guarded functions * `mint()` -- mints tokens to an address, increasing the total supply * `burn()` -- burn an amount of tokens from an address, reducing the total supply The `UserProxy` contract contains the following privileged roles: * `onlyProxy` modifier-guarded functions * `initialize()` -- initialize the contract's variables post-deployment. * `upgradeTo()` -- upgrade the implementation of the proxy to a new contract. * `onlyRole(TIMELOCK_ROLE)` modifier-guarded functions * `processInsurance()` -- process insurance towards ClayMatic donation and fees * `onlyRole(TIMELOCK_UPGRADES_ROLE)` modifier-guarded functions * `setClaimVault()` -- sets the vault to which matic tokens will be sent * `setTreasury()` -- set the treasury wallet * `upgradeTo()` -- upgrade the implementation of the proxy * `_authorizeUpgrade()` -- require a certain sender to be used (when upgrading the implementation) * `onlyRole(CS_SERVICE_ROLE)` modifier-guarded functions * `pause()` -- pause the contract * `unpause()` -- unpause the contract The `ClaimVault` contract contains the following privileged roles: * `claimFunds()` requires the sender to be `clayManager`.

Open the report
LowReliance on `fxRootTunnel` to Be Working as ExpectedClayStack · Quantstamp · 26 Sep 2022Fixed

The `ClayManager` contract is responsible for completing the process of a batch order that is specified by `batchID` in polygon, using `ClayManager._processMessageFromRoot()`. This function is designed and expected to be called only once. However, these functions have no protection against replay attacks. Though `_processMessageFromRoot()` prevents the same `_stateId` from being used twice, it does not prevent the same `_batchId` from being passed into `_registerClaimProceeded()`. `_registerClaimProceeded()` being executed more than once for a `_batchId` is an unexpected condition and could cause negative consequences to the platform.

Open the report
LowUnchecked Return ValueClayStack · Quantstamp · 26 Sep 2022Fixed

Most functions will return a `true` or `false` value upon success. It is important to ensure that every necessary function is checked. `UserProxy.deposit()` does not check the return value of its call to `clayMatic.deposit(amount)`.

Open the report
LowUnlocked PragmaClayStack · Quantstamp · 26 Sep 2022Fixed

Every Solidity file specifies in the header a version number of the format `pragma solidity (^)0.8.*`. The caret (`^`) before the version number implies an unlocked pragma, meaning that the compiler will use the specified version _and above_, hence the term "unlocked".

Open the report
LowIncorrect PermissionsClaystack Matic platform · ChainSecurity · 23 Mar 2022Fixed

The report gives no description here.

Open the report
LowInefficient ModifierClaystack Matic platform · ChainSecurity · 23 Mar 2022Fixed

The report gives no description here.

Open the report
LowLogic ContractClaystack Matic platform · ChainSecurity · 23 Mar 2022Fixed

The report gives no description here.

Open the report
LowMissing CheckClaystack Matic platform · ChainSecurity · 23 Mar 2022Fixed

The report gives no description here.

Open the report
LowMissing whenNotPaused in Migrate DelegationClaystack Matic platform · ChainSecurity · 23 Mar 2022Fixed

The report gives no description here.

Open the report
LowNo Limit On Withdrawal and Deposit Fee AmountsClaystack Matic platform · ChainSecurity · 23 Mar 2022Fixed

The report gives no description here.

Open the report
Show 6 more
LowPossible UnderflowClaystack Matic platform · ChainSecurity · 23 Mar 2022Fixed

The report gives no description here.

Open the report
LowReuse balanceOf Result When PossibleClaystack Matic platform · ChainSecurity · 23 Mar 2022Fixed

The report gives no description here.

Open the report
LowStaking IssuesClaystack Matic platform · ChainSecurity · 23 Mar 2022Fixed

The report gives no description here.

Open the report
LowStorage Operations in LoopsClaystack Matic platform · ChainSecurity · 23 Mar 2022Fixed

The report gives no description here.

Open the report
LowValidator Contract Check Not Strict EnoughClaystack Matic platform · ChainSecurity · 23 Mar 2022Fixed

The report gives no description here.

Open the report
LowWrong Variable LoggedClaystack Matic platform · ChainSecurity · 23 Mar 2022Fixed

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.

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