smokesignal

smokesignal copied to clipboard

Error thrown when Peerlist.prototype.close is called.

vitamink

Changing seeds

4

In a long running application with turnover and new deploys, the seed nodes could change. I think a mechanism for updating the seeds in active modes would be useful.

jabr

Issue with LocalHost node ?

6

I'm setting up the smoke p2p on multiple ip addresses on my machine(Ubuntu shell on Windows 10). I'm testing the connectivity with a localhost node. I'm getting this error concerning...

sethleedy

Question regarding peer count

2

I am assuming smokesignal doesn't simply connect peers directly to each other, so a single peer will not be aware of every other peer on the network. Given this assumption,...

AlexanderParker

Exclusive networks

5

There is a small probability of a network becoming exclusive (and rejecting any new nodes) if they all hit the max peer number within the current network. I hit that...

jabr

Performance

3

It's not yet optimized for performance: - nssocket adds a large overhead, I think, because we don't use any of it's features. - a custom/off-the-shelf binary protocol might be cleaner...

marcelklehr

There's no authentication and encryption. Since hash(message.content) is part of the message id, all messages should survive a change of content by an adversary. Broadcasts are anonymous, so there's no...

marcelklehr

Instead of wrapping your own stuff _around_ smokesignal, why not be able to add it to smokesignal directly?

marcelklehr

Consider allowing people to add other transports, e.g. maybe zmq.

marcelklehr

The underlying cause of netsplits are subnets that form because nodes automatically choose closest nodes as peers. With network stability in mind they should actually do quite the opposite: choose...

marcelklehr