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
Problem
The Hedera Java SDK includes an example that demonstrates how to create an account with a threshold key (CreateAccountThresholdKeyExample.java). This is a crucial feature that allows users to create accounts where multiple signatures are required to authorize transactions, which is an essential security mechanism.
However, there is no equivalent example available in the Hedera JavaScript SDK. Developers using the JavaScript SDK would benefit from having a similar example to guide them in creating accounts with threshold keys in a JavaScript environment.
Solution
Below is a link to the existing Java implementation, which can serve as a basis for creating the JavaScript example:
CreateAccountThresholdKeyExample.java
Steps to Implement
Generate key pairs using the JavaScript SDK (PrivateKey.generateED25519()).
Create a threshold key by initializing a KeyList with a threshold and adding the public keys.
Create an account with the threshold key.
Perform a transaction requiring multi-signature from the threshold key.
Delete the account as part of cleanup, also requiring multi-signature.
Expected Outcome
The new example will provide developers with a clear guide for setting up multi-signature accounts using threshold keys in JavaScript. This is especially important for those building more complex, secure applications that require multi-signature transactions
By providing this JavaScript example, we align the JavaScript SDK with the Java SDK in terms of documentation and usability, making it easier for developers to build Hedera-based applications.
π 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.
ππ₯ 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
Problem
The Hedera Java SDK includes an example that demonstrates how to create an account with a threshold key (CreateAccountThresholdKeyExample.java). This is a crucial feature that allows users to create accounts where multiple signatures are required to authorize transactions, which is an essential security mechanism.
However, there is no equivalent example available in the Hedera JavaScript SDK. Developers using the JavaScript SDK would benefit from having a similar example to guide them in creating accounts with threshold keys in a JavaScript environment.
Solution
Below is a link to the existing Java implementation, which can serve as a basis for creating the JavaScript example: CreateAccountThresholdKeyExample.java
Steps to Implement
Expected Outcome
The new example will provide developers with a clear guide for setting up multi-signature accounts using threshold keys in JavaScript. This is especially important for those building more complex, secure applications that require multi-signature transactions
By providing this JavaScript example, we align the JavaScript SDK with the Java SDK in terms of documentation and usability, making it easier for developers to build Hedera-based applications.
π 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.
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π 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.