---
# System prepended metadata

title: '# SoB 2023 Agenda'
tags: [sob2023]

---

# # SoB 2023 Agenda

- Previous Agenda: https://hackmd.io/nvQCp1dJSjahdNv3KjZEBg
- Data: 05-08-2023
- Partecipants: Harshit, Tarek, Vincent

---

## Topics

Please put the topics under this section.

Tarek:
**Current PR:**
- we already load `chrono = { version = "0.4", features = ["std"], default-features = false }` in the tests crate. That's why there was an error with the CI on github.
- discussion about https://github.com/coffee-tools/coffee/pull/191#discussion_r1282774269

**Off topic**
- transaction fees don't seem much?

Harshit :

- Null value errors persisting inside the clnapp.
- How to decode the bitcoin address which contain amount.
  #### Three cases that I have currently in mind : 
    - If it is an invoice, it would contain `payment_id`
    - If it is a deposit, it would contain `outpoint`
    - Else it can be a on-chain transaction fee containing the transaction id
    - (vincenzo) Naa this is too complex if you see this as a chain of if else, the URL is a language and you should write a parser for this language
    - (vincenzo) From BIP 21: Bitcoin URIs follow the general format for URIs as set forth in RFC 3986. The path component consists of a bitcoin address, and the query component provides additional payment options.    

  Any other case which I am missing here?
  
(vincenzo): yeah all the case that you had inside the BIP 21 :)