All WG: Leads Sync Thread

[will-corcoran]

Sprint 7 (mid-point): October 10th, 2023

🧭 Emoji Legend

⛓️ == Blockchain / Nakamoto WG
💻 == Clarity Wasm WG
📝 == Clarity WG
🫂 == Quality of Life
🔄 == sBTC WG
🤹 == Ecosystem Project Management

Updates from Leads

🤹‍♂️ Ecosystem Project Management @will-at-stacks

• Provided the group with an overview of upcoming dates and releases.
• Current emphasis on shipping sBTC DR 0.2 on 10.16 & Mockamoto on 10.17
• Focus will then pivot to an internal deadline of 11.10. See items in bold in image at bottom of this post.

🫂 Quality of Life WG @will-at-stacks

• @KeewenawSTX provided a quick updated on auditing process. Recommended working with him to get any completed chunks of functionality audited as they are complete - rather than a single large audit at code completion.
• Noted that @wileyj upgraded stacks-network to a GitHub Teams account
• Updates on GH Discussion Boards:
  • All WG Leads to have intros posted by EOD today
  • All WG Leads to start posting meeting minutes ASAP
  • All WG Leads to have Sprint Sync updates posted by 10.17 @ 8am EST

⛓️ Nakamoto WG @EmbeddedAndroid

• Preparing the end to end testing infrastructure (150 nodes)
• Task breakdown and project planning in progress

🔄 sBTC WG @AshtonStephens

• Aiming to ship DR 0.2 by EOW (10.13)

📝 Clarity WG @setzeus

• DR 0.1 - Design frozen
• Planning next sBTC version post-SIP
• Storage contracts for Signer WG WIP
• [proposal] Example contracts & documentation
  • Minting w/ sBTC

💻 ClarityWasm WG @obycode

• Progress continues on testing framework - very extensible tool for replaying transactions from the chain state in different environments
• Slower progress than hoped for implementing new functions - contract-call? and sha256 slowed us down
• sha256 is now complete, and contract-call? will be complete by tomorrow
• print is the only known remaining item that will be a unique challenge — the rest are a variation of something that is already complete
• We have a new team member to help with writing tests, which will speed up the remaining implementations
• Refactoring leading to > 1800 LoC removed and cleaner model for clar2wasm core component

💼 Product & Biz Dev @andrerserrano

• Stacking UX
  • Reviewing changes to stacking post-Nakamoto
• Delegated Signing
  • Double checking there aren’t any challenges with this approach. Requirements feasibly seem to be a signer:
    • 1. Run a Bitcoin Node
    • 2. Run a Stacks Node
    • 3. Run the Signer Binary
• DR testing program & release update
  • 111 testers approved so far
  • Onboarding premiere Stacks apps

[will-corcoran]

Sprint 8 (mid-point): October 24th, 2023

🧭 Emoji Legend

⛓️ == Blockchain / Nakamoto WG
💻 == Clarity Wasm WG
📝 == Clarity WG
🫂 == Quality of Life
🔄 == sBTC WG
🤹 == Ecosystem Project Management

Updates from Leads

🤹‍♂️ Ecosystem Project Management @will-at-stacks

• Upcoming plans for November 10 roadmap reveal.

🫂 Quality of Life WG @will-at-stacks

• Prioritizing scheduling proposals validated by key stakeholders like Coinfabrik.
• Nikos:
  -- sBTC asset contract’s property tests now run as part of the GitHub Actions
  -- sBTC asset contract’s property tests now use the new clarinet-sdk
  -- Proposal in progress for streamlining writing of property tests using the new clarinet-sdk
• Carlos:
  -- Completed integration testing CI
  -- WIP: adding runtime profiles to devnet

⛓️ Nakamoto WG @EmbeddedAndroid

• Update on Makamoto progress, including merged PRs and future goals.
• Target timeline for wrapping up PRs is within a week.

🔄 sBTC WG @AshtonStephens

• Focusing on finalizing sBTC SIP design by Friday.
• Addressing open research discussions transparently here.
• Concerns about delays caused by Makamoto impacting timelines for January release audit preparation.

📝 Clarity WG @setzeus

• Slow due to knowledge transfer but heavily focused on sBTC SIP review.
• Need to consider economic incentives in the sBTC SIP.

💻 ClarityWasm WG @obycode

• Plans to have a complete implementation by November 10.
• Making good progress on implementing functions (61% implemented; 79% for boot contracts)
  -- Completed sha256 and hash160 (with additional testing)
  -- Completed functions for tuples (tuple , get , merge , plus serialization of tuples)
  -- Completed functions for sequences (append , as-max-len? , concat , element-at , element-at? , len , replace-at? )
  -- In progress: buff-to-int-be , buff-to-uint-be , buff-to-int-le , buff-to-uint-le , is-eq , not , xor , slice
