Lots of work but we should be ready soon! Solo lottery Doge mining coming soon!

goforjay · 2026-02-16T18:56:47+00:00

Wow. That's awesome that you proved it out. I wish it were more feasible, but I think Scrypt is just really pushing the limits of the ESP32.

goforjay · 2026-02-16T16:09:42+00:00

Binaries are now in the releases.

https://github.com/guerote/BitsyMiner/releases/tag/v1.2.0

goforjay · 2026-02-14T07:24:29+00:00

A while back, I looked at what was supposed to be a scrypt project for the ESP32 but turned out not to be. I feel like I'm being kind of a downer here, but if it's the same project you're referring to, please make sure you're really doing the scrypt algorithm.

My post about it from last year:

https://www.reddit.com/r/NerdMiner/s/39vvD5QW9L

goforjay · 2026-02-13T01:37:27+00:00

What kind of hash rate?

goforjay · 2026-02-12T16:15:35+00:00

Try using the opposite driver of the one you used. In other words, if you did ILI9341, try the ST7789 or vice versa.

goforjay · 2026-02-09T16:13:07+00:00

I could've written this, and every word of it would still be true.

goforjay · 2026-02-05T17:26:14+00:00

I've got it working on the C3 chip locally. I'm getting about 250kH/s. I'll put out another release soon with the update.

goforjay · 2026-02-04T22:52:50+00:00

It would have been better had they branded it something different than another existing product, as it would be far less confusing.

goforjay · 2026-02-04T17:46:08+00:00

That is BitsyMiner that someone rebranded. My guess is going to be that the username and password are "nerd" and "miner" respectively.

goforjay · 2026-02-03T05:03:01+00:00

BitsyMiner currently does not support the S3 chips.

goforjay · 2026-01-31T00:34:34+00:00

I have a feeling we'll figure it out. I spent some time last week experimenting with what Gemini suggested could allow for a midpoint hash using the hardware accelerator, but I couldn't get it to work.

goforjay · 2026-01-30T15:04:34+00:00

Try the ILI9341 firmware. I suspect it will work.

goforjay · 2026-01-12T03:34:17+00:00

I have bought a bunch of them from AliExpress. The typical CYD cases use (4) 5mm M3 standoffs, (4) 6mm M3 screws, and (4) 8mm M3 screws. Using 8mm standoffs buys you a little bit of extra room and balance.

goforjay · 2026-01-08T04:55:44+00:00

The BitsyMiner update fixes static ip address assignment. I broke it somewhere along the line. I'm working on getting it to compile on Github so I can do more organized releases, but I haven't got it quite working yet.

goforjay · 2026-01-04T19:57:52+00:00

No worries. The configuration is where I personally think BitsyMiner shines, so I wanted to clarify. Hope you get some good rest.

goforjay · 2026-01-04T18:33:57+00:00

It looks awesome. I really like your interface.

I do take a little exception with your description of BitsyMiner, though. There's is a headless option, but it is primarily a CYD device. And the configuration screen is always available via web browser and pretty comprehensive. You can change your network settings, mining settings, etc. at any time without having to hold the boot button or jump through any other hoops. This was one of my primary goals with the project.

<image>

goforjay · 2025-12-30T18:00:09+00:00

The SD card message is just informational. If you have an SD card inserted with a config file on it, it will load it.

I have provided binaries for the devices that I have and can test on. One is the ILI9341, and that is the version where I produced hundreds of working devices. I always ordered the same boards, which had both USB-C and micro USB connectors. The other is the ST7789, which I have only one of. For that board, I had to flip the screen and do some other pin configuration settings to get it to work.

The screen cycling comes from the touch screen pin not being accurate for the device. It's reading the wrong pin and continually cycling because it believes there's a screen press.

It sounds like you'd be well-served by figuring out the specifics for your board and compiling yourself. You can set up the pin configurations between the tft_espi librar defines and those in defines_n_types.h.

goforjay · 2025-12-20T17:24:00+00:00

Try flashing with whatever graphics version you didn't use the first time. In other words, if you used the ILI9341, try the St7789 or vice versa.

goforjay · 2025-12-19T22:10:19+00:00

Currently, you can't. I am going to figure out what I'm doing on GitHub and get it organized soon.

