Only the old P2PK utxo are vulnerable because they expose the public key. So you only need to crack the ECDSA and calculate a private key from the public key.
Very quickly P2PK was followed up by P2PKH and P2SH so only hashes are exposed in utxo. This means that before you get to the public key you need to reverse a double SHA256 and ripemd160 hash.

I would worry about just about anything on the internet before I would worry about btc.

In Euro we're still quite a way off from an ATH, about 5000 € (96.000 now, ath was 105.495)

That is taking a huge risk.
No major exchange will accept bitcoins that have gone through any known mixer.
Even the dust that accumulates on your bitcoin addresses should not be touched since it could taint the entire stash.

This is the store that sells it and here's the blogpost about it: It's in Dutch
https://www.storeofvalue.eu/nl/blogs/bitcoin-blog-nl/introductie-van-btclock-een-open-source-epaper-display?_pos=1&_sid=e4c930a0c&_ss=r

Yeah this clock is quite large. It measures 22x8.5cm or 8.6x3.3".

It's been running 1 week now and I've set it to show BTC/USD permanently, but with a LED flash every time a block is mined. Unfortunatelyu you cannot set it to show blockheight for xx sec and then return to BTC/USD. (or I did not find a setting that does it).

I have no clue where it gets the data from. But a setting is active that says 'use BTClock data source' and not the Nostr datasource.

I also bought one fully assembled.

This is its local website:

Check this out. Bitcoin clock, ticker, and much more.
Some dutch guy makes it. Really nice. Uses e-ink screens to display data. Assemble yourself or buy a fully operational unit.
https://github.com/btclock/btclock_v1

You really should not try to download the entire blockchain using a HDD, it will take literally weeks.
Do it on an SSD. After that just copy the entire thing over to your HDD. You'll save weeks.

First of all, I think that it's very unlikely from customs to inspect your computer and even if they decide to inspect, then how is encrypted disk space going to protect you? They'll force you to decrypt it or will seize your hardware.
Saving something on Google Drive is never a good idea.
[/quote]

That's why you use encrypted disk/files with hidden partitions (like VeraCrypt can do). If forced to decrypt you just give the standard password which decrypts to some wallet with only minimal value in it. The hidden partition is impossible to detect/prove and only accessible with the correct second password. When they seize your hardware you still have dozens of backups at home, online, whatever in the same encrypted container.

Van het partijprogramma van NVA wat betreft beleggingen, laatste alinea:

N-VA

Groeibedrijven willen we verder ondersteunen door het reglementaire kader inzake privaks, beleggingsfondsen en aandelenspaarplannen te versoepelen, zodat meer investeringen richting niet-beursgenoteerde groeibedrijven vloeien.
Tegelijk willen we Brussel als financieel centrum versterken. Het aantal genoteerde bedrijven op de Brusselse beurs kalft al jaren af. De toegang voor kleine lokale bedrijven tot de beurs moet makkelijker worden gemaakt. Een liquide en sterke beurs en een meer wijdverspreid aandelenbezit leiden tot meer welvaart
We verkopen niet-strategische overheidsparticipaties die niet tot de kerntaken van de overheid behoren. De opbrengst gaat naar schuldafbouw en naar investeringen in defensie, de klimaattransitie (bijvoorbeeld nieuwe kerncentrales) en digitalisering.
Belangrijke belastingverminderingen, bijvoorbeeld in het kader van pensioenopbouw of het ondersteunen van startende ondernemingen, behouden we en bundelen we in duidelijk afgebakende korven. Op die manier zorgen we voor meer fiscale neutraliteit voor sparen, investeringen, beleggingen en verzekeringen.
We willen het spaargeld activeren door de huidige vrijstelling van 833 euro voor dividenden uit te breiden naar alle inkomsten uit kapitaal, zoals bijvoorbeeld inkomsten uit beleggingsfondsen of aandelenspaarplannen.
We zorgen voor meer rechtszekerheid door voor inkomsten uit cryptomunten en andere occasionele inkomsten een vrijstelling tot een bepaald plafondbedrag te voorzien.

