[Feature]: Protocol needs to be backward and forward compatible

[spbrogan]

Feature Overview

changes to the crypto protocol must not break compatibility and should allow a caller of a different version to still work (with limited functions). The simplest method of achieving this to only allow changes added to the end.

Solution Overview

only add functions to end
put tooling in place to enforce this

Alternatives Considered

No response

Urgency

Medium

Are you going to implement the feature request?

Someone else needs to implement the feature

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

[github-actions]

This issue has been automatically marked as stale because it has not had activity in 45 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

[github-actions]

This issue has been automatically been closed because it did not have any activity in 45 days and no follow up within 7 days after being marked stale. Thank you for your contributions.

[Flickdm]

See #147 updated generate_cryptodriver.py to support this