Sergey Ukustov

One surprising thing here. When you restart node:a and node:b they do not try to connect each other. The expectation was that peer list survives a node restart.

Might be related: when node:a connects to node:b (single port and WebSocket provided in multiaddr), there are _two_ TCP connections from node:a or node:b.

That's unfortunate @yusefnapora . Actually, I tried to create a more reproducible case in Vagrant, and Docker environments, but that magically works with no errors reported :(( I can still...

IPFS node b reports its peer id on console. So `Here note IPFS peer id` means grabbing that reported peer and pasting it to `run-a.js`. It might be the case...

Something is bothering me about the hypothesis. Two of Ceramic hosted IPFS nodes just wait for an external connection. I run an IPFS node on my machine, and command it...

Use the same way as in https://github.com/machinomy/machinomy-contracts/issues/25

1 It is highly improbable for authors of web3 to come after you or anyone because of that. 2 That bothers me too, though. Going to find a replacement for...

Thank you for getting so much trouble for this @emschwartz Anyway, the idea to get rid of web3 as a direct dependency is too good to be left behind.

@stbrody Thanks. Added a link to the repo to package.json TIL: Apparently shortcut like `"repository": "npm/npm"` is not displayed on npm package page.

Maybe it is better to create a package for the nist weierstrass, so that we could use it and you could use it too?