[desktop-wallet][1200 USD] Revised Peer System

[ItsANameToo]

About This Project

The current peer system needs improving. A lot of the processing and logic is done in the vuex store which shouldn’t be the case. The majority of this logic should be moved to its own controller and handled there, leaving just the data manipulation to the vuex store.

In addition to this, the peer system needs to correctly handle the available APIs. This is already dealt with to an extent in a recent change to the wallet (unreleased). The system should cater to both core-wallet-api and then core-api if there are no peers with the wallet api enabled. It should also respect the ports that are used for both of those APIs.

Finally, Custom Peers are difficult to use. We need you to implement persistence (as a toggle) which means that a user does not get switched to another peer automatically due to failure. You also need to implement the ability to store a subset of peers manually based on a name (E.g. “My Relay 1”, “My Relay 2”, “Home Relay”, etc) against a particular network. It will be required to be able to manage (CRUD) this custom peer list through the same custom peer modal that is used to connect to one. This will add an additional feature which allows the user to switch between peers in their “custom peers” list in the event of a bad relay, and not automatically to a “public” peer.

The difficulty level of this bounty is estimated as advanced. The reward for completion of this project is set at $1200 (paid in ARK Ѧ).

Requirements for completion:

• Refactor the peer system so that all logic is in its own controller meaning only data handling is done within the vuex store
• Peer APIs and ports should be respected to make sure it works across different Bridgechains
• Improve the Custom Peers functionality to allow for a subset of peers that the user may prefer, which is to be stored on a per-network basis

Necessary Skills:

• Electron
• Vue.JS
• Tailwind
• Jest

Applying For This Project

To apply for this project, please read more about the process below before leaving a comment with the following:

1. A brief proposal relating to the project (e.g. Your experience, how you wish to approach the project, estimated time to completion etc.)
2. Your name and a contact email address (or another form of contact, eg. Slack username)

The Process

If your application for the project is successful we'll contact you using the details you provided, assign the project to you and mark it as in progress. You'll be required to check in regularly with the ARK team to discuss progress and development. We'll also use these updates to ensure that the PR is being completed to a satisfactory standard. If we determine that the project isn't being completed to a satisfactory standard and that this cannot be achieved with minor amends or within a satisfactory timeframe, we hold the right to dismiss the PR and reopen the project to other applicants.

To deliver the project your PR must be submitted to the respective repo. ARK repo maintainers will then leave comments and request amends if necessary. All amends requested by maintainers must be resolved before completion, and all projects must comply with our code standards and contribution guidelines (found at: https://docs.ark.io/guidebook/contribution-guidelines/). After you've submitted your project, we'll review against the brief to ensure it meets the criteria and deliverables.

Once your project is approved as complete a member of the ARK team will follow up to discuss payment. You'll need to submit an invoice and payment will be issued in (Ѧ) ARK (equivalent to the USD reward value assigned to the project), sent to an address of your choosing. We may need to request additional information regarding your identity in order to comply with our own internal Know Your Customer (KYC) guidelines.

If you're unsuccessful in applying for this particular project, please consider applying for others. Thanks for your interest and good luck with your application!

[akyo8]

hi.

This is Eugene I am experienced in Electron and Vue. And it would take around 10 days from today if task is assigned to me.

my email : ha.eugene@aol.com

Thanks,

[akyo8]

hello,

when can I expect to hearing any update?

thanks,

[alexbarnsley]

Hi @evgeny127, apologies I did email you yesterday but didn't get around to seeing your response. I have now assigned this task to you 👍

[akyo8]

great, thanks

[akyo8]

hi alex

are you available on slack? it would be great if we can talk on slack or skype.

thanks,

[akyo8]

hi team cc : @alexbarnsley , @faustbrian I was spent most of times on bug fixing last week. And hopefully I can commit code this week

[alexbarnsley]

Hi @iMiracleDev, how are things progressing?

[ItsANameToo]

How's your implementation progressing @iMiracleDev ? Otherwise we'll be opening up this issue again for someone else to take on.

[dated]

:eyes:

[ItsANameToo]

You finished your previous one? 🤔 including tests? :trollface: