Some SDK users have been having issues with the Key Provider. This is because formerly during Testnet3, verifying keys were fetched from a remote. They are now provided via SnarkVM, this PR updates the KeyProvider to use the keys directly from SnarkVM.
Motivation
Some SDK users have been having issues with the Key Provider. This is because formerly during Testnet3, verifying keys were fetched from a remote. They are now provided via SnarkVM, this PR updates the KeyProvider to use the keys directly from SnarkVM.