Inicio › I have a private key and I don't want to import it yet

I have a private key and I don't want to import it yet

Looking and spending are different operations

A private key has a public counterpart derived from it, and the address comes from that public part. The path runs one way: private gives you public gives you address, but you cannot walk back from the address.

Which means to see how much is there you only need the address, and the address is not secret — it is written into every transaction you ever received. To move funds you need the private key. Two separate operations, and people routinely collapse them, exposing a key to answer a question that never required it.

If you hold a paper wallet, the address is most likely printed right next to the key. That address is all you need to look.

The real risk of importing in a hurry

Importing means loading the private key into software. From that moment your funds are only as safe as that computer: a clipboard sniffer, or software that is not what you thought it was, and the key has left the paper and does not go back.

There is an asymmetry worth holding onto: checking a balance cannot go badly wrong, importing can. So the sane order is look first, decide second, and only then choose how to move.

Sweeping is not the same as importing

When you do decide to move funds you will meet two verbs, and they are not synonyms.

Importing adds the key to an existing wallet. The old key stays valid — and stays valid for anyone who ever saw that paper: a relative, whoever printed it, whoever photographed it.

Sweeping builds a transaction sending everything to a new address controlled by a key only you hold. The old key is left empty and it stops mattering who saw it.

For a paper wallet of uncertain provenance, sweeping is almost always right. Importing keeps alive a key whose history you do not control.

If someone gave it to you, assume someone else has seen it

A paper wallet you received as a gift, bought pre-made, or found in a drawer has an invisible problem: you do not know how many copies exist. Whoever generated it could have kept one, and no amount of looking at the paper will tell you.

That does not mean the funds are gone — it means the clock is running. If you are going to move them, sweep to an address of your own rather than importing, and never reuse the old address.

Nobody who asks for your key is helping you

Asking about this publicly tends to attract private messages offering to sort it out. The rule has no exceptions: there is no legitimate reason for a third party to need your private key or your twelve words. Not to check a balance, not to recover anything, not to verify whether it is valid.

The address can be shared without risk of theft — it costs privacy, because it becomes linked to you, but not funds. The private key is never shared.

The principle, beyond this case

Almost everything worth checking about a backup can be checked from the public side. Bitcoin Core arranges it that way deliberately: there is a notion of a watch-only wallet with private keys disabled, precisely to separate observing from spending. Its own documentation puts it plainly when describing how to build one: "Create a watch-only descriptor wallet (blank, private keys disabled)" — doc/descriptors.md.

The same logic applies to what you already have stored: you can verify that your backup reproduces the address you expect without writing your seed anywhere. That turns "I think my backup works" into "I checked", which are different things.