We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
const { Client, AccountInfoQuery } = require("@hashgraph/sdk"); require("dotenv").config(); async function main() { const operatorPrivateKey = process.env.OPERATOR_KEY; const operatorAccount = process.env.OPERATOR_ID; if (operatorPrivateKey == null || operatorAccount == null) { throw new Error("environment variables OPERATOR_KEY and OPERATOR_ID must be present"); } const client = new Client({ network: { "0.testnet.hedera.com:50211": "0.0.3" }, operator: { account: operatorAccount, privateKey: operatorPrivateKey } }); const info = await new AccountInfoQuery() .setAccountId(operatorAccount) .execute(client); console.log(`${operatorAccount} info = ${JSON.stringify(info, null, 4)}`); } main();
Error: (node:26920) UnhandledPromiseRejectionWarning: BadKeyError: Failed to parse correct key
The text was updated successfully, but these errors were encountered:
Thanks for the report. This is a valid bug. Fixed in v1.1.2.
https://github.com/hashgraph/hedera-sdk-js/blob/9cccd7978e2d5128f5906d4f895e41f6305c1d80/src/crypto/PublicKey.ts#L16
Sorry, something went wrong.
No branches or pull requests
Error: (node:26920) UnhandledPromiseRejectionWarning: BadKeyError: Failed to parse correct key
The text was updated successfully, but these errors were encountered: