The problem GevuRisc solves

People will be able to use Gevolut for Risc0 proving/verification.

Challenges I ran into

1. According to documentation filesystem should be cleaned after each task, so I used same input file name for 2 different programs in the transaction. However, it failed without any details what went wrong. I played around with it and found easy workaround - https://github.com/koxu1996/gevulot-risc0-integration/commit/4ea759b7fe0392caca64ccb284bb20676bc3b246#diff-c360e038bc005da1dc6b976492ad4d2f274e8859c5f072518ebc1a90dbe0b3c5 2) JSON-RPC is missing error details, so if your transaction is stuck, then you must wait until someone from Gevulot will investigate internal logs. Right now I have issues with parsing arguments - tried to fix them with https://github.com/koxu1996/gevulot-risc0-integration/commit/6cb922085d68c5093af4e0b989637dc288f0b568 but still no luck.