SecondFi (ex Yoroi): the Asset Recovery Tool is now live

The tool went live on October 7

SecondFi activated its Asset Recovery Tool on October 7, 2026. Its official account (@secondfiapp) announced it at 05:16 UTC —02:16 in Chile—: “The Asset Recovery Tool Is Now Live”.

It was expected by the end of September and shipped a week later. One fact deserves to lead: NIGHT, the night token, is in fact recoverable, and it is in writing in the terms you must accept before using the tool. The announcement does not mention it even once.

It runs in the browser only, at secondfi.io, and does not require a prior ticket. Recovering assets is not the same as migrating the wallet: that process is covered in the guide to migrating from Yoroi to SecondFi. The entire interface is in English only, a real barrier for the affected Spanish-speaking community.

How the process works

The announcement describes four steps:

1. Prove control of the wallet —“Enter the recovery phrase for one affected wallet”, with 12, 15, or 24 words—.
2. Review which assets are eligible.
3. Enter the destination address.
4. Generate the proof and submit the request.

Generation takes about 15 minutes and downloads close to 2 GB; the request is processed in batches, taking up to 5 business days.

What you see on screen

The scan is not a silent button: the app reports it with fixed strings —“We are checking your wallet keys against the list of compromised addresses”, “Checked {checked} of {total} keys”, “Scanning accounts 0 to {max}”, “Scanned {count} keys”— and, when there are matches, “Suspected keys detected”. It can take a few minutes: it is not frozen.

When it finishes, the results screen classifies each affected address and shows what you can recover on each one: in a whitehat sweep, your ADA, your tokens, and your NFTs; in an attacker drain, ADA and some popular tokens only. The amount is an estimate, and non-returnable NFTs add 30 ₳ to the ADA for that address; they do not subtract.

The destination is locked inside the proof (it cannot be changed after submission): an address linked to the incident or a script address is rejected, the network is validated, and a FATF / Travel Rule notice appears if the destination is an exchange. The app also requires a countdown wait (“Wait {sec} seconds…”) before confirming: it is an anti-rush measure, not an error.

During generation, the screen runs through these stages:

1. Initialising proving engine…
2. Downloading constraint system…
3. Verifying eligible assets…
4. Preparing recovery request for address {current} of {total}…
5. Submitting recovery request…

That is where the ~2 GB is downloaded and the ~15 minutes go. Each address also shows its status: To recover · Submitted · Transferred · Nothing to recover · Check failed.

If something is interrupted, and what to have ready

None of this forces you to start over: if the connection drops or the browser runs out of memory (“Your browser ran out of memory”), the app resumes with “Picking up where you left off”, retries on its own, and offers a diagnostic log.

Two precautions: generation needs ~2 GB of RAM, so close other tabs; and do not refresh the page during the ~15 minutes, because the window is kept open on purpose.

Besides the phrase, it accepts an encrypted QR backup of the chimera type (CIP-0301) or the root key (xprv) imported with a password, both decrypted locally; it validates that the first derived address is the correct one.

Requirements: 2 GB of RAM, a processor no more than 5 years old, and at least 50 Mbps.

What the announcement does not say

The app and its Recovery Terms —not the announcement— document three things that change how the process is understood.

NIGHT is in fact recoverable

Clause 3.1(a) lists the assets recoverable “in kind”: ADA, NIGHT, SHEN, STRIKE, iUSD, MIN, SURF, WMTX, STUFF, USDM, IAG, VIPER, INDY, BODEGA, PALM, FLDT, HOSKY, COPI, USDA, and DRIP —twenty tokens—. The night token is on the list. The complaint the community carried all through September is answered —in the terms, not in the launch tweet—.

Two policies, two treatments

The tool classifies each affected address and shows it on screen. The two main treatments are these (the app also records the `friend` and `mixed` categories):

Policy	What happened	What is recovered
Whitehat sweep	The funds were swept to protect them from the attackers	“You receive back exactly what was removed — ADA, tokens, and NFTs”
Attacker drain	Taken by “a non-cooperating criminal”	ADA and some popular tokens only; the less common tokens and the NFTs do not come back. Requires checking “I understand some stolen assets may not be recovered”

This clears up a common confusion: the 16.1M ADA stolen across 374 wallets reported by the official statement (attacker drain) and the ~129M ADA secured —the ones the tool labels as whitehat sweep— are two distinct pools, with two levels of restitution. What was secured is in custody and comes back in full; what was stolen comes back only in ADA and popular tokens.

Recovery follows order of arrival

The terms set a hard rule (clause 5.6): the result is transferred to the address “specified in the first Recovery Request that successfully completes verification and processing”. With 4.4 —SecondFi must not determine ownership— and the closing words of 4.2 —a proof verifies control, not that the credentials were never copied—, the conclusion is clear: on an address whose credentials were exposed, whoever proves control first wins.

What the design does with your seed phrase

It is established in the design and in the Recovery Terms, and the code your browser downloads backs it up —without being an absolute guarantee verifiable from the outside—. We read it from the production bundle without entering any phrase or running the flow: it is not an independent security audit, nor a guarantee by this site.

