Sanity check the deployed contracts are with expected configs/args/params

[boolafish]

Issue Type

[ ] bug report
[x] feature request

Current Behavior

No check after contract deployment

Expected Behavior

Have the check to validate what we deploy is what we expect

Motivation for Change

There was discussion in the effort of moving PaymentExitGame constructor to an init function. Should that function being guarded by maintainer. There is the risk somebody aside from our deployment script could pass in the params before we do that and lead to a wrong contract deployment.

With this, we would immediately know this set of deployed contracts cannot be used.

Sth outside of contract could be like checking authority address nonce.

This might be sth good to have no matter our deployment script would have the concern or not.