CB-23Q2-03.2 : sBTC Bridge: Integration with Trezor & Ledger

[will-corcoran]

Introduction:

sBTC is a SIP-010 fungible token on the Stacks blockchain that can be used in DeFi protocols, NFT marketplaces, DAOs, governance, and several other use-cases. The sBTC Bridge is a trustless two-way mechanism that allows users to wrap and unwrap BTC as sBTC. The sBTC Bridge is also a key component to sBTC operations. The development of an initial prototype for the sBTC Bridge has been led by @radicleart , you can review the sBTC Bridge repo here.

Critical Bounty Mission Statement:

The purpose of this Critical Bounty is to extend the list of wallets supporting sBTC to include Trezor and Ledger, two of the leading hardware wallets within the Bitcoin community. As a result of this Critical Bounty the sBTC Bridge will connect to the Trezor Bridge or Ledger Live applications the user is running to request the user sign the sBTC Wrap/Unwrap transaction for broadcasting. For better UX sBTC Bridge should allow for signing with multiple wallet providers.

Functionality / Deliverables (shall include, but not be limited to):

• UI / API Development for all required user flows
• Documentation including 'How To' videos and tutorials
• Usable with P2PKH/P2WPKH wallets.
• Support for latest versions of Trezor Bridge / Ledger Live and a single leading product.
• Product 'roadshow', feedback, and improvements: All recipients will be responsible for demonstrating functionality, championing early adoption, gathering feedback, and making one to two rounds of high-impact, feedback-based improvements.

Required Knowledge / Skills:

• Knowledge of Trezor / Ledger hardware wallets.
• Knowledge of Clarity / Clarinet
• Stacks js or Micro Stacks
• Bitcoinjs or preferably scure-btc-signer libraries
• Bitcoin transactions
• Best practices in software testing / continuous integration

References:

1. sBTC Bridge Design Doc
2. Hiro Wallet Issue #2824
3. Hiro Wallet Pull Request #3321
4. sBTC Whitepaper
5. Stacks Nakamoto Release Whitepaper
6. sBTC project dashboard
7. Clarinet Docs (reference for design system req’d for Typescript applications wrapped within a Rust application)
8. TM Repo (code & documentation standard)

Critical Bounty Fee:

• Maximum Fee: $30,000

Reviewers / Advisors:

Igor Sylvester, Core Engineering Lead, Trust Machines
Kyran Jamie, Hiro Wallet, Trust Machines
Mike Cohen, EcosystemDAO
Jesse Wiley, Integration and Security Lead, Stacks Foundation
Kenny Rogers, Developer Advocate, Stacks Foundation
Will Corcoran, Grants Lead, Stacks Foundation

Additional Comments:

Recipient will be expected to attend sBTC Core Engineering Working Group calls while the bounty is in development and provide weekly updates.

APPLY HERE

---

NOTES ABOUT CRITICAL BOUNTIES:

If you have thoughts, questions, or comments on the rough outline for this Critical Bounty above, please comments below.

Please note, all 2023 Q2 Critical Bounties that have funding approved for them will be moved to the Issues page (here) on Tuesday 03/21/2023.

Some procedural items to keep in mind with 2023 Q2 Critical Bounties:

1. Each Critical Bounty will have a pre-approved minimum and maximum budget listed within the issue.
2. All applications will be submitted via a BlockSurvey which will be linked within the Issue.
3. Applications will be open from 03/21/2023 to 04/03/2023.
4. Critical Bounty applications will be reviewed by relevant members of the sBTC Core Engineering Team and technical staff from the Stacks Foundation.
5. The selected recipient will be the low, qualified bidder (in the eyes of the reviewers).
6. Selected Critical Bounty recipients will be announced on 04/07/2023 and will be expected to start work immediately and attend sBTC Core Engineering meetings to provide weekly updates on their work.

[will-corcoran]

Congrats on being awarded this Critical Bounty @radicleart

This discussion thread should be used for all payment requests for your grant. Please follow these steps:

• Create a Gitbook for your project (watch this video for details on how)
• Once you complete a milestone, update your Gitbook and post a message below summarizing which milestone was completed and the updates you made to your Gitbook.
• When you post your request please tag @will-at-stacks
• Once I have a chance to review your deliverables I will begin the process of disbursing the associated payment.

Your CB fee of $20.4k will be paid out in (2) $10.2k payments at the following milestones:

1. At contract signing
2. Substantial Completion

[radicleart]

@will-at-stacks this seems to be a duplicate of #873

[will-corcoran]

I am not a GH expert by any means, so open to suggestions - but #848 is the original Discussion Item. This was then used to create an Issue (#873).

In the grants repo, we tend to think of Issues as being analogous to grant applications - and I've started a practice of creating a Discussion Item for each grant after its awarded - so I moved the conversation back to the Discussion Item. Hope thats clear.

[radicleart]

I am not a GH expert by any means, so open to suggestions - but #848 is the original Discussion Item. This was then used to create an Issue (#873).

Ah i see - thanks for clarifying ! 😄