Has anyone had this problem too? Since updating to 3.27.3.0 I´m having a stupidly high amount of ghosting. I can´t even turn one page or close a document that almost all that image or file or text freezes as i close it or turn it.
Is there a way i can downgrade to another previous firmware?
I’m seriously considering an ERA Wallet for long-term BTC storage. My intended setup is to generate the BIP39 entropy completely outside the device using physical dice, verify the resulting seed independently, and then import the seed into the ERA. I’d use it purely as an air-gapped signer with Sparrow, communicating only via QR/PSBT. So ERA would not be involved in seed generation at all.
There are several things I really like about ERA for this use case: it’s completely QR-only with no USB or Bluetooth, supports up to 10 separate wallets/seeds on one device, has a Bitcoin-only firmware, and the form factor/transaction display make it very appealing as a dedicated signer. The fact that I can generate the seed myself externally is also a big plus for me. My main reservation at this point is actually the company itself and the fact that ERA is a relatively new wallet from a company based in Dubai/UAE. I’m trying to compensate for that lack of track record by understanding exactly what can be independently verified from the firmware and audits.
The one thing that makes me hesitate technically is Dark Skippy / nonce exfiltration. Even with a perfectly generated external seed, a malicious or compromised signing firmware could potentially leak information about the private key through ECDSA signatures by manipulating the nonce. Since ERA doesn’t appear to advertise an Anti-Klepto/anti-exfil protocol like BitBox02 or Jade, I’m trying to understand whether there is actually a meaningful way to rule this out. Has anyone gone through the ERA firmware closely enough to determine exactly how ECDSA/Schnorr nonces are generated? Is it RFC6979, a CSPRNG, or some combination involving external randomness/commit-reveal? Is there any nonce commitment or other mechanism that would make a Dark Skippy-style attack impossible?
I’ve looked at the Keylabs audit, but I don't see a specific analysis of nonce exfiltration. What I’m really trying to figure out is whether this can be independently verified from the published firmware/source, or whether that part of the signing implementation is still closed. If someone familiar with the ERA codebase, secp256k1, or the Keylabs audit can point me to the relevant code or explain the signing flow, that would be extremely useful.
Before becoming carnivore I took a neck carotid Artery (left and right) eco doppler, only to find that i had plaque, not too big but it was there. Being only 37 i got pretty scared.
2 years later being carnivore (750gr ribeye + tallow + lots of salt per day), i repeated the study.
Here you can see the results:
Patient Name: ---
Date of Birth: ---
ID Number: ---
Study Date: 06/17/2026
Accession Number: ---
Referring Physician: ---
Sex: Male
ULTRASOUND REPORT
Equipment Used: Mindray DC-70 X-Insight Ultrasound System
Reason for Examination: Carotid atherosclerosis.
Previous Study: Ultrasound dated 03/26/2024.
Report:
A carotid Doppler ultrasound examination was performed using B-mode imaging, color Doppler, and pulsed-wave Doppler.
RIGHT SIDE:
LEFT SIDE:
IMPRESSION:
Right carotid atherosclerosis.
Based on the systolic and diastolic flow velocity measurements and velocity ratios, the atherosclerotic plaque described above does not produce hemodynamically significant alterations and represents less than 50% stenosis.
--------
Of course the plaque haven´t dissapeared (yet) but it´s almost 50% smaller than the last study when I was eating a normal diet and had an LDL of 100. Two years later, after choking in tallow every day, eating shitloads of salt and meat, and having an LDL of 230, ApoB of 130, my plaque is reversing. To give context mi CPR-US is 0,1, my fasting glucose in 80 and my insulin sensitivity is perfect.
I don´t know what to think anymore.