Skip to content

Make the legacy Keep deployment key optional - #192

Open
mswilkison wants to merge 1 commit into
mainfrom
codex/84-optional-keep-deployer
Open

mswilkison wants to merge 1 commit into
mainfrom
codex/84-optional-keep-deployer

Conversation

@mswilkison

@mswilkison mswilkison commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Setting only CONTRACT_OWNER_ACCOUNT_PRIVATE_KEY makes Hardhat reject the Sepolia account list because its second entry is undefined. Hardhat validates every configured network, so this also prevents commands targeting mainnet from starting. The original Ropsten failure in #84 survives in the current Sepolia configuration.

Include the legacy Keep key only when it is nonempty. When both keys are set, the deployment account remains first and the Keep account remains second. When the deployment key is absent, retain RPC-managed accounts; malformed supplied keys still fail validation.

Validation: seven regression checks load the actual project configuration through Hardhat's validator with synthetic keys and no provider initialization. The three missing/empty-key cases fail on the base revision; all seven pass with this change. Modified-file JavaScript lint, Prettier, and git diff --check pass.

GitHub Actions passed on 28c367f: contract build, all 387 tests, deployment dry run, and Slither, plus formatting checks.

Closes #84.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

KEEP_CONTRACT_OWNER_ACCOUNT_PRIVATE_KEY shouldn't be required by default for deployments

1 participant