Current solution

Currently users rely on forking to achieve this, as described in the docs.
That's why we thought it's sufficient to mark #171 as resolved.

Request

But it seems users want to be able to do this without forking, as requested on Slack.

Questions

1. Should we predeclare just the latest version and update it when needed? Or do we keep on accumulating these classes, as new Argent account versions appear? Because in the first case, it might constitute a breaking change if a predeclared class suddenly disappears (i.e. is replaced). It might not be a breaking change if we warn the users in the docs that they should not rely on a predeclared Argent account class to be always present at the same hash value.

2. What would be the startup time impact of this? Can we use the existing benchmarking scripts for this or do we need a new one?