Jeffrey Esquivel S.

Hi @magmel48, sorry for the delay with this, most of our efforts are currently on 2.0, and not so much on adding new features/supporting new platforms on 1.0. I hope...

Hi guys! Sorry again for the delay, I did take a look at this issue back in April, but didn't had easy access to an M1 Mac to test possible...

Perfect! Thanks @magmel48

Closing stalled issue. Since all efforts are now geared toward albatross, it's unlikely this would be implemented.

This issue seems to be fixed by the merging of #586 , so I'm closing it. Feel free to reopen it if there's something still missing.

One initial idea that comes to my mind is to have an RPC method to create a new validator out of the current node. This would have improvements in UX...

Hi again, I did some more digging on this issue and it seems the problem started with https://github.com/npm/cli/commit/3a7378d889707d2a4c1f8a6397dda87825e9f5a3 that removed `node-gyp` from npm's `bin/` directory (where yarn looks for it...

> Sounds good to me. That works on all later npm versions? I just tested it with the following combinations of node and npm: - For Node v16.20.2: npm versions...

> So isn't the real bug that yarn can't find `node-gyp` anymore? Yes, that is the real bug indeed and the ideal solution would be to fix it there, but...

> I don't think we can use PEM files for the TLS certificates as native_tls haven't finished that feature yet[1] > > [1] [sfackler/rust-native-tls#27](https://github.com/sfackler/rust-native-tls/issues/27) I moved this to #41 so...