Major rewrite of Solana crate which switches the programs over to

[Brando753]

Anchor. Adds support for a Verifier Router which can support multiple routers. Supports Emergency Stop calls.

Work In Progress: Still Requires Rewrite of Code Comments, Documentation, Some Examples, and User Scripts.

Add support for Program Verifier Routing and Emergency Stops.

• Groth16 Refactors
• Solana Verifier Router
• Solana Emeregency Stop
• Utility crates for use with these contracts
• A simple contract that verifies a RiscV proof using the main contracts.
• Deployment scripts and management scripts for Solana contracts that can run on testnet.
• A TransactionSigner class that supports Fireblocks for use with Deployment Scripts

[Brando753]

The main functionality is complete. The final step is documenting the code, adding comments, and cleaning up.

[Brando753]

Code cleanup complete; Only waiting on Documentation of Readmes and updating/adding comments.

The example program is not working as the verifier is returning a VerificationError on the run; I tested the example code against the original Solana verifier program and got the same error; @hans, am I passing in the correct arguments to the groth16 verifier?

[Brando753]

Documentation, code comments, and readmes have been added. The verifier still throws a verification error, but the router is complete. This is ready for code review.

[hmrtn]

Overall, I think this PR is in the right direction. The groth16, estop, and router logic seems correct. Further testing and review is still needed to merge.

Aside from small fixes, there is one issue that I think must be investigated, namely the emergency_stop_with_proof commented on in the thread.

I also notice some large gaps in testing coverage:

• While there are tests for the "bad verifier", there aren't comprehensive tests demonstrating successful verification of actual groth16 proofs
• tests for correct pairing checks and public input validation
• tests for invalid scalar values (exceeding BASE_FIELD_MODULUS_Q)
• tests for incorrect number of public inputs
• tests for the vk_ic length validation
• general rust unit tests for all modules

As a side note, from here out lets have smaller and more focused PR's and commits.

[hmrtn]

Consider adding breaks for all sections in TOML files

Suggested change

	[profile.release.build-override]
	[profile.release.build-override]

[Brando753]

Aside from small fixes, there is one issue that I think must be investigated, namely the emergency_stop_with_proof commented on in the thread.

I commented specifically on that section, but as is, it's not an issue, though we could document it better.

I also notice some large gaps in testing coverage:
While there are tests for the "bad verifier", there aren't comprehensive tests demonstrating successful verification of actual groth16 proofs

Yes, this feature was to create a verifier router, and so all the tests were done with a mock verifier that always has simple known inputs that it will validate on to allow us to test if the router is correctly routing, passing in the data correctly, and handling emergency proofs correctly. The verifier I was given for this feature was presumed to be unit-tested and working, though the example program does test the verifier as an integration test.
Regarding the routing, emergency stops, ownable macro, and entire integration test, I do not believe we have any missing coverage. The verifier itself falls out of the scope of this PR.

general rust unit tests for all modules

Unit testing was done in typescript as many aspects of anchor make the smaller module testing difficult. Much of the router code heavily relies upon the strongly typed elements of anchor, and therefore, unit testing was done in tests/router-verifier.ts, and the integration test was done in the example program and the ownable test program.