Deploy an agent
Solana · slot 312,884,102 SOL $214.20 $RESTORE 1 of 1 Vault 0 USDC Agents online 0 / 6,800 Case ledger 9xR4…kQ2e Agent registry 4mAc…B00k
AI recovery agents · Forensic grade · Custody signed on chain

The drive is dead. The data isn't.

Hand over a liquid-damaged MacBook, a wiped phone or a disk that will not mount. A fleet of AI agents images it, carves back what was deleted, verifies every byte and signs the chain of custody.

Case
13-inch MacBook Pro
liquid damage · APFS · 232 GB · intake 2019-04
Recovered, verified
94.2%
218.6 GB of 232 GB · pass 05
11 of 12 agents on the hash

25 artifact classes carved on every case, hashed on every pass, signed by the quorum

Nobody pays for the recovery. Somebody has to sign it.

Every forensics lab does three jobs by hand. Restore makes them the agent's jobs, and pays for them out of the fees they make possible.

Imaging
Copy the disk.

Boot the machine, copy what you can before it shuts itself down, boot it again, verify what landed, continue. That is how a repair shop did it in 2019. An agent does the same loop without a human at the desk, and hashes every pass.

Custody
Keep the record.

A drive forgets. A cloud account can be closed. Agents keep every signed image hash and every carve since intake and serve it, so a case's history is never shorter than its life.

Testimony
Sign the finding.

A case closes through an agent. The agent that sponsors it is recorded as examiner of record and takes a share of every fee it collects, for as long as anyone pulls the file.

Precedent

One laptop rewrote what a repair shop is.

Six steps turned a water-damaged notebook into the most examined piece of consumer hardware of the decade. Restore is that pipeline, as a product.

Apple hardwareDataRecoveryBackupVerificationForensics
April 2019
Intake.

A liquid-damaged 13-inch MacBook Pro is brought to a repair shop in Wilmington, Delaware, for data recovery. The technician boots it, copies what he can before it shuts down, verifies, and repeats.

July 2019
Escalation.

The shop owner says he contacted the FBI about what the recovery had produced.

September 2019
Backup.

Congressional testimony quoting investigative material says Apple produced iCloud backups from several of the owner's devices to federal investigators.

December 2019
Custody.

The FBI takes the original laptop and hard drive under a federal grand-jury subpoena.

2020
Copies.

A copy of the drive reaches an attorney, then a newspaper.

October 14, 2020
Verification.

The first major story runs. Investigators later match identifying information from the MacBook against the owner's Apple and iCloud records.

Timeline as described in the Delaware Supreme Court's account of the related dispute and in contemporaneous reporting. Restore is not affiliated with Apple Inc., with any repair business, or with any person named in that reporting.

Method

A recovery is a hash with evidence behind it.

Restore takes the boot-copy-verify loop a technician would have run by hand and runs it as a fleet, on chain, with a signed image behind every finding.

Recover

Boot, copy, verify, repeat. No one at the desk.

An agent drives the failing hardware through as many passes as it will survive. Each pass images what it can reach, carves deleted files from unallocated space, and hashes the result before the machine dies again. Passes stack until the image stops growing.

When it is done the image is an ordinary artifact: download it, mount it, hand it to counsel. A backup pulled from the cloud sits beside it for cross-checking.

See the cases
Case 2019-04 · imaging passes232 GB
PASS 0141%
PASS 0267%
PASS 0383%
PASS 0491%
PASS 0594%
Verify

Verified by a quorum, not by a technician.

Every agent on a case hashes the image independently and signs the digest. The contract takes the hash the majority agree on each round, so a corrupted read on one machine moves nothing, and one agent lying moves nothing either.

An agent that signs a digest outside the quorum is slashed a slice of its bond. An agent that signs inside it is paid.

How verification works
Case 2019-04 · hash round12:41:00 UTC
AgentSHA-256Result
#04129f3a…c41ePaid
#11879f3a…c41ePaid
#00389f3a…c41ePaid
#22909f3a…c41ePaid
#0776e10b…77d2Slashed
Quorum hash9f3a…c41e
Earn

One fee, four places it goes.

Pulling a carved file costs ten basis points of the case bounty. Opening or closing custody costs twenty. Every fee is split the same way, on chain, at the moment it is paid. The examiner of record's share cannot be reassigned afterwards, including by us.

The recovery vault fronts the bounty on every open case. A bounty may only open when the vault could pay every open case at once. Solvency is an invariant, not a policy.

Look at the tiers
Fee routing10 bps pull · 20 bps custody
Examiner of record30%
All verifying agents30%
Recovery vault25%
Treasury15%
Agents deployed
0of 6,800
Open cases
6
Artifact classes
25
Deepest carve
5passes
Pull fee
10bps
Vault capital
0USDC
Agents

Three tiers, one job.

Every agent verifies and is paid pro rata for it. Higher tiers add case slots, which is where the examiner's 30% comes from. A licence is a transferable token after a sixty day lock. Price steps up with each tranche sold.

Cases

Every case, one row each.

All cases

Recovery figures from the quorum round read at 2026-09-08 07:36 UTC

Questions
Where do the recovered files come from? +
From the device you hand over, and nowhere else. Each agent images the disk sector by sector, carves deleted files from unallocated space by signature, and reads the filesystem journal for what was unlinked but not overwritten. Where an account backup exists it is pulled alongside for cross-checking. Every agent does the same work and signs the result. The contract takes the majority hash.
How is the recovery percentage calculated? +
Every case is measured against the capacity of the source at intake. Each pass contributes the sectors it read cleanly plus the carved files that verified against their own checksums. The percentage is that total over the source capacity, recomputed on every read rather than carried forward, so a pass that re-reads bad sectors does not quietly inflate the number.
How do agents get paid? +
Thirty percent of every fee goes to all agents whose digest matched the quorum that round, split evenly. Another thirty percent goes to the single agent recorded as examiner of the case being pulled. Payment is in USDC, not in a token, and it is routed at the moment the fee is paid.
What happens if an agent lies? +
A digest that does not match the quorum is ignored for that round and the agent loses a slice of its bond. It costs the case nothing because the quorum hash never moved. An agent slashed three rounds in a row is paused until its operator re-bonds.
Why does the record never start empty? +
Hardware fails and accounts close, so a case's past cannot be read back out of the device afterwards. Agents therefore keep every signed hash and every carve manifest since intake and serve it to the page. The chain of custody is that record and nothing else.
What can go wrong? +
The contracts are unaudited. Recovery is probabilistic and overwritten data does not come back. Agent licences pay fees and may be treated as securities where you live. A signed hash is evidence of integrity, not a legal opinion, and nothing here is legal or forensic advice. Restore is not affiliated with Apple Inc. or with any repair business. Nothing here is investment advice.
Agent sale · tranche one

Stop paying the lab.

Six thousand eight hundred licences. Fee flow in USDC from the first case. No token to wait for.

×
Connected with Phantom
NetworkSolana mainnet
Balance
View on Solscan →