Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Private keys as Zero Hashes cause "Private Key is invalid" #652

Closed
quiet-node opened this issue Jan 30, 2024 · 0 comments · Fixed by #662
Closed

Private keys as Zero Hashes cause "Private Key is invalid" #652

quiet-node opened this issue Jan 30, 2024 · 0 comments · Fixed by #662
Assignees
Labels
bug Something isn't working

Comments

@quiet-node
Copy link
Member

Description

Currently, if a user doesn't provide enough 6 Private Keys in the .env, the program will fill out the constant PRIVATE_KEYS with zero hashes which will cause Private Key is invalid

Steps to reproduce

  1. In .env, provide less than 6 private keys for the PRIVATE_KEYS attribute
  2. Run npx hardhat test

Additional context

No response

Hedera network

mainnet, testnet, previewnet, other

Version

0.7

Operating system

macOS

@quiet-node quiet-node added the bug Something isn't working label Jan 30, 2024
@quiet-node quiet-node self-assigned this Jan 30, 2024
@quiet-node quiet-node moved this to Sprint BackLog in Smart Contract Sprint Board Jan 30, 2024
@quiet-node quiet-node moved this from Sprint BackLog to In Progress in Smart Contract Sprint Board Feb 2, 2024
@quiet-node quiet-node linked a pull request Feb 2, 2024 that will close this issue
2 tasks
@github-project-automation github-project-automation bot moved this from In Progress to Done in Smart Contract Sprint Board Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant