archive snowblossom slack dev
prev 2019-01-10 next
2019-01-10 05:04:55
GitHub
[snowblossomcoin/snowblossom] Issue closed by fireduck64
2019-01-10 05:05:11
GitHub
[snowblossomcoin/snowblossom] Issue closed by fireduck64
2019-01-10 05:06:11
GitHub
[snowblossomcoin/snowblossom] #78 add vote tally page
2019-01-10 05:06:22
GitHub
[snowblossomcoin/snowblossom] #88 adding pool failover to pool miner
2019-01-10 07:35:47
GitHub
[snowblossomcoin/snowblossom] Issue closed by fireduck64
2019-01-10 12:06:10
Fireduck
Slowing down adding transactions enough to see the fee shift before pool is full
2019-01-10 12:15:19
Rotonen
so use a semaphore pivoting on that?
2019-01-10 13:50:51
Fireduck
Just for testing, don't need very fancy
2019-01-10 19:56:29
Clueless
Btw, I don't know if you need it, but I happen to have spent a lot of time messing with x509 certificates. Also happen to be testing my own CA library and command line tools.
2019-01-10 19:58:28
Fireduck
In channels I have a thing that builds an x509 cert signed with the node's key pair
2019-01-10 19:58:55
Fireduck
and when a node connects to another it always knows what node id (and thus public key) it is expecting so can validate the cert
2019-01-10 20:21:09
Rotonen
that leads to a race to masquerade?
2019-01-10 20:23:17
Fireduck
in the case of channels, it isn't hard to create a new node and get it into the peer tables
2019-01-10 20:23:44
Fireduck
but pretending to be a different node that exists would involve finding a public key that hashed to the same node id (address)
2019-01-10 20:23:48
Fireduck
so basically impossible
2019-01-10 20:31:00
Rotonen
check