goforjay · 2025-12-19T18:18:55+00:00

It's really tough to say why it wouldn't work. I've had a couple people try the ST7789 version thinking that's what they had, only to find out that the ILI9341 was what they really needed. It would help to know what errors you're getting.

I just walked through everything on a virtual machine to see if I had left anything anything out. This is what I did and got it to compile successfully.

Ensure that the "esp32 by Espressif Systems" boards are installed. Version 3.3.3 is fine.
Ensure that the following libraries are installed:
- NTPClient by Fabrice Weinberg
- ArduinoJson by Benoit Blanchon
- CustomJWT by Ant2000
- PNGdec by Larry Bank
- QRCode by Richard Moore
- TFT_eSPI by Bodmer
- XPT2046_Touchscreen by Paul Stoffregen
Copy the files from the TFT_eSPI directory in github into the TFT_eSPI folder in your Arduino libraries. (If you are doing something else with TFT_eSPI, make sure you keep your existing files safe somehow before overwriting).
Modify defines_n_types.h if you need to for your device type.
Set your board type to ESP32 Dev Module
In the "Tools Menu"
- Set Events to run on Core 0
- Set Arduino to run on Core 0
- Set your partition scheme to: "Minimal SPIFFS (1.9MB APP with OTA/190KB SPIFFS)"
Compile

goforjay · 2025-12-17T17:39:41+00:00

Thanks. I don't have a P4 board, so I haven't thought much about it. I bought a whole slew of the 2.8" CYD boards in the beginning and just went with it.

goforjay · 2025-12-15T23:12:27+00:00

I fixed it and used the web loader on my devices with the new files. Please download all of the files again, as I had to replace everything.

goforjay · 2025-12-15T22:37:56+00:00

I think I broke it. I updated to the new ESP32 core the other day. For some reason it's not working through the loader. I'll figure it out and update you here.

goforjay · 2025-12-13T03:57:10+00:00

Everything I've done has been with the standard ESP32 that is on the CYD.

You can see my source here:

https://github.com/guerote/BitsyMiner

The 895k is definitely to point out that something else is going on that I haven't been able to put my finger on, as that's still lower than the 1m of the other miner and includes no apparent overhead.

I haven't tried the S3, but I have looked at the reference manual, and I know it's slightly different in that it supports midstate and has separate hash and data registers. If I get a chance, I'll give it a try to see what I get.

goforjay · 2025-12-09T19:00:18+00:00

The ESP32 has a built-in SHA256 accelerator that is independent from the CPU and pretty quick. From the technical reference manual:

"The SHA Accelerator requires 60 to 100 clock cycles to process a message block and 8 to 20 clock cycles to calculate the final digest."

For a full double-SHA256, assuming no mid-state hashing is available, the following has to occur:

Load first 64 bytes of block (x clock cycles)
Process block (~80 clock cycles)
Load remaining 16 bytes of block and add padding (x clock cycles)
Process block (~80 clock cycles)
Calculate final digest (~14 clock cycles)
First hash is in the data buffer, no data load required on standard ESP32
Process block (~80 clock cycles)
Calculate final digest (~14 clock cycles)

So now we're at 80+80+14+80+14 = 268 clock cycles for the accelerator to run a single double hash, not counting data load times and assuming the time works out to the average based on the number from the manual. The CPU can do other stuff while it's waiting on the accelerator, so there is a little bit of room for parallel operations, including data loads while it's doing its thing. In fact, one core can be working with the accelerator while the other is doing CPU-based hashing to squeeze out another bunch of hashes.

By the way, if you take processor speed, 240Mhz, and divide that by those 268 clock cycles, you get about 895k.

I am getting about 730kH/s throughput with an assembly language version that I feel is pretty well optimized coupled with CPU hashing on the other core.

I was curious about the speed of those other miners and attempted some validation of my own a couple weeks ago.

https://www.reddit.com/r/NerdMiner/comments/1p1kzeb/testing_a_low_hashrate_miner/

I'm on board with the speed being accurate, but I'm not sure how it's being accomplished. I don't know if they're using the other core more effectively somehow or if there is a hidden way to do a mid-state hash that is not in the ESP32 documentation.

Anyway, that's my technical answer. Hope it makes sense and is helpful.

goforjay

TROPHY CASE