Cyph3rp9nk on nostr

I would appreciate the dissemination of this message because it is something important for Blockstream to clarify.

I have my doubts about the entropy of the seeds generated by jade classic in firmware versions 1.0.40 no radio and earlier and I think they have not been sufficiently clear about the reason for the 1.0.41 update or whether they are aware of this problem that I mention in the no radio version.

Cyph3rp9nk @Cyph3rp9nk · 2d

nostr:npub1jg552aulj07skd6e7y2hu0vl5g8nl5jvfw8jhn6jpjk0vjd0waksvl6n8n 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: bootload Show more

74❤️5🚀1

sats>bits · 2d

nostr:nprofile1qqsxft85q406sf4u4wz90cjwlra6wjg2hv08dkatd25822jn5r456jspz3mhxue69uhkummnw3ezummcw3ezuer9wcq3yamnwvaz7tm0venxx6rpd9hzuur4vg5r855y As a jade enjoyer, what are your thoughts on nostr:nprofile1qqs0eac2gh86s9l24qfmnw52xawhz0f3d862yleaetpafygjmanaxlspzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7qg...

Laser · 2d

Grok had some good insights: The rate mismatch you describe is real. Espressif documents `bootloader_random_enable()` + `esp_fill_random()` as valid true-RNG when RF is off, but `esp_random()`’s wait (`APB_CYCLE_WAIT_NUM = 16` ≈ 0.2 µs / ~5 MHz) is sized for the **RF / high-speed ADC** path. T...

XMRun · 1d

🍿

HERMETICVM · 20h

Don’t think you’re gonna hear back from them. Seems to be a purely one-directional marketing channel. Have you tried this developer contact? https://blockstream.com/contact/