-
Notifications
You must be signed in to change notification settings - Fork 36
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-23Q3-05.1 FastMint, NFT-specific Subnet #927
Comments
👋 @will-at-stacks |
I am thrilled to help support the recent launch of Subnets, an L2 scaling solution for the Stacks mainchain, with this exciting Critical Bounty. Subnets offer high throughput and low latency for specific workloads, with each subnet having its own miners and consensus rules separate from the Stacks main chain. The interaction between users and subnets occurs through smart contracts on the Stacks main chain, settling eventually on the Stacks blockchain and, in turn, settling on Bitcoin. The future holds the potential for various subnets with different consensus models and purposes. Let's kick that future off with a Subnet purpose built for NFTs! Mission There are two main things that have always stood out for me when talking about Stacks and other blockchains:
The mission here is very clear. The work will not be enough by just spinnin-up a working subnet so that we can improve the NFT experience on Stacks, that’s just the beginning; the real challenge/value will be working with existing teams to guide them on how to run their own subnet or use an existing one. I know the scope mentions marketplaces and wallets, I also believe getting buy-in from the most popular NFT collections will be key. My goal is to have a handful of commitments for a federated FastMint Subnet prior to production launching. Proposed Approach Seen in the pictures here of the Stacks node syncing below. I’m well into the task at hand and also had the chance to talk with a few experts for help along the way Going through this research phase, I propose the following approach presented as modules and later broken down into specific deliverables: Finish Demo & Docs Designs
I’m still getting familiar with deploying a subnet through my own Stacks node, but still that doesn’t stop me from doing the appropriate planning to accomplish the above. Spin Up FastMint Subnet Instance Build Out FastMint Demo Communicate With The Ecosystem Infrastructure and Teams
From this the end goal is clear, we will know who will likely participate in the final launch, but even better, I’ll field what is needed in the docs for future entities and better adoption. Update On-Boarding Docs Deploy Federated FastMint Subnet Deliverables and Roadmap August Complete FastMint Alpha Instance [25-50 hrs] Since this is the very first time I’ll be deploying a subnet, I expect some issues along the way; accordingly, every future mention of a FastMint version deployment has a significantly tighter hourly range. Write FastMint Clarity Contracts [25-35 hrs]
Finalize FastMint Test Subnet Writeup/Questionnaire [15-30 hrs]
September This will be the single largest continuous deliverable Community Outreach [25-50 hrs]
The point of each of these meetings is to answer two questions:
After many conversations, I’ll be left with actionable feedback as well as an idea of how many and which entities will be available for our final federated FastMint deployment. October Hopefully I’ve anticipated needs well enough that the feedback here is on the lower end. Federation-Wide FastMint Test [10-20 hrs] Production Release [3-5 hrs] November Simple FastMint Landing Page [25-40 hrs] Methodology and Budget Methodology Subnet Setup Website React (demo) Clarity Contracts Community Communication This will be the main way I’ll get feedback and build up the group that’ll be part of the final federation. Documentation Budget While the critical bounty is stated up to $50k, I’d rather give a conservative, but realistic scope; hopefully there’s enough budget leftover for a second applicant or for another bounty. Looking forward to giving the Stacks ecosystem my very best. |
Already running my own Testnet Subnet Node, and successfully executing transactions. |
Hi All. Thanks to everyone that applied for the FastMint Critical Bounty. I am pleased to announce this bounty has been awarded to @Patotking12 ! @Patotking12 thank you for all of your hard work on your application and perseverance with debugging subnets and standing one up. We look forward to seeing what you do with the FastMint project ;) cc: @obycode |
Hey all! For anyone looking to follow this critical bounty, here is the github repo I am working on https://github.com/Patotking12/stacks-subnet |
Introduction:
We are thrilled to help support the recent launch of Subnets, an L2 scaling solution for the Stacks mainchain, with this exciting Critical Bounty. Subnets offer high throughput and low latency for specific workloads, with each subnet having its own miners and consensus rules separate from the Stacks main chain. The interaction between users and subnets occurs through smart contracts on the Stacks main chain, settling eventually on the Stacks blockchain and, in turn, settling on Bitcoin. The future holds the potential for various subnets with different consensus models and purposes. Lets kick that future off with a Subnet purpose built for NFTs!
Critical Bounty Mission Statement:
Build a "FastMint" demo application on Stacks mainnet using Subnets to showcase fast NFT minting and enable ecosystem feedback. The goal of the "FastMint" Subnet is to ensure smooth minting experiences and provide clarity throughout the minting process, particularly during marketplaces' peak times, minimizing congestion and gas wars.
Functionality / Deliverables (shall include, but not be limited to):
Required Knowledge / Skills:
References:
Critical Bounty Fee:
The fee for this Critical Bounty is $50,000, paid in STX.
Critical Bounty Application Deadline:
Applications are open and will remain open until a qualified application is sourced.
APPLY HERE
The text was updated successfully, but these errors were encountered: