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-3Q23-03.1: Bitcoin on Stacks | Improvements #916
Comments
👋 @will-at-stacks |
Linking the StackScreener project proposal here for visibility to community members: If anyone has any thoughts, questions or suggestions on the future of StackScreener, here would be an appropriate place to make those. I'd also like to note that I feel that while StackScreener applied for the Bitcoin on Stacks grant, it really does apply to both this category and the Stacks/Clarity grant. We plan on screening and providing data for STX tokens as well as BRC20s, Ordinals, and anything in the future to come from both spaces. We believe that Stacks is the layer 2 that will allow innovations on Bitcoin to scale. Great example of this is the creator of BRC20s, domodata, working with Alex Labs for an onchain indexer for BRC20s using Stacks smart contract functionality. Anyways, have a glance at the proposal and look forward to continuing to build out a much needed tool for the community. Thanks! |
+1 to @ddimaria95 proposal. A. Thanks for providing the actual proposal. Community visibility is helpful and unfortunately missing with this new process. |
@dantrevino Curious, what is missing regarding community visibility? |
Submitting for this track & officially revealing what we've been cooking up internally :) https://docs.google.com/document/d/1cuJbv_iCiXn80ByIcW7osLt346DDXqEKtbVhsxEN1sA/edit?usp=sharing |
@igorsyl ... After @will-at-stacks refuted my complaint yesterday, I looked again and I do see a link to existing work post-approval. I will say, though that none of the applications seem to be public before approval. Its like the whole grant thing is now behind a wall. Submissions are via a form. The community never sees those afaict. Then a grant committee of 4 (apparently) ... approves or disapproves without any community feedback. Then, and only then, are the approved grantees asked to provide their proposal. Followed by a single "here's where to find gitbook" link buried in the comments (usually). I'm not even sure my characterization of the process is correct because, honestly, I cant find anything about how its supposed to happen or, ideally, why its happening that way. Maybe I missed a memo. Maybe I missed a big community share... doesnt feel like it though. I think this process can be better communicated and more open. But I'd be happy to learn that I'm just ignorant about whats going on. |
Blog post for March. Plus: "none of the applications seem to be public before approval" "Its like the whole grant thing is now behind a wall. Submissions are via a form. The community never sees those afaict." Then a grant committee of 4 (apparently) ... approves or disapproves without any community feedback. Then, and only then, are the approved grantees asked to provide their proposal. Followed by a single "here's where to find gitbook" link buried in the comments (usually). "I think this process can be better communicated and more open. But I'd be happy to learn that I'm just ignorant about whats going on." Best, |
Excellent @will-at-stacks. Thank you. The only thing I'll agree to disagree with you on is "Don't bring me problems, bring me solutions". I'm not getting paid to be the Grant Administrator. So i'll 100% continue to offer my feedback, but solutions, like the community grant process outlined yesterday, will have to come from y'all. |
Sounds good! I guess what I meant by that - if if Grants hopes to decentralize - people will need to take ownership and not think of it as salaried vs. no salaried. The goal is to have shades of grey. Not just a binary. |
Appreciate all the convo above and feedback from Dan.
|
UPDATE ON CRITICAL BOUNTY SELECTION:Please note that the applications are in review. We are first, prioritizing the selection of the sBTC Testing Team. Once that selection has been made we will begin final reviews for all other Critical Bounties. Our goal is to announce the selected critical bounty recipients the week of July 10th. Best, ( cc: @jennymith @igorsyl ) |
Hi All - We are excited to announce FOUR recipients of the Bitcoin on Stacks critical bounty! Congrats to : If you could like to review all of the applications go here. Thanks to all that applied! Best, |
Thank you @will-at-stacks! |
Thanks @will-at-stacks started sprint planning using trello |
Discussed in #912
Originally posted by will-at-stacks May 8, 2023
PLEASE NOTE: This RFP is still in development and will be formally published on 5.12.23. Applications will be open until 6.20.23. Applicants will apply by following the link in this document once it is formally published as an Issue.
Introduction:
We are excited to announce our latest batch of Critical Bounties (RFP-style grants)! With a total funding up for grabs of 12 BTC and 250k STX, we are seeking talented individuals to help us drive the sBTC, Bitcoin on Stacks, Stacks, and Clarity forward. Applications will be open from 5.12.23 to 6.20.23. Don't miss this chance to be a part of the future of Bitcoin L2 and Stacks!
Critical Bounty Mission Statement:
Join us in our mission to bridge Bitcoin and Stacks through sBTC! We're seeking open-source proposals that drive high-impact contributions to advance the activation of L1 Bitcoin-based assets on the L2 Stacks layer. Whether it's improving sBTC at the infrastructure or application level or enhancing developer experience, we're excited to hear your ideas. Each application submitted to this open-ended Bitcoin on Stacks Improvements RFP will be evaluated on the merits of its mission and the needs of the ecosystem at the time of review.
Project Idea (feel free to suggest ideas not on this list):
Required Knowledge / Skills:
Critical Bounty Fee:
APPLICATIONS ARE NOW CLOSED
CHECK BACK FOR MORE CRITICAL BOUNTIES IN LATE-AUGUST
The text was updated successfully, but these errors were encountered: