W23 BDK Lib Team Call

[notmandatory]

📆 Tues June 6, 2023 12:00 UTC
📍 Discord General Voice Channel

Please add comments to this issue to suggest issues and PRs to discuss.

General Discussion Items

• BDK 1.0 milestones and timeline
• rust-esplora-client v0.5.0 released 🎉
• Summer of Bitcoin
• Any review begs? 🙏
• Blockers? 🪨

New Projects and Support

• Galoy, Fix caching bdk#985
• Fortris, currently using bcoin

Top BDK 1.0 PRs and issues

• 🎯 BDK 1.0 Next Release
• Reimplement Wallet, ElectrumExt and Esplora{Async}Ext with redesigned structures. bdk#976
• Test conflicting tx situations. bdk#964
• Fix release/0.28 branch 1.57 MSRV errors bdk#991

Top BDK_CLI PRs and issues

• 🎯 BDK-CLI Roadmap
• Bump bdk and bdk-cli to version 0.28.0 bdk-cli#153
• Update to v0.28.0 bdk-reserves#26

Top Other PRs and issues

• Create case studies page bitcoindevkit.org#143

Upcoming Events

• BTC Prague June 8-10
• Candadian Bitcoin Conf June 17-18
• TABConf Atlanta Sept 6-9
• BTC Azores Sept 23-24

🌅 Future Call Notes

📜 Past Call Notes

[evanlinjin]

I would like to talk about what I've been working on last week. Other than assisting @danielabrozzoni with the CoinControl stuff, I started work on a LocalChain that utilizes a linked list: bitcoindevkit/bdk#1002 (this was originally @LLFourn's idea, but I see how it will simplify our API).

pub struct CheckPoint {
    pub height: u32,
    pub hash: BlockHash,
    pub prev: Option<Arc<CheckPoint>>,
}

Imagine two threads, one holding the IndexedTxGraph and one sending from the chain-data-source. To start the chain-data-src thread, we only need to send the tip Arc<CheckPoint>. The chain-data-src can iterate in reverse to find the "point of agreement" without having to hold a lock on any structure, or having the main thread send over 10 blocks initially.

Likewise, when the chain-data thread discovers a new block, the tip Arc<CheckPoint> is the only thing we need to send to the main thread. No need to think about the previous blocks to include in order for the update to connect with the original chain.

Ideally I would like to include the RPC chain example with this PR as it shows how it is used.

[evanlinjin]

The other thing I would like to discuss, is how we can come up with a good guideline for spec-writing. Unfortunately @danielabrozzoni will not be able to make the call.

I already have some thoughts on this: https://gist.github.com/evanlinjin/41e6a23cc08e888884bded327e290866?permalink_comment_id=4587231#gistcomment-4587231

[notmandatory]

Meeting notes from HackMD (lightly edited)

W23 BDK Lib Team Meeting Notes

New Projects/Support

• Justin from Galoy working on Blink live batch service
  • currently watchonly, payout side next week
  • using new hot wallet, needs to scale for 200K+ addresses
  • Reimplement Wallet, ElectrumExt and Esplora{Async}Ext with redesigned structures. bdk#976 (comment)
  • would like to do block by block sync, horizontal scaling (multiple nodes)

Top PRs

• Evan working on RPC

  • first step LocalChain PR
  • then update example

• Evan PR 976

  • Daniela reviewing
  • LLoyd final ACK
  • Merge end of next week
  • in Italy
  • review call Thur June 15 13:00 UTC
  • Vlad may have review web page

• LagginTimes PR 964

  • taking over from Raj
  • framework for setting up TX
  • updating tests with new framework
  • target for alpha.2

• Esplora client

  • steve to create issue to discuss retry

• Testframe logging

  • Vlad sync up with LagginTimes

• backport 0.28 MSRV PR 991

  • Vlad to help final ACK

Timeline

1. alpha.1, PR 976 Redesignd IndexTxGraph, ChainOracle, basic electrum and esplora clients, wallet
2. alpha.2, linked list localchain, RPC client, test framework
3. alpha.3, coin selection
4. alpha.4, planning?
5. alpha.5, wallet txbuilder

Can we do monthly alpha releases? TBD

Spec writing

• Evan asked how should we write specs (see link in above comment)
• better guidelines