Enforce use of the bootloader in verified program

[tdelabro]

Swiftness is built under the assumption it is verifying programs run on the bootloader.
If you don't (generate the proof of your own program) things start breaking left and right and you lose soundness.
Yet it is not mentioned anywhere and not enforced during proof verification.
I believe it should.

Most likely you can compute the program hash and check that it is indeed the bootloader, but I'm not sure.

[tdelabro]

Or, you could take the entrypoint into account while computing the program hash and aim for a more generalistic verifier.
I don't know what is the scope you want for swiftness

[Okm165]

I want swiftness to be a generic verifier for both Cairo0 and Cairo1
I mentioned the issue with verifying Cairo1 pub_mem further waiting for response
When I have procedures for Cairo1, verifier will support both pub_mem kinds so we will have no such issues

[Okm165]

#58 (comment)