search

harmony-one / bounties

Bounty program is to help the community take part in the development of the Harmony blockchain. It covers from core feature to validator tooling, from dApp development to DeFi integration.
MIT License
59 stars 23 forks source link

[BTC Bridge] Rust client & react web-based dashboard for vaults #43

Open gupadhyaya opened 3 years ago

gupadhyaya commented 3 years ago

Description

Harmony is in the process of building a trustless bridge to Bitcoin using Interlay's XCLAIM protocol. There are several components of the bridge. Vaults are the heart of the OneBTC bridge. They are responsible for maintaining the physical 1:1 peg between BTC and OneBTC. Vaults receive BTC for safekeeping from users and ensure BTC remains locked while OneBTC exists.

This bounty needs to port Interlay's PolkaBTC vault rust client to Harmony, which is currently implemented for Polkadot. The bounty also needs to develop a minimal react web-based dashboard for vaults showing issue, redeem and replace requests, collateral status, BTC holdings and earned fees.

Resources

Requirements

Acceptance Criteria

Reference

Reward

$15,000 equivalent in ONE tokens

dB2510 commented 3 years ago

@gupadhyaya Is this bounty listed on gitcoin? Is it open?

gitcoinbot commented 3 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 177402.8996 ONE (15208.4 USD @ $0.09/ONE) attached to it.

papiofficial commented 3 years ago

@dB2510 https://gitcoin.co/issue/harmony-one/bounties/43/100025919

gitcoinbot commented 3 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work has been started.

These users each claimed they can complete the work by 2 weeks, 4 days from now. Please review their action plans below:

1) anweiss has started work.

Attempting to implement a Rust Vault client for the OneBTC bridge

Learn more on the Gitcoin Issue Details page.

anweiss commented 2 years ago

Given that many of the ONE<>BTC bridge and relay contracts are incomplete relative to the ONE<>BTC spec, is it sufficient to have placeholders in the ported code sections for which there is not yet an equivalent contract function that can be executed? Otherwise, it's very difficult to port the Vault client without a full understanding of the logic behind both the spec and the contracts as they are implemented.

papiofficial commented 2 years ago

@gupadhyaya ^

gupadhyaya commented 2 years ago

Given that many of the ONE<>BTC bridge and relay contracts are incomplete relative to the ONE<>BTC spec, is it sufficient to have placeholders in the ported code sections for which there is not yet an equivalent contract function that can be executed? Otherwise, it's very difficult to port the Vault client without a full understanding of the logic behind both the spec and the contracts as they are implemented.

we have extended the deadline till aug 9th and by then, we will try to get all the contract interfaces figured out at least. feel free to keep making progress and keep us posted. thanks.

srstomp commented 2 years ago

A bit late. But is it still open @gupadhyaya ? On the bounties is has the status open.

givp commented 2 years ago

@srstomp It is open but we were planning to close it by end of this week. Are you actively working on it? Do you have an ETA?

gitcoinbot commented 2 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

The funding of 177402.8996 ONE (20542.37 USD @ $0.12/ONE) attached to this issue has been cancelled by the bounty submitter