Jonathan Underwood

This sounds like an Electron issue. Electron treating Uint8Array as interchangeable with Buffer is probably not a good idea. I'm not sure why Electron would do such a thing. I...

I am here, but this repository is not a priority for me. PRs and more importantly PR reviews are greatly appreciated and needed.

I don't think this should be a BIP, but rather it should be managed separately like BOLTs for lightning, EIPs for Ethereum, and SLIPs for Satoshi Labs proposals. NACK.

> Spreading [misinformation](https://twitter.com/LukeDashjr/status/1625481050196529152) that coinjoin transactions are affected because of ordinals is an attack on bitcoin. Doesn't look good for a BIP editor to get involved in such things. Maybe...

> Whether this gets allocated a BIP number or not seems ultimately down to the BIP editors' discretion to me and whether or not this is going to be used...

From BIP32 spec: > Each extended key has 2^31 normal child keys, and 2^31 hardened child keys. Each of these child keys has an index. The normal child keys use...

If the spec had said `"a string path representation of i+2^31 MUST be represented as iH"` then it would be spec... but also it would mean `i'` (apostrophe style hardened...

```js pathSuffix.join('/') ``` Can also be changed to ```js Array.from(pathSuffix).map(n => n & 2**31 ? `${n & 2**31-1}'` : `${n}`).join('/') ``` Which should work with either implementation. Edit: Also this,...

Currently on the block info page the full un-truncated block hash isn't displayed anywhere. It currently shows like `000000...fcc4a45` on the page. Could you be more specific on exactly where...

Getting target hex string from bits number would be a simple PipeTransform of the bits value: ```js const exponent = decimal >> 24; const mantissa = decimal & 0x7fffff; //...