YSeed

How To Verify a BIP39 Seed Phrase Offline

Verification is a structure check: count, wordlist, and checksum. The safe version keeps the phrase inside a trusted offline workflow and refuses balance lookups.

Structure onlycount, wordlist, and checksum checksOffline-firstreal wallet phrases need controlled toolingNo balance checkvalidation must not become phrase exposure

Verify structure offline, not balances online.

To verify a BIP39 phrase offline, check the word count, confirm every word is in the BIP39 English list, and run checksum validation in trusted offline software. Do not use a balance checker or public phrase upload tool.

What does offline BIP39 verification check?

The first three checks are technical. The fourth is operational: the phrase must not leak while you are trying to verify it.

01 Count

BIP39 English phrases use standard word counts: 12, 15, 18, 21, or 24 words.

02 Wordlist

Each word must belong to the official 2,048-word English list.

03 Checksum

The final bits must match the hash-derived checksum for the encoded entropy.

04 Boundary

The phrase should not leave your trusted environment during the check.

Run the check before the phrase touches a live site.

A clean verification workflow should end with a yes/no structure result, not with more secret material copied across tools.

  1. Prepare a trusted offline environment or wallet-controlled workflow.
  2. Confirm the phrase has 12, 15, 18, 21, or 24 words.
  3. Check every word against the BIP39 English wordlist.
  4. Run checksum validation in offline software you trust.
  5. Record only the pass/fail result; do not copy the phrase into notes, cloud storage, or chat.
  6. If the phrase was ever exposed online, treat it as compromised and move funds from a clean wallet if any remain.

Which verification surface is safe?

Intent Safer path Avoid
Learn how validation works Use a public page with a test phrase generated only for learning. Do not paste a real wallet recovery phrase into a live page.
Check a real funded wallet phrase Use trusted wallet software or an offline environment you control. Do not use public validators, balance checkers, or support forms.
Confirm a backup after writing it down Verify word count and checksum in the same controlled ceremony before funding. Do not photograph or sync the backup just to compare it later.
Phrase was already pasted online Assume exposure, create a new wallet from a clean device, and move funds if possible. Do not keep testing the same phrase in more tools.

Stop if verification turns into wallet recovery.

Balance after paste

A page that needs the phrase before showing a balance can capture the phrase before any result appears.

Private key output

Verification does not require showing private keys, xpubs, addresses, derivation paths, or QR codes.

Support handoff

A request to continue in chat, screen share, extension, download, or copied command is outside safe validation.

Cloud convenience

Saving a phrase into screenshots, notes, passwordless documents, or synced clipboard history defeats offline checking.

No test mode

A safe educational page should work with demo phrases and should not pressure the user to paste a live wallet secret.

Wallet recovery claim

A validator can confirm structure. It cannot guarantee funds, restore success, ownership, or future compatibility.

A validator should not become a secret extractor.

YSeed keeps validation narrow because every extra wallet feature makes a public page more dangerous for people holding real recovery phrases.

No phrase backend

YSeed validation logic runs in the browser. Real phrases still belong offline because the surrounding device and extensions matter.

No balance lookup

A BIP39 checksum result is not a wallet lookup. YSeed does not derive addresses, query chains, or inspect balances.

No secret expansion

A verification workflow should not produce private keys, xpubs, derivation paths, addresses, or recovery exports.

No exposure excuse

Passing checksum never makes it safe to reuse a phrase that has been pasted into an untrusted page.

A pasted recovery phrase should be treated as exposed.

Do not keep testing it. If the phrase belongs to a wallet with funds, switch to a clean trusted device, create a new wallet safely, and move funds if any remain.

Open the emergency checklist

Check the workflow against primary references.

Offline verification is useful because BIP39 has a defined structure. It stays safe only when the phrase does not leave a trusted environment.

Offline verification FAQ

What does offline BIP39 verification prove?

It can prove that the word count, wordlist, and checksum are structurally valid. It does not prove the phrase has funds, belongs to you, or was generated safely.

Can I verify a real phrase on YSeed?

Use YSeed online only for demo or test phrases. Real wallet phrases should be verified in an offline environment or trusted wallet workflow you control.

Does checksum validation check wallet balances?

No. Checksum validation checks BIP39 structure. Balance information comes from blockchain data for derived addresses, which is a separate wallet operation.

What if the words are valid but checksum fails?

The phrase may be mistyped, incomplete, in the wrong language, from a nonstandard tool, or manually assembled without following BIP39 checksum rules.

Should an offline verifier show private keys?

No for a simple structure check. Showing private keys, addresses, or xpubs expands the risk surface and belongs only in advanced offline recovery tooling.

What if I already pasted my phrase into a public checker?

Treat the phrase as exposed. From a clean trusted device, create a new wallet and move funds if any remain.

Use the smallest safe surface.

Start with local generation, validate only structure, and treat any balance-check promise as outside the safety boundary.