where
Address (created from Faucet) : ccefefbdc1d81de0
Public Key: 72f9de5e0056d2c4b83d10a302e7ff799547ff721cd3a6737c8893fd39901621ce304d6c23789ae9a7b75d0cba2ae10bf453f3194bdea43883b4f361546fbcbd
Private Key: c4604e5d29201a44ad107191c08c9f2ce7ee3266a1a306760212e313c7476219
Following Error is received:
Status: SEALED
Execution Error: Execution failed:
error: cannot decode runtime public account key: input is not a valid ECDSA_secp256k1 key
→ 3308ae867cfa7cfb451049ac14ebcb87901049e17f808ad14df08c7d6fcf5cda:7:3
|
7 | acct.addPublicKey(key.decodeHex())
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
for key in publicKeys {
acct.addPublicKey(key.decodeHex())
}
for contract in contracts.keys {
acct.contracts.add(name: contract, code: contracts[contract]!.decodeHex())
}
}
}
Events:
None
Any help / tips would be greatly appreciated, thx !
EDIT: I see, you mentioned about Faucet account already “Address (created from Faucet) : ccefefbdc1d81de0”
If you are trying to create accounts on Testnet, you might need to require account creation permission via the Faucet. It is simply a one-time request https://testnet-faucet.onflow.org/
“If you are trying to create accounts on Testnet, you might need to require account creation permission via the Faucet. It is simply a one-time request https://testnet-faucet.onflow.org/” —>
I I have already requested and obtained account creation permission.
Thank you very much and this had to be the root cause of the issue.
However, after re-generating keys with the ECDSA_secp256k1 option and re-ran the Create Account command,
I now get a different error:
Status: SEALED
Execution Error: invalid signature: signature could not be verified using public key with index 0 on account ccefefbdc1d81de0
---->. Does this mean I’d need a NEW Faucet Test account to go with the new pair of keys ?
Does this mean I’d need a NEW Faucet Test account to go with the new pair of keys ?
No, you should be able to use the same Testnet account.
You’ll need to make sure you’re signing with the same key pair that you used to create the faucet account (my-testnet-account). If you don’t have the private key anymore, you’ll need to create a new faucet account.
“You’ll need to make sure you’re signing with the same key pair that you used to create the faucet account (my-testnet-account). If you don’t have the private key anymore, you’ll need to create a new faucet account.” ------> precisely what I expected, thank you very much for confirmation
Hi @pete I have a question. Can I only create a test account through the official faucet?Is it possible to create available test accounts through programs such as JS or Go?
"“You’ll need to make sure you’re signing with the same key pair that you used to create the faucet account (my-testnet-account). If you don’t have the private key anymore, you’ll need to create a new faucet account.” —>. Since we are on the topic of test account creation thru Faucet, I have not received confirmation from Faucet after one week since request.
Currently after inputting a valid Public Key and click “Create Account”, the page shows a progress bar and stops responding. Is this behavior normal?
I tried on both Safari and Chorme and same behavior persisted.
I was able to create a Testnet Account previously and the expected behavior is to redirect to a page showing “Request Fullied” with the TestNet Account Address showing.
