Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CB-23Q2-00.2 : Ordinal and sOrd Research (Research and Critical Bounty Development) #864

Closed
will-corcoran opened this issue Mar 21, 2023 Discussed in #850 · 1 comment

Comments

@will-corcoran
Copy link
Collaborator

Discussed in #850

Originally posted by will-at-stacks March 17, 2023

Introduction:

Similar to how sBTC trustlessly converts BTC into a SIP-010 fungible token on the Stacks blockchain that can then interact with smart contracts, sOrdinals (or sOrds) has the potential to trustlessly convert Ordinals native to Bitcoin into SIP-009 non-fungible tokens on the Stacks blockchain.

Critical Bounty Mission Statement:

The purpose of this Critical Bounty is to research the most current developments in Ordinal Theory and highlight the following:

  • What are the blockers to implementing sOrds as outlined in the sBTC Mini Whitepaper
  • And more generally speaking, what infrastructural improvements need to be made to help harden Ordinals and provide them with more functionality.

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

  • GitHub Repo or GitBook documenting research findings
  • 3-4 scoped Critical Bounties that can address blockers identified by your research. Critical Bounties RFPs consist of:
    • Introduction statement
    • Mission Statement
    • Functionality / Deliverables
    • Required Knowledge / Skills
    • References
    • Min and Max Number of Developer Hours Req'd
    • Suggested Reviewers / Advisors

Required Knowledge / Skills:

  • Experience working with Ordinals and PSBTs
  • Experience working with Stacks transactions encouraged, but not req'd
  • Strong documentation skills

References:

  1. sBTC Whitepaper
  2. sBTC Mini Whitepaper
  3. Ord
  4. Ordinal Collection Standard

Critical Bounty Fee:

  • Maximum Fee: $4,000

Reviewers / Advisors:

Igor Sylvester, Core Engineering Lead, Trust Machines
Trevor Owens, Bitcoin Frontier Fund
Andre Serrano, sBTC Resident and sBTC Go To Market Working Group Lead
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.
@stacks-foundation
Copy link

👋 @will-at-stacks


Thanks for your application! We will do a pre-review and let you know if we have any immediate questions. In the mean time please refer to our review schedule here for a detailed timeline and response dates.


Best,
Will

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants