Make room for protocol versions.

[jubeira]

Description

Place existing task / deprecated / scripts under a v2 directory, create a v3 directory for new tasks and adapt scripts.

Type of change

• Bug fix
• New feature
• Breaking change
• Dependency changes
• Code refactor / cleanup
• Documentation or wording changes
• Other

Checklist:

• The diff is legible and has no extraneous changes
• Complex code has been commented, including external interfaces
• N/A Tests are included for all code paths
• The base branch is either master, or there's a description of how to merge

Issue Resolution

N/A

[elshan-eth]

LGTM!

[EndymionJkb]

Good first step, though I think we will need to refine it later. Maybe there needs to be a way to address v2 or v3. The "global" scripts (e.g., that generate addresses) would run over both v2 and v3, and take a long time. Do we want to reverify v2 every time we deploy a v3 thing? Stuff like that we can think about later. Could even split the readme into two pages: either v2/v3 or pre-/post-v3 launch (e.g., v2 and v3 would be mixed on the post-launch page, but only show v2 things deployed after the v3 launch. All legacy v2 stuff would be in the first page.

[jubeira]

Good first step, though I think we will need to refine it later.

Suggestions and PRs are welcome after launch :)