Walter Smuts

Added explicit peers about a month ago: ``` [neutrino] neutrino.addpeer=btcd-mainnet.lightning.computer neutrino.addpeer=mainnet1-btcd.zaphq.io neutrino.addpeer=mainnet2-btcd.zaphq.io neutrino.addpeer=mainnet3-btcd.zaphq.io neutrino.addpeer=mainnet4-btcd.zaphq.io ``` This didn't fix anything but since then I haven't accrued any new unconfirmed tx's: ```...

I ran `lnd` with `--reset-wallet-transactions`, waited for `LNWL: Finished rescan for`. Removed the second two unconfirmed tx, first one still there: ``` $ lncli listunspent --unconfirmed_only { "utxos": [ {...

I don't have much experience with `no_std` but here goes some info. Take it with a grain of salt however because I've not ever really been involved: * `rustfft` uses...

> or else we'd need a [semver-trick](https://github.com/dtolnay/semver-trick/) re-export to make the versions compatible. So this option has no downsides?

See https://github.com/ejmahler/RustFFT/issues/98

Suggestion to use "buffer" when talking about rust data types and ["signal"](https://en.wikipedia.org/wiki/Signal) when talking about the mathematical concept?

I've updated the wording to use "signal" and "buffer" where appropriate.

If you're trying to provide an example of how to work with real-valued signals I'm not sure it's appropriate here. [realfft](https://github.com/HEnquist/realfft) is a nice wrapper if you know you're only...

I'm happy to be FFT POC. Some initial thoughts are: * FFT is a pure function and should always return the same output for the same input * All combinations...

So I gave a bash at actually using this crate from a `no_std` binary. You quickly realise that it still tries linking in `std`. After a bit of fiddling with...