11:11:56 <Hishawork> just did a git pull on p2pool and went to start and got ZMQReader exception Address already in use, aborting
11:12:50 <Hishawork> do I need to remove the --zmq-pub command from my monerod?
11:13:04 <moneromooo> Either another process is already binding on that port, or the system has it reserved for a minute after the process died. Fix this and restart.
11:31:29 <Hishawork> so it looks like whatever change happened over the weekend doesn't play nice with source monerod, removed it and moved back to the one pulled from p2pool and connects fine
11:33:06 <sech1> yes, it's a bug in the latest code
12:31:36 <sethsimmons> sech1: is https://github.com/SChernykh/monero/tree/p2pool-api-v0.17 still the best branch to be building to stay up to date? Or should I switch my guide to using https://github.com/SChernykh/monero/tree/p2pool-api-release?
12:31:55 <sethsimmons> I would imagine -release but have been out of the loop for a few days.
12:32:14 <sech1> I think you can just use the official release-v0.17 branch
12:32:19 <sech1> my PR was merged
12:32:38 <sethsimmons> sech1: Ah, from the main repo?
12:32:44 <sech1> yes
12:32:53 <sethsimmons> https://github.com/monero-project/monero/tree/release-v0.17?
12:33:06 <sech1> yes
12:33:09 <sethsimmons> Ok, awesome, will switch and re-build
12:41:03 <DataHoarder> ^ using that on my nodes, works well
13:58:21 <hyc> having all users with a pre-set config file pointing at the same monerod somewhat defeats the ability to have independently created blocks
13:59:02 <jaska087> but i doubt most of miners care about it
13:59:17 <jaska087> those who care can and will run their own monerod without problem
13:59:22 <DataHoarder> let them make the choice, default the good option :)
19:34:14 <mightysnowman[m]> Is 51% attack something to really be worried about or?
19:34:47 <mightysnowman[m]> Like wouldnt it be possible for the nodes to detect if one single node with 51% hashrate submits suspicious transactions and just ban that node?
19:35:36 <mightysnowman[m]> There are many small coins that have pools with like 70% hashrate and people buy them for some reason
19:41:14 <hyc> in the long run, yes, it is really the only attackable surface in a Pow scheme. if it gets valuable enough, any PoW chain will become a target
19:41:48 <hyc> if the majority of miners are solo or p2pool, that threat goes away
20:09:15 <gingeropolous> and in general mightysnowman[m] , a 51% isn't great, but its not a death sentence for a cryptocurrency network. For a healthy network, they are difficult to pull off, but in the cases that they do happen, a 51% attack is usually used to double spend, so its exchanges that are usually affected
20:09:37 <gingeropolous> not really individual users, except for any market effects. but the market seems not to care much about fundamentals 
20:09:40 <gingeropolous> so, .shrugface
20:10:36 <gingeropolous> i.e., a 51% attack is used to target a specific target, not the entire network
20:11:11 <gingeropolous> however, in the case of monero and other ringsig based currencies, there can be some hits to privacy
23:09:38 <abberant[m]> my monerod is being semi-spammed with "Transaction not found in pool", maybe p2pool is trying to ask for transactions that have already been added to blocks? I have a few of my  friends p2pools hooked up to my node so it might be an issue with one of theirs
23:09:56 <abberant[m]> seems to be functional so
23:10:55 <xmrvsbeast[m]> seeing this as well, might be cause by p2pool as my private node has a few but public p2pool node has many
23:11:17 <abberant[m]> that would make sense, thanks for the input
23:14:20 <DataHoarder> When a block gets broadcast through p2pool it tries to get transmitted again through your monerod node
23:14:36 <DataHoarder> the template only includes txid list, not the transactions themselves
23:15:03 <DataHoarder> if you try to broadcast a block with a txid your node does not have, you get that error
23:15:44 <DataHoarder> some nodes do not have transactions other nodes do have, maybe too new :)
23:18:12 <DataHoarder> At the moment p2pool has 10s delay before including new transactions it knows about into block templates