-
Notifications
You must be signed in to change notification settings - Fork 5
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
Impossible to deploy a smart contract in LAOS Mainnet and Sigma using Hardhat (with different errors!) #280
Labels
bug
Something isn't working
Grooming Needed
Extra attention is needed
High Priority
Proposed to focus on this when other tasks are present
Comments
tonimateos
added
bug
Something isn't working
Grooming Needed
Extra attention is needed
labels
Jan 12, 2024
I could deploy using both Remix & Truffle, but not with Hardhat |
tonimateos
changed the title
Impossible to deploy a smart contract in Caladan & KLAOS
Impossible to deploy a smart contract in Caladan & KLAOS using Hardhat
Jan 15, 2024
Try with Moonbeam first |
tonimateos
added
bug
Something isn't working
Grooming Needed
Extra attention is needed
labels
Sep 10, 2024
tonimateos
changed the title
Impossible to deploy a smart contract in Caladan & KLAOS using Hardhat
Impossible to deploy a smart contract in LAOS Mainnet and Sigma using Hardhat (with different errors!)
Sep 10, 2024
tonimateos
added
the
High Priority
Proposed to focus on this when other tasks are present
label
Sep 10, 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
Grooming Needed
Extra attention is needed
High Priority
Proposed to focus on this when other tasks are present
ACCEPTANCE:
To reproduce, put some currency on your deploying account. Put the pvk in your
.env
asPRIVATE_KEY="04e.....04"
checkout repo: https://github.com/freeverseio/experiments/tree/master/erc20NonTransferrable
The errors in LAOS mainnet and Sigma are different!
Error in LAOS MAINNET
Error in LAOS SIGMA
ACCEPTANCE
The text was updated successfully, but these errors were encountered: