nymius

Hi @kouloumos, thanks for the review! In relation to the second point about the transcript metadata, I think that if we add the other speakers, to keep the consistency of...

> Good point! Although I'm not sure that the Bitcoin Design calls have a specific host in the same way that a podcast has. Other than Josie, the rest of...

Hey! I've finished the review. I think this one is ready. Answering your questions: 1. An hour and a half for the final review. Considering I was also listening the...

Totally! I wanted to check my final version (beyond the changes made by AI) were correct too, as in my other review you discovered an error after I marked it...

Hello @brunoerg I'm working on [coin-selection simulator](https://github.com/nymius/bdk-coin-select-simulation/tree/main). The idea is to have a common framework to run test consistently over different bitcoin coin selection implementations. I mainly followed this [simulator](https://github.com/achow101/coin-selection-simulation),...

> I agree with [@LLFourn](https://github.com/LLFourn)'s suggestion. I think someone should take this ticket on. I would like to give it a try.

I didn't considered the legitimacy of this as a real production case either. It seemed a good case just for the comments on #1103. Besides its utility I think I'm...

Hello @sudo-rsingh, notice here I was seeking for feedback about the justifiability of the change. The project can decide this is not necessary or it breaks some workflow, and not...

Hi @PranavKumar20, thanks for working on this. Answering your questions: 1. Your approach seems aligned. 2. I think that will come up later during the review of your code. It...

I would like to work on this, but I've got some questions: - There cannot be a situation where a user doesn't want to aggregate changesets? - For any reason...