Bovendien is de ex minister van financien Van Overtveldt (die opkomt in Europa) een bitcoin hater.

Heeft er iemand al gevonden welke kandidaten (voor Belgie) er op de Europese lijsten staan die pro-bitcoin zijn ?

With 12 words you can only encode 16 bytes (128 bits). For 32 bytes you need 24 words. The word list contains 2048 words so 11 bits.

If you just want to backup a single WIF key using the word list, that is perfectly possible:

So let's take an example WIF key:
5JphUWRuWJwZktUdGBUmtsazoc1GGuRXFBxoTkJWZGpXjUzXXa7

We recalculate to the hex SEED using base58CheckDecode, this gives us the 32 bytes seed:
84A1A9C49C1257DE2D4FF2EEC4F6CF109E6BE3DF6E075EFB9AD895EFEAB20201

In binary this gives:
1000010010100001101010011100010010011100000100100101011111011110001011010100111 1111100101110111011000100111101101100111100010000100111100110101111100011110111 1101101110000001110101111011111011100110101101100010010101111011111110101010110 0100000001000000001

The SHA-256 checksum of this is:
45F4FD103DAAB39409C60F715E9A4B66D32322C7926ED2364169F232998D5808 or in binary
0100010111110100111111010001000000111101101010101011001110010100000010011100011 0000011110111000101011110100110100100101101100110110100110010001100100010110001 1110010010011011101101001000110110010000010110100111110010001100101001100110001 1010101100000001000

We take the first 8 bits of this hash to add at the end of the first binary bits:
So we add 01000101
and it becomes:
1000010010100001101010011100010010011100000100100101011111011110001011010100111 1111100101110111011000100111101101100111100010000100111100110101111100011110111 1101101110000001110101111011111011100110101101100010010101111011111110101010110 010000000100000000101000101
This is 264 bits length (which is divisible by 11 = 24 words)

Translating this to the BIP wordlist gives us:
lucky ask illness deal century upper release wrestle uphold chicken record cancel trade vehicle laundry science galaxy system renew cloth wrong flip amount chunk

This wordlist can be retranslated to the WIF at any time. It also contains an 8 bit checksum so you know. There is only a 0.4% chance that replacing one word will give you a correct checksum (1 in 256).

My fiat only arrived last week in my EU bank account.
They didn't even send an email announcing it ...

They've started the payments to creditors.

2024 update:

20BTC: 88 (26 intact)
10BTC: 107 (27 intact)
5BTC: 144 (49 intact)
1BTC: 589 (297 intact)

Seems a lot of the 1BTC have been cleaned out.
Intact means the bitbill contains as much (or more) value as indicated on the card.

The best way to do would be to convert the actual Bitcoin UTXO database into a SQL database so you can search it.
This database is kept on every node but it is a LevelDB database that can only be accessed sequentially.
So you need a translation software to read it.
I made one myself in Java. It takes about 1 hour to convert the full UTXO to a MYSQL database. It's about 24GB large when only a few fields are saved (addresses, balance, block height, txid). It contains 162 million records as of today.

You can then do a quick search to see if a specific address is in the database.
If found you can easily calculate the balance by doing a select count(*).
Running the queries would need a pc with a very fast random access SSD and as much ram as you can spare (think 128 or 256GB).

There's probably a few projects on GitHub that convert the UTXO.

And what about something liker a Trezor hardware wallet? They now have a built-in service called "coinjoin" which in my view is nothing else but a mixer. So will anything about Trezor also be banned

If you have Bitcoin-QT installed you could also simply:
- create a new empty wallet
- import your self-made WIF key
- take a look at the corresponding public key it calculates. easiest way is to enable coinControl features and start a send_transaction to see the list of all public keys.

If you're using SecureRandom in JAVA that is as strong as it's going to get.
Creating a secure private key is as simple as calling nextBytes on a 32 byte byte[].
The only edge case here is that you have to check for the upper limit of the key.

Creating P2PKH or P2SH bitcoin addresses is NOT that difficult and the number of edge cases is limited.

I believe a self-written, properly tested paper wallet generator is MUCH safer that using whatever you can find on the internet now.