---
# System prepended metadata

title: Meeting Minutes 3
tags: [Meeting, BDK Core]

---

Meeting Minutes 3
===

###### tags: `BDK Core` `Meeting`

:::info
- **Location:** Online
- **Date:** Oct 14, 2022 09:00 AM (UTC)
- **Agenda**
    - Weekly standup
    - Change to floating points for feerate calculations? 
    - How should we continue with coin control?
    - Testing.
    - How can be on-board new contributors?
- **Participants:**
    - Evan (@evanlinjin)
    - Daniela (@danielabrozzoni)
    - Lloyd (@LLFourn)
    - Raj (@rajarshimaitra)
- **Reference:** 
    - [Project board](https://github.com/users/LLFourn/projects/2/views/1)
    - [Raj's notes on coin control](https://hackmd.io/@raj/H18T1LV7i)
    - [Last meeting](https://hackmd.io/@evanlinjin/bdk_minutes_20221007)
:::

### Minutes

**Standup**

* Evan splitting up...
* Lloyd
    * General API for BnB, but still does what Bitcoin Core does.
 * Daniela
     * Nearly there, 3 days? But bugs.
     * Solution is close to what Lloyd had in mind.
     * Vec of placeholders -> build_witness -> substitute placeholders with actual pks/sigs/etc -> :tada:
     * can derive works for pks, but not pk hashes. Children keys? Use descriptor keys for now, iterate on top on that, add derive trait later.
     * TODO: Replace what is on bdk_core and see how it plays out.
 * Raj
     * Rpc sync with new structure.
     * Worked on coin control document, but needs to wait on what happens with coin selector and miniscript planning module.
     * Coin control is pre-processing before coin selection. Defines boundary, criteria for what coins to be candidates. Grouping, filtering and adding metadata basically.
     * Testing framework for bdk_core. Move testing framework from BDK -> bdk_core.


**In two weeks - PR applying everything we do to bdk :tada:**
* Use new Coin Selection API
    * CoinSelectionAlgorithm trait dies :skull_and_crossbones: 
* Use new Syncing API
    * Blockchain trait dies :skull_and_crossbones: 
* Use the planning stuff instead of `max_sat_weight`
* Focus on replacing internals, avoid keep adding features
* How to persist data?
* Don't break everything just now, just what we need
    * Some API will change a bit (CS), some will change a lot (Sync)
    * TxBuilder good enough :heart: 
* "Stable" API end of next week so we can start testing. 