Nakamoto WG: Mtg Mins Thread

[EmbeddedAndroid]

October 5th, 2023

✅ Status

@jbencin

• Adding tenure change based on Aaron Nakamoto branch

@kantai

• Updates to the chains coordinator for running a Nakamoto node

@jcnelson

• Finishing HTTP server refactor
• Helping the sBTC team sort out merkle proofs

Mark

• Discussing timing on audit, hoping to save time.

@saralab

• Waiting on Mockamoto node to be ready
• Adding features to explorer for sBTC developer release

@will-at-stacks

• Overall project management and working group refinements
• @CAGS295 and @moodmosaic have had their grants extended

@EmbeddedAndroid

• Tied up with sBTC developer release this week
• Working on task breakdown, milestones, and project plan
• Distributed multinode "smoke testing" for stacks and stacks signer
• https://github.com/EmbeddedAndroid/stacks-signer

🅿️ Parking lot

What should @jcnelson work on next?

• Nakamoto chainstate needs to support storing staging blocks and also yielding the processable block
• Updates to the coordinator
• @kantai will continuing working on chainstate in parallel and miner changes (entry point)

[will-corcoran]

October 12th, 2023

✅ Status

@jbencin

• making progress; identified why WSTS failed to compile

@jcnelson

• 40% into Nakamoto coordinator; no blockers
• Mockamoto update (Oct. 17th deadline): 9 issues remaining (most or all in progress)
• Call to action: Https refactor needs reviewed & merged (any 2 reviewers). Jacinta & ?

@wileyj

• waiting to connect w/ TB to pursue what’s next; focused on research

@jferrant

• integrating Sayak’s changes re: contract calls, mocking PoX contract/updating integration test to use it

@soju-drinker

• Working closely w/ Jacinta - good movement, important problems being solved; porting over btc test from old WSTS repo to new hub

@saralab

• Offsite/hackathon needed? (early Nov; Sarala to connect w/ Will)

@xoloki

• focus on solving Byzantine coordinator problem re: signers & identifying bad actors; writing new versions of coord state machine

@will-at-stacks

• General project management; mtg invite out for roadmap review mtg (11/10); connect w/ Sarala re: possible offsite

[AmandaJHall]

October 19th, 2023

✅ Status

@jbencin

• Working on ledger & multisig PRs
• Updated TenureChange PR

@jferrant

• Signer work going well; DKG now triggered by the coordinator on startup if it is not found in the pox 4 contract (PR up)
• Work continuing on hardening the system/handling restarts; have potentially better solution to coord/signer DKG determination in the POX contract (dependent on clarity 256 bit math)
• Need to make a decision re: how we plan to set DKG based on math decision

@saralab

• Looking into the draft PR from @kantai

@EmbeddedAndroid

• Owe @wileyj documentation on lava-server + lava-dispatcher installation (will deliver EoW)
• Working on multinode test definition for the stack signer distributed test rig
• Blockers: time; hi-pri issue put on plate from Leather team

[AmandaJHall]

October 26th, 2023

✅ Status

@jbencin

• Done with Ledger!
• Taking a look at the PR requests assigned to me
• Working on the TenureChange (goal to get it in a state where it can be merged)

Blockers:

• Waiting for deserialize with epic trait; would like to pick this from someone else code
• Would be ideal to have this in a separate PR AI: Merge Aarons PR’s to provide this

@jcnelson

• Expanding test harness, implement better tests
• Wrapping up work on HTTP refactor, addressing issue from @xoloki

@kantai

