Fragmetric Restaking Program security record

As of 19 Nov 2026, Fragmetric Restaking Program has 4 audit reports by 2 security firms on Trustblock; the latest is by Quantstamp, dated 8 Oct 2025. Those reports list 1 open critical finding.

Critical findings
1 open critical finding
Reported in “Fragmetric v1” by Certora, Oct 2024. Not marked fixed in that report. See the findings
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.

Audits4

Newest first

ReportSecurity firmDateScopeCritical findingsSource
Fragmetric Liquid Restaking Program - 2Security firm: QuantstampDate: Scope: Not recorded; see the reportNone opencertificate.quantstamp.com ↗
Fragmetric Liquid Restaking ProgramSecurity firm: QuantstampDate: Scope: Files listedNone opencertificate.quantstamp.com ↗
Fragmetric Restaking ProgramSecurity firm: QuantstampDate: Scope: Files listedNone opencertificate.quantstamp.com ↗
Fragmetric v1

Includes formal verification

Security firm: CertoraDate: Scope: Not recorded; see the report1 open critical findingGitHub ↗

Findings32

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

SeverityOpenAcknowledgedFixedMitigated
Critical1000
High1020
Medium0121
Low2320

The firm marks these findings Mitigated. They are not counted as open, acknowledged or fixed.

MediumSignature Replay Attack Allows for Increased RewardsFragmetric Restaking Program · Quantstamp · 24 Oct 2024Mitigated

The protocol allows users to benefit from an accrual rate based on the wallet they use to deposit. The protocol relies on the on-chain `ed25519 program` to verify signatures related to metadata that the user supplies. The metadata needs to be signed by the admin, and the user passes that signature to the `ed25519 program` by placing the instruction before the `deposit`: ``` let current_ix_index: usize = instructions::load_current_index_checked(instructions_sysvar)?.into(); let ix = instructions::load_instruction_at_checked(current_ix_index - 1, instructions_sysvar)?; require_eq!(ix.program_id, ed25519_program::ID); ``` The `ed25519 program` will verify that the admin private key signed the metadata, indicating that the metadata is safe to use. However, there is no way to cancel a valid signature, this is because the signed data only includes the wallet name and the accrual rate related to it, but no information about an expiry time: ``` pub struct DepositMetadata { pub wallet_provider: String, pub contribution_accrual_rate: u8, // 100 is 1.0 } ``` There is also no way to verify that the user used the same wallet to deposit as the one specified in the `wallet_provider` unless the verification is done through the front end. However, users can still interact with the program directly, use whatever wallet they want with valid metadata, and get the accrual rate.

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="fragmetric-restaking-program"
></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