10:07:17 <masai> hi
10:13:55 <masai> does anyone knows Monero fork that only allows solo mining
10:21:25 <moneromooo> wownero does something about this.
10:21:48 <masai> https://git.wownero.com/wownero/wownero/commit/122fc4aa56f50206bf78568b13f2ebc7cce1a9bd
10:21:52 <masai> this one 
10:25:14 <masai> i found https://git.wownero.com/wownero/wownero/pulls/369
10:25:42 <masai> but does this helped wownero?
10:25:49 <masai> from 4july
10:27:50 <masai> or maybe to find another way of removing pools
10:36:45 <masai> moneromooo is very important the idea of removing pools
10:37:09 <masai> practically i dont c smth working until now
10:38:11 <masai> any suggestion if worth using wownero approach?
10:43:35 <moneromooo> Not really.
10:44:16 <moneromooo> One possibly avenue might be to require loads of data per block on the miner side.
10:44:42 <moneromooo> So you'd rely on saturating a pool's ability to transfer lots of data fast enough.
10:45:00 <moneromooo> Handwavy so far though.
10:46:06 <moneromooo> So it would have to be fast to generate (so you can do it locally), require something secret from the pool (so it can't be generated by the miner).
10:54:55 <masai> "loads of data per block" what this means exactly
11:05:47 <moneromooo> Large amount of bytes which are per miner (so can't be, eg, optimized by miners re-sharing) and per block, so transfer has to be made for every block. Possibly even small amount of data for every nonce.
11:06:31 <moneromooo> The point being that a pool will have lots of miners, so if every miner needs 1 MB/block of fresh data, a pool with 1k miners will need 1GB/block.
11:17:22 <masai> how miners is identified from pool
11:17:35 <masai> are
11:31:16 <masai> miner.cpp ?
11:48:00 <masai> how to block miners from creating pools/miners cooperative?
11:49:06 <masai>   finding smth more specific than data/block
11:57:37 <masai>  how miners are identified
11:57:53 <masai> for putting a limit on them
12:09:45 <masai> moneromooo what do u think