State validation for V2 Upgrade

[Whytecrowe]

No description provided.

[Copilot]

Pull Request Overview

This PR adds state validation functionality to ensure contract storage data remains consistent before and after V2 upgrades. The implementation creates utility functions to read and compare contract storage layouts, then integrates these into the existing upgrade test suite.

• Added storage validation utilities for reading and comparing contract storage data
• Integrated state validation test into the zDAOToken V2 upgrade test suite
• Cleaned up configuration by removing unused imports and commenting out deprecated test networks

Reviewed Changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 9 comments.

File	Description
test/zDaoTokenV2.ts	Adds pre/post upgrade state validation test using new storage utilities
scripts/utils/storage-check.ts	Implements storage layout reading and comparison utilities for upgrade validation
package.json	Adds protocol-utils dependency and removes postinstall script
hardhat.config.ts	Comments out deprecated network configs and removes unused task imports

Comments suppressed due to low confidence (1)

scripts/utils/storage-check.ts:1

• [nitpick] Variable declaration should follow consistent spacing conventions. Add space before the colon: preUpgradeState: ContractStorageData.

import { getStorageLayout, getUnlinkedBytecode, getVersion, StorageLayout } from '@openzeppelin/upgrades-core';

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

[nitpick] Type declaration should follow consistent spacing conventions. Remove spaces around colons: [label: string]: ContractStorageElement.

Suggested change

	[label : string] : ContractStorageElement;
	[label: string]: ContractStorageElement;

[Copilot]

[nitpick] Type declarations should follow consistent spacing conventions. Remove spaces around colons: key: string, valueBefore: ContractStorageElement, valueAfter: ContractStorageElement.

Suggested change

	[label : string] : ContractStorageElement;
	}>;
	export type ContractStorageDiff = Array<{
	key : string;
	valueBefore : ContractStorageElement;
	valueAfter : ContractStorageElement;
	[label: string]: ContractStorageElement;
	}>;
	export type ContractStorageDiff = Array<{
	key: string;
	valueBefore: ContractStorageElement;
	valueAfter: ContractStorageElement;

[Copilot]

[nitpick] Parameter and return type declarations should follow consistent spacing conventions. Remove spaces around colons: contractFactory: ContractFactory and : Promise<StorageLayout>.

[Copilot]

[nitpick] Parameter and return type declarations should follow consistent spacing conventions. Remove spaces around colons: contractFactory: ContractFactory, contractObj: Contract, and : Promise<ContractStorageData>.

[Copilot]

[nitpick] Parameter type declaration should follow consistent spacing conventions. Remove space around colon: acc: Promise<ContractStorageData>.

Suggested change

	acc : Promise<ContractStorageData>,
	acc: Promise<ContractStorageData>,

[Copilot]

[nitpick] Return type declaration should follow consistent spacing conventions. Remove space around colon: : Promise<ContractStorageData>.

Suggested change

	) : Promise<ContractStorageData> => {
	): Promise<ContractStorageData> => {

[Copilot]

[nitpick] Type annotation should follow consistent spacing conventions. Remove space around colon: e: unknown.

Suggested change

	} catch (e : unknown) {
	} catch (e: unknown) {

[Copilot]

[nitpick] Parameter type declarations should follow consistent spacing conventions. Remove spaces around colons: dataBefore: ContractStorageData, dataAfter: ContractStorageData.

[Copilot]

[nitpick] Parameter type declaration should follow consistent spacing conventions. Remove space around colon: acc: ContractStorageDiff | undefined.

Suggested change

	(acc : ContractStorageDiff | undefined, stateVar, idx) => {
	(acc: ContractStorageDiff | undefined, stateVar, idx) => {