志宇
志宇
> Yes.. I have been seeing this one in my local.. I mean if the error states `"Resource TEMPORARILY unavailable"`, I think we can safely wrap the calls with exponential...
Thank you @casey for filing this issue, and @rajarshimaitra for identifying the part of the codebase responsible for the inefficient sync logic. When I was restructuring the `RpcBlockchain` implementation, I...
@terror @casey Would it be possible to show me how you are using `RpcBlockchain` for testing?
I still have some security concerns regarding the current implementation (although, I am no security expert, just based on what I've read on the internet). I will list them here,...
Another aspect I've been thinking about, is the great majority of the time people will be using English (which shouldn't require Unicode normalization). For the passphrase, we can do a...
> This, instead, I think should be tackled here: for now, avoiding Debug and Display (or manually implementing a really generic one) should be enough (with an appropriate comment on...
> > Should we avoid using heap memory, and keep everything on the stack? > > One advantage of this (on top of the extra safety) is that it would...
There seems to be a typo in the title - "singer" should be "signer" :sweat_smile: - whole world of difference haha.
This will be extremely helpful for the multi-descriptor capability (#486), so we do not have to attempt to sign with every single `Signer` contained within `MultiTracker`.
Damn I wish I saw this PR before working on the `RpcBlockchain` bug fixes/reimplantation