So, the biggest problem with using an FPGA, is the difficulty of finding someone who can "program" it, right? If that's the case, wouldn't it be simpler for me to try learning to configure/program it myself? Since I can make mistakes multiple times, as long as I'm careful not to damage the chip or anything like that.

I know I'm already being annoying with this subject, but it's something I've genuinely become interested in.

So the "ideal balance" is to combine the useful with the pleasant? Trading raw performance for ease of development and scalability?
Because for me, using FPGA, despite being very complex to "program," would bring absurd performance compared to writing GPU code. In this case, I’m considering that the FPGA configuration would be done in such a way as to make it scalable with other FPGA boards of the same model and similar ones.

So why are so many people still programming for GPUs instead of investing in FPGAs? Since FPGAs are so much better in terms of both price and performance, maybe it's because of the number of threads? 

And what is the average speed a program like this can reach? Considering the investment, it would need to achieve a speed greater than running it on a computer.

So, since an FPGA is so much cheaper and can be customizable (configurable) at the hardware level, why hasn’t anyone been using it?

The idea of an ASIC is good, but the problem is its price—it’s an unfeasible investment for many people. My idea of an OS is to eliminate this price issue and use the potential of a regular computer for this search. It would be more like a mutual benefit as an open project. However, it’s understandable that it might not be well-received by the community, as it would be a massive undertaking, even though the idea isn’t to build an entire system.

It’s more like creating a basic, ultra-powerful calculator solely for Bitcoin searching, with nothing sharing even the slightest percentage of processing power with anything unnecessary, making full use of every CPU cycle. Anyway, it’s a crazy idea, but I see it as a good one, even if insane. 

Linux still has many limitations. Any common operating system doesn’t allow you real and total access to all the processor’s resources with full efficiency—they at least run alongside your program, sharing processing power.

My idea is to create a system stripped of anything that could take even the slightest bit of processing power away from the program itself, leveraging every CPU cycle to the fullest.

---

And yes, Linux, for security reasons, does not give you full access to your computational power. And even if someone finds a way to make it grant that access, it’s still an operating system that runs alongside your program, consuming processing power that could otherwise be used by your program.

What if we created a mini operating system, basic but designed solely for finding private keys?

It might be a good idea, though a bit insane, since any operating system runs beneath any program—partly for security and hardware integrity reasons. It limits program performance to a safe level.

The idea of creating a mini OS sounds interesting to me, as this way we would have full access to the hardware and wouldn’t face any security restrictions or anything else that could hinder the program’s execution—aside from obvious hardware limitations.