Quote from: Frasz on August 21, 2022, 05:38:19 PM

My question is: there a way to implement the cuckatoo cycle in the SHA256 coin to make it more asic resistant ?

Cuckatoo32 is designed to be ASIC friendly, and there are in fact ASICs for it.
But where SHA256 can be seen as proof-of-logic-circuit, C32 is proof of SRAM.
You need 512MB of SRAM to find solutions most efficiently.
It's true that the performance gap with GPUs is much smaller than for SHA256,
and current ASICs don't have enough SRAM to achieve full efficiency, but for
future ASICs there will be at least an order of magnitude gap.

Quote

If so there is a lot of C++ code I found on your GitHub but not a guide on how to maybe implement it ? Do you have one ? Can you maybe help me ? I am also from the Netherlands and don’t mind paying you for your time and effort.

The actual Cuckatoo32 verifiying logic should be easy to integrate into Bitcoin Core. The majority of effort needed will instead be for enlarging the header with a new field for the 42 cycle indices of size 42*32 bits = 168 bytes. I'd advise you to first get your blockchain working with this larger header, where you just ignore the contents of the new field. Let me know when you have that working.