• Wrapping up reviews + feedback on PRs (Jude's coordinator PR)

@jferrant

• Refocus on sBTC this week

• Hardening the system, gracefully pickup state after a signer crash

• TM folks starting to work on the sBTC, VRF calculations, will post a discussion.

• Blockers: Need clarification on Nakamoto timeline

@soju-drinker

• Working with @jferrant & reviewing Mockamoto PRs

@EmbeddedAndroid

• Writing up a test plan document for the signer testing

@xoloki

• Finishing up Byzantine coordinator work

@saralab

• Need to get ahold of Mark put together a (more staggered) game plan for audits

🅿️ Parking Lot

@saralab
Neon status and breakdown

• Is this enough post Mockamoto? @kantai: I think that it is, outside of any issues discovered in PRs.
• Are there additional resources?

Beyond Neon we need to breakdown the next couple milestones-

• How do we get to code complete by Dec 31st?
• Merge some of the Milestones together?
• At least one milestone can be collapse into another

--Nakamoto + sBTC timelines
--Merge up
--HTTP PR- @xoloki: can you bump up the number of keys?

[will-corcoran]

November 02nd, 2023

TL;DR Congrats to the team on merging Mockamoto PRs! Amazing work done while parallel-processing sBTC design conversations!

✅ Status

@jferrant

• Status:
  -- Working on sBTC specific designs/where they overlap with Nakamoto
  -- Reviewed Jude’s PR 4009 but plan to go over again
  Working on diagram of Stacks Signer
  -- Noted:
  --- sBTC can also not be done without Nakamoto. So there definitely is awareness on sBTC side that focus will have to return to Nakamoto
• Blockers:
  -- Time limitations and context-switching

@kantai

• Status:
  -- Working on breaking down remaining chainstate tasks (Neon and beyond)
  -- Next, breakdown testing implications for chainstate
• Blockers:
  -- Review of PR 4009 is blocking Mockamoto follow-up work

@jbencin

• Status:
  -- Updated block proposal endpoint PR
• Blockers:
  -- Distracted by Ledger multi-sig work

@saralab

• Status:
  -- Focused on planning - NOW to public Neon Node launch. (working to add GH issues + milestones)
  -- Dedicating time to up-levelling the Quality of Life WG with @wileyj and @CharlieC3
  -- Preparing agenda for Austin offsite with @will-at-stacks
• Blockers:
  -- Concern about parallel work happening between sBTC and Nakamoto.

@jcnelson

• Status:
  -- Completing work on PoX-4 Instantiation to work as part of Epoch 2.5.
  -- Processing peg-ins / peg-outs moved from sBTC to Nakamoto (will speed up the dev time on Nakamoto)
  -- Focus on sBTC integration work?? (@kantai disagrees - other people can lead on this) -> Focus on network state machine
• Blockers:
  -- Time

@wileyj

• Status:
  -- Moving most of the CI work out of the stacks-blockchain repo
  -- Improve testing time
• Blockers:
  -- Context-switching
  -- Testing core contracts in Clarinet needs to be updated to utilize the SDK

@soju-drinker

• Status:
  -- Working with Jude to write design doc for sBTC / Nakamoto converging components (PoX-4)
• Blockers:
  -- Jude's time & attention

🅿️ Parking Lot

• Meeting format resembling daily stand-ups.
• Coordination changes with Jude for further progress.
• Nakamoto needing more focused time.
• Design calls diminishing after sweeping tasks.
• Prioritizing SBTC testnet.
• Task breakdown, timelines, and milestones for Nakamoto work.
• Testing implications for chain state.
• Design document for SPTC components within Nakamoto.
• Tagging and versioning for Nakamoto and Chains Coordinator PRs.

[will-corcoran]

November 09th, 2023

✅ Status

@jferrant

• Status:
• Blockers:

@kantai

• Status:
• Blockers:

@jbencin

• Status:
• Blockers:

@saralab

• Status:
• Blockers:

@jcnelson

• Status:
• Blockers:

@wileyj

• Status:
• Blockers:

@soju-drinker

• Status:
• Blockers:

🅿️ Parking Lot

Topic 1:

Topic 2:

[saralab]

November 09th, 2023

✅ Status

@jferrant

• Status

  • Working on consolidating sBTC designs
  • Miner validation and proposal for new blocks
  • Re-Reviewing Nakamoto PRs

• Blockers

@AshtonStephens

• Status:
  • Reprioritize focus to Nakamoto after task breakdown
  • Adding contracts for Nakamoto Signers

@kantai

• Status:
  • Reviewing Coordinator PR, merging some changes to the Mockamoto
• Blockers:

@jbencin

• Status:

  • Wrapped up multisig changes
  • Blockproposal PR ready to close today
  • tenurechange PR : part of it made it into Aaron’s PR
  • Validation checks possible now and merge the PR
  • Otherwise it will pull in other issues related to Neon and post-neon

• Blockers:

@saralab

• Status:

  • Updated GitHub with Neon, Argon task breakdown
  • Working on the estimates and testing plan
  • Offsite agenda and tasks

• Blockers:

@jcnelson

• Status:

  • Chain processing system , test peer example to work
  • Single tenure working , 10 tenures, 10 blocks working for now
  • Target completion this week

• Blockers:

@wileyj

• Status:

  • Waiting to get Neon nodes running
  • Resurrect Scott’s Fuzz testing PR:
  • This particular fuzzing is already in master
  • Focus on other fuzzing
  • Meeting with coinfabric to run distributed tests

• Blockers:

@soju-drinker

• Status:

  • Reviewing coordinator PR
  • Pox-4 changes for sBTC

• Blockers:

###🅿️ Parking Lot

• PR velocity
  - Legacy code base
  - Multiple dependencies and touchpoints for simple changes
  - Crosscutting concerns
  - Is it possible to have buildable PRs ?
  - We can breakdown tasks better
  - Separate PRs into functionality as much as possible
• Task Breakdown round 2
  • Include PR review time, merging and testing in all estimates
  • Consider design conversations and other tasks
  • Breakdown tasks to be as granular as possible for parallel processing
• QoL and Testing WG:
  • QoL, Testing infra, CI/CD, GH, Integration Test pipeline : JW, Charlie
  • Property Testing, Fuzzing, Mutation Testing: Help needed!
  • Nikos, Carlos, Who else?

[moodmosaic]

Property Testing, Fuzzing, Mutation Testing: Help needed!

Happy to help 🎯

[will-corcoran]

November 20th, 2023

✅ Status: Nakamoto 0.2 (aka Neon)

@jferrant

• Status: Working on Neon #3927, encountering a bug related to serializing and deserializing a point. Plans a pair programming session with @xoloki @soju-drinker for resolution.
• 🔴 Blockers: Unusual bug in task #3927; waiting for final review.

@kantai

• Status: Integrating the latest change coordinator PR into the mock node, planning to work on the Neon #4027 node next.
• 🔴 Blockers: Other stacks blockchain work may affect progress on Nakamoto stream.

@jcnelson

• Status: Working on Neon #4014, coordinator PR for tenure changes. Planning a second PR for validation tasks.
• Blockers: None mentioned, but tight timeline for PR completion.

✅ Status: Nakamoto 0.3 (aka Argon)

@jbencin

• Status: Working on Argon #4069, adding Nakamoto block to p2p communication. Waiting for Jude's PR merge to proceed with tenure change transaction PR.
• 🔴 Blockers: Dependence on Jude's PR for progress.

@soju-drinker

• Status: Gearing up to start Argon #3929, Signer binary submits BlockProposal validation to stacks-node for validation.
• 🔴 Blockers: Awaiting final review and backlog clearance.

✅ Status: OTHER

@xoloki

• Status: Working on WSTS #37, may take over some of Jacinta's tasks. Coordinating with @jcnelson and @kantai for task sequencing.
• 🔴 Blockers: Uncertainty in task assignment, needs coordination for task sequencing.

@BowTiedDeployer

• Status: Newly joined, bringing expertise in PoX-related tasks. Expected to assist with testing and parks related tasks.
• Blockers: None mentioned, but shorter onboarding period anticipated.

🅿️ Parking Lot

• Emphasis on tracking progress accurately and adjusting estimates for tasks and milestones.
• Upcoming PR review session planned.
• Deep dive on PRs in the next meeting.

[will-corcoran]

November 27th, 2023

✅ Status: Nakamoto 0.2 (aka Neon)

@jferrant

• Status: Working on tasks related to the Nakamoto coordinator; plans another pair programming session with @jcnelson .
• Blockers: Faced errors while implementing suggestions in the Nakamoto coordinator. Planning to pair again with @jcnelson .
• Backlog Issue: Neon genesis block generation routine

@jcnelson

• Status: Working on Tenure Change transaction validation
• Blockers: Concerned about @soju-drinker taking on a task related to PoX-4 due to unfamiliarity with the codebase.

@kantai

• Status: Working on Tenure Change transaction validation
• Blockers: No blockers - just concern about unknown issues during testing.

✅ Status: Nakamoto 0.3 (aka Argon)

@soju-drinker

• Status: Working on signer binary issues #3929 and #3930. Goal is to be completed with both by next Monday.
• Blockers: None mentioned.

@jbencin

• Status: Working on Nakamoto p2p block support. Goal is to be complete by end of Sprint 11.
• Blockers: Challenges with merging; uncertainty about completing certain parts of the task.

@setzeus

• Status: Working on PoX-4 stacker registration functions. Goal is to be complete by tomorrow.
• Blockers: None mentioned.

✅ Status: OTHER

@BowTiedDeployer

• Current Work: Working on mutation testing; suggests storing output for better analysis.
• Blockers: Needs guidance on storing the output of mutation testing.

@saralab

• Current Work: Leading meeting on tasks related to the neon milestone; discussing mutation testing and planning further discussion in the testing working group.
• Blockers: Concerned about meeting the December deadline for code completion in Neon.