Getting AccountId from Mnemonic

[cdigiacinto]

🆕🐥 First Timers Only

This issue is reserved for people who have never contributed to Hedera or any open source project in general.
We know that creating a pull request (PR) is a major barrier for new contributors.
The goal of this issue and all other issues labeled by 'good first issue' is to help you make your first contribution to Hedera.

👾 Description of the issue

We need to add a method to get the ecdsa publickey for an acount. The implementation of that functionality in the JS SDK can be found in the toStandardECDSAsecp256k1PrivateKey() method of Mnemonic.js.

Usecase

In case I already have an account on Hedera and I have the mnemonic how I can get the accountId that is associated? (the account was created by using the ECDSA_SECP256K1 public key)

let mnemonic = try Mnemonic.fromString(seed)
let privateKey = try mnemonic.toPrivateKey()

privateKey is a Ed25519

I don't see any methods in the SDK to get the ecdsa publickey so I can then query for this publicKey.
The aliasKey is not a reliable alternative because there is no record in the Hedera network of an account associated with a given aliasKey until an amount of Hbar is transferred to the account.

📋 Step by step guide to do a contribution

If you have never contributed to an open source project at GitHub, the following step-by-step guide will introduce you to the workflow. More information and concrete samples for shell commands for each step can be found in our CONTRIBUTING.md file.
A more detailed general documentation of the GitHub PR workflow can be found here.

• Claim this issue: Comment below that you are interested in working on the issue
• Wait for assignment: A community member with the given rights will add you as an assignee of the issue
• Fork the repository: You can do that in GitHub (by simply clicking the 'fork' button).
• Check out the forked repository
• Create a feature branch for the issue. We do not have a hard naming definition for branches but it is best practice to prefix the branch name with the issue id.
• Solve the issue in your branch.
• Commit your changes: Here, it is needed to add sign-off information to the commit to accept the "Developer Certificate of Origin" (https://developercertificate.org). More details can be found in our CONTRIBUTING.md
• Start a Pull Request (PR): We have a pattern for naming pull requests that a GitHub Action checks. We use that pattern to support the creation of automatic release notes.
• Check GitHub Actions: Several GitHub Actions will be triggered automatically for each PR. If a GitHub Action fails and you do not understand the cause of that error do not hesitate to add a comment to the PR and ask the Hedera developer community for support.
• Wait for reviews: Members of the Hedera developer community will review your PR. If a reviewer finds any missing pieces or a problem, he or she will start a discussion with you and describe the next steps for solving the problem.
• You did it 🎉: We will merge the fix in the develop branch. Thanks for being part of the Hedera community as an open-source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a chance to receive cool goodies like a T-Shirt. 🎽

🤔 Additional Information

If you have any questions, just ask us directly in this issue by adding a comment. You can join our community chat at Discord. A general manual about open-source contributions can be found here.

[cdigiacinto]

There will be no functionality like in the Hedera SDK js?
In Hedera SDK js there is the function toStandardECDSAsecp256k1PrivateKey()

https://github.com/hashgraph/hedera-sdk-js/blob/0feddb25bc2f17399bf0ab346e0464b79f10d0fe/packages/cryptography/src/Mnemonic.js

[RickyLB]

@cdigiacinto Thank you for pointing this out. This functionality will be added to the SDK soon.

[tknoch-symphony]

@RickyLB What is the timeline for this issue? All Hedera SDKs support this except switf