• Completed the major refactoring work
• A/B tester is a little behind, but ready for internal demos tomorrow

💼 Product & Biz Dev @andrerserrano

• BD - Business partners finally understand the importance of Nakamoto; lots of chats of folks wanting to become a signer for sBTC. Next step — packaged offering for nodes with a third party.
  -- Copper announcement went live! Copper (premier custodian) will be supporting the Stacks layer as a Bitcoin L2. Copper released support for Stacking, SIP 010 assets, and announced they will be a signer for sBTC.
• Product - Successful hackathon turnout and builder momentum
• sBTC DR retro
  -- Testnet deployment complications
• sBTC Research
  -- Security model
  -- OP_DROP vs OP_Return
  -- Economics of sBTC transaction fees

[will-corcoran]

Sprint 10 (mid-point): November 22nd, 2023

🧭 Emoji Legend

⛓️ == Blockchain / Nakamoto WG
💻 == Clarity Wasm WG
📝 == Clarity WG
🫂 == Quality of Life
🔄 == sBTC WG
🤹 == Ecosystem Project Management

Updates from Leads

🫂 Quality of Life WG @saralab & @wileyj

• Working towards Controlled Testnet:
  -- Can kick off next week, requirements are WIP
  -- Resuming Mutation Testing from where it was left off
  -- Great progress on optimizing the CI/CD (h/t @wileyj )
  -- Need to run a Fuzzer pronto, @moodmosaic most likely can own this

⛓️ Nakamoto WG @saralab

• Nakamoto 0.2 Updates:
  -- 33% Complete
  -- Slight delay with failing tests on a PR
  -- TenureChange tx validation is making good progress
  -- All 0.2 (and 0.3) milestone tasks have been broken down, estimated, and assigned
  -- MVP for Public Testnet and Mainnet WIP (hope to be completed next week)
• Audits:
  -- @saralab and @KeewenawSTX to coord on kicking off DKG audit

🔄 sBTC WG @AshtonStephens

• Organizing existing work
  -- What can be meaningfully worked on right now? (end of Nov)
  -- Who has the potential
• Communicating with stakeholders
  -- Changed timelines
  -- Work they can do now before sBTC
• Determine if there are any resources that make sense to add to Nakamoto

📝 Clarity WG @setzeus

• Clarity-Bitcoin-v5 should be released late next week (~11/30 - 12/2)
  -- Increasing test coverage on Clarity-Bitcoin-v5 from 70% → 95%
  -- Writing up documentation for other devs
  -- Design doc
• Nakamoto research & planning (PoX-4)
  -- Majority of time was spent researching, detailing & discussing all data structures & functions required for PoX-4
  -- Kicking-off Argon/PoX-4 engineering this sprint

💻 ClarityWasm WG @obycode

• Still making good progress towards 100% of builtins implemented
  -- 92% - 10 functions remaining! (​asserts!, from-consensus-buff?, index-of, index-of?, int-to-utf8, map, to-consensus-buff?, try!, unwrap!, unwrap-err!)
• Still on track for an initial developer release with 100% of functions covered by end of November
  -- UTF8 support will be limited
  -- Costs tracking and error handling will not be perfect
  -- Switching between VMs by epoch may or may not be included
• Continued slow progress on A/B tester
  -- Learning a lot about node’s inner workings while doing this
  -- Identified many potential optimizations that can be applied to core
  -- Very close to running through real blocks of transactions
• Good progress on integration with Clarinet, which may be the ideal place to “release” the developer release

💼 Product & Biz Dev @andrerserrano

• Delegated signing
  -- Question: are we able to assign two public keys to the signer? This would allow Figment to easily collect fees to one address and send the remainder directly to the client’s address.
  --- We’d need a way to do a weighted rewards distribution
  ---- Ex: Address A = 90% of reward; Address B = 10%
  ---- It would happen at the delegation level (not a protocol level change). it’s not obvious that it would work.
  --- Exploring options to better serve pool providers and solo-stackers, including backup node providers
• Coming Soon: sBTC Design Series, topics to include hard cap

🚀 Launch Comms @cuevasm

• Updates to be provided in this call moving forward

[will-corcoran]

Sprint 11 (mid-point): December 6th, 2023

🧭 Emoji Legend

⛓️ == Blockchain / Nakamoto WG
💻 == Clarity Wasm WG
📝 == Clarity WG
🫂 == Quality of Life
🔄 == sBTC WG
🤹 == Ecosystem Project Management

Updates from Leads

🫂 Quality of Life WG @saralab & @wileyj

⛓️ Nakamoto WG @saralab

🔄 sBTC WG @AshtonStephens

📝 Clarity WG @setzeus

💻 ClarityWasm WG @obycode

💼 Product & Biz Dev @andrerserrano

🚀 Launch Comms @cuevasm