It seems that proof-market toolchain would be more convenient to use if the user could easily substitute the proof-producer binaries.
Because many teams will inevitably do custom implementations and optimizations of our prover (including hardware-specific deployments), it may make sense to give them a separate repository, which they could fork and do their job there.
It became clear to me that we need to do [this task](Includes thishttps://github.com/NilFoundation/zkllvm/issues/179) first since proof producers copy part of the serialization algorithm.
It seems that proof-market toolchain would be more convenient to use if the user could easily substitute the proof-producer binaries. Because many teams will inevitably do custom implementations and optimizations of our prover (including hardware-specific deployments), it may make sense to give them a separate repository, which they could fork and do their job there.
Separate prover can be moved to https://github.com/NilFoundation/proof-producer
Check this issue after proof-producer is separated: https://github.com/NilFoundation/zkllvm/issues/178