• The app scans the phrase locally against the list of compromised addresses.
• The circuit proving key is downloaded to your browser: the `ownership.pk` file weighs 1.07 GB, which explains the ~2 GB download (proving key, constraint system, and WASM).
• The secrets are wiped from memory when you leave the page.
• The prover verifies the proof locally before submitting it.

Clause 4.5 makes it precise: SecondFi “does not require you to disclose or transmit a recovery phrase” and requires the credential to stay on your device, outside any field other than the official local component. What can be checked is that the phrase is used and the proof is generated on your machine. What cannot be checked from the outside is that the phrase is not transmitted under any circumstance: that depends on the JavaScript in force at the moment you use it.

Who built the tool (an inference)

The repo Emurgo/proof-tool holds 244 commits from a contributor (`colll78`) who lists “Anastasia Labs” as the company, and Phil UPLC (@phil_uplc), CEO of that company, marked the launch. The terms mention only “third parties in collaboration with SecondFi” (4.2): that Anastasia Labs built the tool is a reasonable inference, not an official announcement.

How to verify you are on the right site

Before typing the phrase, two minutes:

• Type the domain by hand: `secondfi.io`. Do not arrive through a link from a message, an email, or an ad; the two shorteners in the official announcement resolve to `https://secondfi.io/`.
• Do not install any extension that claims to be necessary for recovery: it is not.
• Nobody charges for this: SecondFi does not ask you to pay a fee to unlock recovery, and does not ask for the phrase outside the official tool (7.4).

And an honest warning from SecondFi itself: some anti-phishing extensions may show an alert or a blank screen because the tool asks for the phrase. That, on its own, does not mean the official tool is malicious.

The fine print you should read

The Recovery Terms have 11 sections and are effective September 12, 2026; the accept button is enabled only at the end. Five points:

• A very broad release. On receiving the assets, you release the SecondFi Parties “irrevocably and unconditionally” for everything related to the incident, the wallet, and the tool (6.5 and 6.6). It is not absolute: 6.5 itself excepts the rights the law does not allow you to waive and the claim for what you accepted and were not delivered. The mandatory checkbox in the app is that.
• Liability cap: USD 10,000 (9.3) for errors in determining eligibility and for any other claim. It does not apply if you accepted a result and were not delivered it: there it answers for the value of what was not delivered (9.3(a)).
• Governing law and forum. Singapore law governs, with ICC arbitration in Tokyo in English and class action prohibited (11.1).
• Audit discounted by contract. The zkSecurity report exists, but clause 4.3 states that “An audit, security review… does not constitute a representation, warranty or guarantee”.
• You pay the fees. SecondFi does not charge for submitting the request (7.1); network, taxes, and reports are on you, unlike the migration.

Excluded are liquidity pools, delegated positions (how to delegate your stake), unprotected staking, governance and voting rights, assets received after the incident, taxes, and fees (3.3); the determination is final, with a single review in the following 7 days (3.4); for whatever SecondFi contributes from its own resources, you assign your claims to it against whoever took the assets (5.7); by claiming you ratify the Protective Measures (2.5); and the release and the assignment survive (11.3).

What the community says

Three voices from the community:

• @Chuntingkw95978 (Sep 9): “We just want our ADA back, like you promised.” The mismatch the announcement does not address: the community is asking for restitution, not tools.
• @Brian52343644 (Sep 14): “I am glad to see you are taking the time to do it right. I also had a good chunk in NIGHT that went down the drain, but the priority is ADA.” He prioritizes ADA and warns that scammers are still exploiting the confusion.
• @YUBYEONGCHAN (Sep 14): “The 3rd unfreezing already finished, but I do not see the airdrop.” A concrete datum: an unlock that already happened and did not arrive.

Frequently asked questions

What is still unanswered

• The thaws 3 and 4 of the night token that reach a compromised wallet: the terms exclude assets “received after the Incident” (3.3), and the claim of several users remains open.
• If an attacker submits the request first: clauses 5.6 and 4.4 leave that scenario without a clear ownership mechanism.
• Who pays the NIGHT redemption fee from a compromised wallet: the unlock calendar is published, that point is not.
• The role of Intersect in the custody of the secured assets, and whether the Final Recovery Offer is mandatory or appears only when there are discrepancies.

The NIGHT calendar, with dates

The tokens are not lost: they unlock on a calendar. The distribution runs in four equal installments of 25%, and the first unlock for each address falls on a random date between day 1 and day 90. From there, each address takes between 270 and 360 days to unlock completely. The portal is open for 450 days —360 of thawing plus 90 of grace—: thawing ends on December 4, 2026, and 90 days of grace remain before closing.

With those dates, anxiety turns into a plan. What remains unanswered is not the calendar, but who pays the redemption fee from a compromised wallet.

The full timeline is in what happened in the SecondFi and Yoroi exploit and in when the ZK tool was going to launch. If you are choosing what to continue with, look at the Cardano wallets compared.

This article is informative: it is not legal, financial, or security advice. Before entering your seed phrase, confirm the official domain and read the Recovery Terms.

Sources

• @secondfiapp — “The Asset Recovery Tool Is Now Live”
• secondfi.io · support.secondfi.io · kb.secondfi.io
• zkSecurity audit report · Emurgo/proof-tool

Facts and timelines: official statement from @secondfiapp and the Recovery Terms. Technical details: the repository and the public bundle of the application.