View complete GPT-powered meeting notes
Skim through the meeting in minutes by GPT-powered summary, notes, action items and more.
Overview
Mårten and Will discuss their agenda for the meeting, which includes updates on SBTC, a developer survey, and organizing meeting documents. Mårten introduces the Stacks Core Engine GitHub project and encourages everyone to add their issues to the board. They also discuss OKRs for the SPDC Working Stream, focusing on delivering SPDC mini, creating an SDK for developers, and engaging participation in early releases of SPDC. The goal is to have documentation completed and usable by developers. They also aim to have at least 50 unique STX addresses using SPDC on testnet.
Mårten discusses the goals and key results for building on SPTC, including having a list of applications and seeing STX holders registering as signers. Andre asks about best practices for deployment on testnet before going to mainnet. Mårten emphasizes the need to track usage on testnet before deploying anything on mainnet. The transcript also covers goals for September, such as having a design agreement, roadmaps, user guides, and completing SPDC Alpha on testnet. Mårten presents an initial deployment plan with aggressive deadlines but acknowledges that they may change based on project risks and visibility. Andre suggests releasing SPDC mini 0.1 in September on testnet and aiming for mainnet release in October or Q4. Will discusses adding distinctions between releases intended for testnet and mainet in the Gantt chart timeline. Jacinta expresses concerns about security considerations before putting something on main net, but considers a testnet release feasible with caution.
Jacinta Ferrant mentions that getting the project done may be difficult without a finalized design, but still doable. She also believes that focusing on the mainnet is too ambitious. Mårten and Sayak briefly comment before Igor raises concerns about prioritization, shipping a main net without an SDK or documentation, testing efforts visibility, and lack of audit consideration. Will Corcoran confirms there will be an audit and discusses planning around it. Sergey Shandar suggests organizing a meeting to discuss deployment tasks for the testing team. There is a brief discussion on naming schemes and code deliverables related to SBTC and Nakamoto integration work. Jacinta provides updates on consolidating documentation for the Sprint while explaining the major components of the signer ecosystem: Signer Library, Signer API, Signer Web UI, and Signer Dashboard. Will Corcoran asks if Jacinta is collaborating with Hero Explorer for adding SBTC functionality to their platform. Jacinta explains potential overlap between metrics in Hero Explorer and functionalities in Signer Web Dashboard but emphasizes collaboration efforts with Andre regarding any overlaps. setbern mentions shifting focus towards documentation readiness before further development on web parts of the project. No updates are provided by Jose Sedze regarding Clarity side issues.
Andre discussed several product items during the meeting. He mentioned the importance of designing the SBDC architecture to support Ordinals in the future, as it is an area of interest for developers. Andre also raised a question about using SBDC to pay for transaction fees and whether STX is required for this purpose. Martin mentioned sponsored transactions as a potential solution. Andre highlighted the need to remove the liveness ratio, which has been identified as a barrier to institutional adoption. Lastly, he mentioned the SBDC bridge as a primary product offering and discussed defining its product requirements and user interaction with the protocol.
Mårten mentions the presence of smart individuals who can contribute to alternative SPDC designs. He also acknowledges Jose's interesting proposal for a time-locked BTC peg for Bitcoin. Andre is unsure if the current SBDC design supports this functionality, and he suggests further analysis. Will asks Jose about his knowledge on Nakamoto improvement and leveraging resources between different groups. Sergey is working on testing infrastructure but needs more clarity before onboarding new people. Martin reminds everyone of tomorrow's project board review in the working group call. Igor points out that certain parts of the technical specification document can be closed or migrated, while also highlighting potential interactions and transitions to consider in future meetings.
Outline
- I. Introduction
- A. Purpose of the meeting and agenda (00:36 - 02:53)
- B. Introduction of the stacked blockchain developer survey (01:31 - 02:16)
- II. Documentation and Communication
- A. Importance of clear and concise documentation (03:32 - 04:23)
- B. Single source of truth for meeting documents and agendas (03:32 - 04:00)
- C. Updates and editing of project board issues (04:23 - 05:30)
- III. Testing and Deployment
- A. Discussion on deployment testing documentation (02:32 - 02:37)
- B. Formulating initial OKRs for the SPDC Working Stream (08:49 - 10:24)
- C. Deployment schedule and milestones (17:06 - 21:08)
- IV. Collaboration and Prioritization
- A. Importance of robust prioritization (25:25 - 27:11)
- B. Audit process and involvement of Nakamoto team (27:11 - 28:37)
- C. Status update on the Clarity side of things (37:21 - 37:35)
- V. Open Discussion and Questions
- A. Addressing questions and concerns regarding deadlines (23:53 - 24:06)
- B. Discussion on Ordinals and other product items (43:57 - 46:05)
- C. Reviewing the project board in the working group call (55:25 - 56:04)
- VI. Conclusion
- A. Summary of the meeting and closing remarks (58:34 - 58:54)
- Note: The timestamps provided in the outline indicate the approximate time range when the topics are discussed in the transcript.
Notes
- Meeting to cover a super active project
- Topics discussed include testing, documentation, and deployment
- Will Corcoran to circulate a document for action items and agendas
- Single source of truth to be established with a README pointing to all meeting documents
- Contributors encouraged to prioritize backlog items
- Will Corcoran to assign action items and provide context
- Participants can edit project board issues
- OKRs discussed: key results, early SPDC releases, engagement
- Deadlines and prioritization concerns raised
- Clarity and visibility in working groups emphasized
- Collaboration with the Nakamoto team mentioned
- Martin providing initial structure and understanding of SPTC
- Backlog of product items to be discussed
- Concerns about ordinals and other topics raised
- Call scheduled for further discussion
- Will Corcoran to close the meeting.
Action items
- Will Corcoran will reach out to Jose regarding their knowledge or experience in leveraging different resources between Nakamoto group and SBTC group.
- Sergey Shandar will ask for help from SBTC team to provide what they need for testing infrastructure.
- Marten will ping critical bounty team on a discussion thread or write them an email so that they don't feel forgotten.
- Note: Other action items may have been discussed but are not mentioned in this specific part of the transcript (part 5).