Things I’ve gotten wrong:
- recommending Liquid
- recommending Jade
- recommending Lightning
- thinking that AI was a scam
What steps have I taken to prepare for what’s coming?
Don’t use any L2s; everything that’s been built around Lightning has also failed and will fail—Lightning is too complex a protocol.
Stick to L1, and if you’re looking for privacy, use CoinJoin.
Login to reply
Replies (31)
What’s wrong with Jade wallet?
@npub1jg55...6n8n
Technical question for the Blockstream/Jade team regarding Jade Classic (original ESP32) + No-Radio firmware, especially around v1.0.40.
In v1.0.40, Jade initialized its 256-bit entropy state with:
bootloader_random_enable();
esp_fill_random(entropy_state, 32);
bootloader_random_disable();
On the original ESP32, bootloader_random_enable() enables the SAR ADC entropy source when RF/Wi-Fi/Bluetooth are disabled.
The point I am trying to understand is the entropy extraction rate.
For ESP32 Classic, esp_random() uses:
APB_CYCLE_WAIT_NUM = 16
With an 80 MHz APB clock, this corresponds to a minimum enforced interval of ~0.2 us between RNG reads (~5 MHz theoretical maximum, excluding execution overhead).
However, the ESP32 Technical Reference Manual recommends reading RNG_DATA_REG at no more than ~500 kHz when using the SAR ADC in order to obtain maximum entropy, which corresponds to ~2 us per 32-bit read.
So there appears to be a difference between:
SAR ADC recommendation:
<= 500 kHz
> = ~2 us/read
esp_random() on ESP32 Classic:
> = ~0.2 us/read minimum enforced delay
> ~5 MHz theoretical maximum
Espressif also uses a much more conservative extraction rate in its bootloader RNG code when the SAR ADC is the entropy source.
At the same time, Espressif explicitly documents bootloader_random_enable() + esp_random()/esp_fill_random() as a valid way of obtaining true random numbers when RF is disabled.
Jade later changed this logic and now performs individual esp_random() calls separated by ~1 ms, explicitly mentioning additional time for HWRNG entropy refeeding and scheduler jitter.
My questions are:
1. Did Blockstream measure or estimate the min-entropy of esp_fill_random(32) on ESP32 Classic with bootloader_random_enable() active and RF disabled?
2. Was the ESP32 TRM recommendation of <=500 kHz for maximum SAR entropy considered?
3. Is there a known lower bound for the min-entropy of the 256-bit entropy_state generated by Jade v1.0.40 in this configuration?
4. Was the later 1 ms delay purely defense-in-depth, or was it also intended to remove uncertainty about the SAR entropy refresh rate on the original ESP32?
5. Does Blockstream consider a 12-word BIP39 mnemonic generated on Jade Classic + No-Radio + v1.0.40 to retain the full expected 128 bits of entropy?
I am not claiming a demonstrated vulnerability. I am trying to understand how the entropy guarantees of Espressif's SAR ADC/HWRNG path were evaluated in Jade.
View quoted note →
Good on you to speak out.
What wallet is good then? Seems they’re all having problems lately
The only secure option is multi-signature and using different manufacturers.
I also don't recommend those setups that use only Bitcoin Core because, while I agree that Bitcoin Core is the most thoroughly reviewed software, you end up relying on a single piece of software and a single point of failure.
If you want something very private to do you can always swap btc with Moreno though only makes sense for vey private things. I would not keep Monero long term for sure.
Man, that’s really going to reel in the masses lol. I guess Bitcoin will never be simple and will always carry a huge risk
Well, here's a theory that people don't usually like.
Bitcoin will reach the masses when Apple creates a Bitcoin wallet.
What's the issue with lightning?
at least u ack. good sign
coinjoin tainted BTC will NOT be ACCEPTED in many places
What about Ashigaro, the Samari fork?
What about telling everybody that Monero ring signatures cause supply inflation and all of us recommending it were scammers?
That was a pretty big fuck up too.
- boltz
- CLN
- BTCPay Server
- lnp2pbot
- Alby
…Everything has been hacked in recent weeks…
Lnd on own node still working fine
We'll see…
As far as I'm concerned, it's not worth having coins exposed to risk right now…
The biggest and the most pathetic.
Litecoin MWEB
I'm still on the fence with AI. I wonder if when subsidies stop we will see as much usage.
similar to electric car usage.
not a scam but i'm scheptical of LLM's impact on daily life
*use Monero
... Many *KYC'ed places. Is that a problem?
You have a too volatile mentality, sometimes you write as you know everything and you have control over everything. Then as if you get everything wrong and it's the end of the world lol
Please correct me if I'm wrong:
- Boltz didn't get hacked, they shut down their service because of ongoing attacs and before these are successful.
- Never heard lnp2pbot got hacked. In their last message nothing like that was mentioned.
- AlbyHub instances could only be drained if you down update it for over one year. The bug was found and fixed for all instances that update regulary.
I'm also not a big fan of Lightning and its complexity but for today we dont have a better option of scaling in Bitcoin. With ZKPs and a verifier in bitcoin script something like ShieldedCSV could be a better scaling method.
Hate to say it but there is a growing body of evidence showing the bitcoin ecosystem is not as secure as we would like to think it is.
Nothing is wrong with Lightning.
LN is working perfectly fine for me.
It's the biggest target.
Back to the roots so to say…
Lightning is too complex? Did you take a look at fiat lately? 🤣🤣